skysight-inc/HackerNews huggingface dataset:
My story is much like yours. My mother was a stay-at-home Mom. She made extra income by sitting for a few kids after school and during the summer. During the summers we spent everyday at the pool. Took swim lessons from as early as I can remember. Became a lifeguard at the same pool I grew up at when I turned 16 and came back every year until I was 22.

During my years as a guard, I had roughly 100 "saves." Most were inner-city males, bused in a few times a month.

I'll never forget my first save. Its one of the few I really honestly consider a save and not just proactively going in after someone before it became a real issue. It was around 7:45PM, the pool was about to close and people were starting to leave. She was about 3 years old carrying a beach ball larger than her above her head. A strong gust of wind blew the beach ball from her hands and into the deepend of the pool and she ran right after it and into the water. She went straight down to the bottom. I watched the whole thing happen in what seemed to be maybe 3 or 4 seconds. Soon as she went in, I went in after her. Pulled her out and got her to the side and before her dad even realized what happened. I doubt she even realized what happened. Her dad couldn't stop thanking me for saving his little girl.

My most terrifying save was on St. Rita's Day, which is a school in Cincinnati for the Deaf. It was one of my first days guarding the pool and a deaf guy and his two deaf daughters went up a slide in the shallow end of the pool. When they got to their turn he put one girl in each arm and sat down. I tried and tried to whistle at them to get their attention. When I finally did it was too late and they had started going down the slide. No sooner did they leave the gated area did they fall over the side about 15 feet into 3 foot water. He landed standing and still holding onto the girls. I jumped in and rushed over to them. His arm had broken when he tried to grab the gate to prevent his fall. I didn't know sign language at the time so I couldn't really communicate with him which made the situation even worse. We were lucky though, we did have one girl who was pretty good and was able to talk to him, ask him and the girls if they were ok. The girls were fine but after his adrenaline had calmed a bit and we got him out of the water we noticed he had also broken one of his legs in the fall. As far as I am aware, that was the last St Rita's day we had.

My son is now 3 and I have already started teaching him how to swim. I vow to never have to worry about him in the water.

My wife jokes about how I act near pools and bodies of water. Always scanning, always counting, always watching for signs of a weak swimmer and I always will. Its part of me.
Bother you for a little advice? I'm working at a mid-sized tech company and am evaluating Docker for CI, testing and limited, internal deployment usages.

The services in question are built with a hodge-podge of shell scripts and build tools, so getting them all to compile locally is a challenge, let alone deploying them. My hope was that containerizing the builds would isolate any configuration problems, and that containerizing the deployed services would cut down on outages by permitting trivial rollbacks (say, by snapshotting all the service containers before each deploy and merely restoring them should a deployment fail). Of course, all of the above could be fixed by traditional means (e.g. rewriting the build system with a single, standard tool; streamlining the deployment process, etc.), but it seemed like Docker could solve 80% of the problems while easing the implementation of the proper solutions down the line.

Considering the above, do you still think Docker's a poor fit for business that aren't building hosting systems? Oh, and any nuggets of wisdom you could throw to a newcomer to the industry? :)
I get a certificate error. That's pretty egregious for banking software.
Scarry Pigs in Peril
We Should Not Ban 'Killer Robots', and Here's Why
I do agree with you, but we're on Heroku and that also has it's downsides - the biggest one we've found is that CPU performance on 1x and 2x dynos is very unpredictable - We've had to move to Performance dynos ($500/month each!) to get decent performance and prevent random timeouts.

Services like Cloud66 are interesting (they manage deployments onto your own EC2 or other cloud infrastructure), but the developer experience doesn't quite match Heroku yet.

Heroku really needs some more competition...
> I cannot currently compile Android on Android or iOS on iOS.

You actually could, hypothetically, compile Android on Android, in a sense, by chrooting into a Debian environment and compiling from there. I've done at least the chroot part (I had a Debian chroot environment with Xfce installed on my Galaxy Tab 2 for quite a while, though it was really slow and limited by the tablet's measly RAM).

The idea of running a GNU/Linux-like system on Android (reusing the device's kernel in a chroot or a similar setup) is basically the idea behind the Ubuntu for Android concept that fizzled away as Ubuntu's mobile version started to be developed: plug your phone into a dock, and the Ubuntu chroot takes over the peripheral devices and presents a desktop.
Same here, weird hijack.
Байкал+Кто+сейчас+на+конференции+•+Страница+1+•+Текущее+время:+29+июл+2015+09:26
Was there any? People need infrastructure at the same rate, even if that infrastructure is being surveilled , and there's no reason to believe their competitors aren't equally on the take.
>How well does Nix interact with inherently stateful things like databases?

This is a frequently asked question. Nix/Guix do not interact with such files, and we make it a point to differentiate between stateful and stateless. Nix and Guix manage the stateless, deterministic stuff, and system services or other mechanisms manage the stateful stuff. For example, there's a postgresql package in Guix, but installing it doesn't create a db cluster in /var/lib, it just installs the binaries, docs, etc to the user's package profile. However, GuixSD, the distro built on Guix, comes with a postgresql system service that creates the system db cluster before launching the postgresql server. In other words, stateful things are handled at a different layer than the packaging layer.

If a new version of an application requires a schema migration, then that would be something for a system service to perform with the updated binaries from the package manager. You still need to take care to back up your databases, home directories, etc.
One of the many sad things in this story is that Stephanie Lee was given false hope by overly enthusiastic technologists. Since YC is now funding biomedical startups, this will hopefully serve as a warning to others who find it easier to sound smart and confident than actually run a clinical trial.
We can, actually.

It's just so happens that 100% predictable outcome has nothing to do with hackability.
Google Contributor live to US users, contribute monthly to see fewer ads
It was a bad broker. But I've only met a single good one, compared to a dozen bad ones.

We bothered trying to go up the stairs because we'd already spent 30 minutes getting to Harlem, and apparently it had a terrace. Classic sunken cost fallacy, compared with greed. Who doesn't want a terrace?
I read three out of those five plus the Times, and I am not convinced they're significantly better - in the contrary, the New York Times does a lot of things better.

There are some advantages these papers have - for example, Haaretz is more willing to put good analysis on its (web, Hebrew-edition) front page, but I think that reflects an American culture of journalistic caution about mixing even vaguely editorial content with news, which I generally enjoy. (e.g. however much I disagree with the WSJ editorial board, I generally regard their news as credible and well-reported; I cannot say the same about e.g FAZ's straight reporting on Greece.
I don't want to address the difference between civilian and military pilots, since I think the author has done a fine job of that.

But I would like to point out that see-and-avoid doesn't really work in general, and particularly not in the case of two small aircraft with wildly different performance characteristics. I suspect that, even if the F-16 was on a practice instrument approach, the bottom of its performance envelope is significantly higher than the top of the Cessna 150's. (According to the 'pedia, maximum speed is 109kt and Vne is 140kt.)

See-and-avoid has been the first and more-or-less primary anti-collision system in aviation use, but if you've ever tried to cross a highway with high-speed oncoming traffic, you've probably already learned that there are limits to the human visual system. It's just not built to do that sort of thing. No doubt keeping your head outside the cockpit does prevent a lot of crashes, but expecting it to have prevented any crash, much less this one, is too much of a reach.

Keep in mind that most animal's visual systems are pretty good at picking up movement, but one of the signs that you are on a collision course with another vehicle is that it isn't moving in you visual field.

From [1]: "[The University of Washington’s Autonomous Flight System Lab] came up with a novel way to [modeled the UAS collision risk], reasoning that the known behavior (and random collisions) of gas molecules could serve as a way to predict collision probabilities between VFR aircraft, including UAS. (PDF)[3] To test the hypothesis, they compared the gas-molecule data to actual midair collision data and found a remarkably good fit. This allows two conclusions: manned airplanes under VFR run into each other at about the same random rate as gas molecules do and that’s pretty strong statistical evidence that see and avoid doesn’t work. (Because of a variance between the gas data and actual midairs, the paper concluded that see and avoid might work 14 percent of the time, but a bit better during the past few years. Possibly for a reason.)"

By the way, [1] is an entertaining post with some information, while [2] is a paper from 'stralia called, "Limitations of the See-and-Avoid Principle".

[1] http://www.avweb.com/blogs/insider/Why-See-and-Avoid-Doesnt-...

[2] http://www.skybrary.aero/bookshelf/books/259.pdf

[3] https://www.aa.washington.edu/research/afsl/publications/lum...

Ps. Ok, I do want to say something about the difference between military and civilian pilots. Back in 2004, six soldiers and a general died when a Blackhawk hit a television transmission tower guy wire while in heavy fog.[4] The tower was 1800 feet tall; apparently the helicopter hit the wire about half way up. It wasn't a training mission; the helicopter was "headed to Red River to check maintenance on equipment". The first question from me, the most holster-sniffing of non-pilots, was, "What was he doing flying below 1000 feet in heavy fog?"

[4] http://www.chron.com/news/houston-texas/article/Seven-soldie...
I really want to play Phutball, now. I wish there was an android app.
Wow, this looks really nice – I'm going to have to try FlexCSS for my next side project. Thanks for sharing!
The only reason I got "Lack" right was because of https://wiki.eth0.nl/index.php/LackRack
I'd like to hear your thoughts on how to be a good developer. I fall into this group and I'm entirely self-taught. I've been following the Free Code Camp curriculum while also working through some Linux books and Shaw's "Learn C the Hard Way." It's difficult for me to know what things I might be missing--the classic "unknown unknowns"--and I'd like to close whayever gaps there might be.
There is no algorithm to prove the correctness of programs in general but you can still prove correctness of specific programs.
[Disclosure: I'm the author] No argument that up-front, perpetually licensed software is currently a huge, profitable business. Windows and Office alone, as acknowledged, generate essentially $44B by themselves. There are also profitable businesses that pursue the traditional perpetual license model - Palantir being perhaps the most notable example (although from conversations with employees there, they are increasingly being pushed towards alternative models).

But the point of the Software Paradox is not that companies are not currently and cannot in future make money from software, and that there are no exceptions to the rule, it's that the trajectory broadly is not promising. Looking across a variety of software categories, from mobile to operating systems to infrastructure to tooling to consumer, the trendline is downward in terms of their up-front realizable revenue potential.

None of which should be taken to mean that software is going away. If anything it's becoming more important, hence the use of paradox. But developers and companies seeking to monetize software should at least be aware of the market context which is that it's becoming more difficult to make money from it the way that it was possible to even a few years ago. Even the lock-in mechanism, which is correctly cited as a method proven to monetize customers efficiently, is more easily replicated in services businesses (e.g. cloud) than it is in traditional on premise software, where open source has become both an expectation and a means of combatting lock-in.

If one looks at all of the available evidence and decides to proceed with a traditional software licensing approach in spite of the observable challenges, it is certainly not impossible for them to a) generate revenue and b) be profitable. But the degree of difficulty attached to this model has gone up considerably, and looks to only be getting worse. And this isn't just an academic theory, it's something I hear almost daily in conversations with vendors.
How startup Appbot works on creating great culture
Ye olde tragedy of the commons.
Don't forget people buy more cellphones because they get stolen more often.

Smartphone makers have little to no incentive to change this.
The attempts to get surgical checklists[1] (a basic aviation tool) adopted see to suggest that it is very, very amazing that outcomes are so good.

[1] http://www.who.int/patientsafety/safesurgery/ss_checklist/en...
Calculating Lego Brick Combinations Is Ridiculously Complex
Nokia builds a VR camera
That's cheating. I mean actually using vanilla Android as your host. Yours amounts to using a chrooted debootstrap for cross-compiling to an Android target.
I also get a certificate error and a blank blog site...
"If you're a merchant I wouldn't see Visa and American Express investing and taking equity in Stripe as a good thing."

What's best for the merchant is what's lost in much of these discussions. The continued fragmentation of the industry has left merchants struggling to navigate necessary customization and even more difficult documentation; although Stripe has led well in this area. Since accepting alternate payment methods and the ability to switch processors is prohibitively difficult, competition is artificially constrained - leaving "fees as high as possible". That's why we're building http://accepton.com Would love to chat: jonathan [at] accepton {dot} come
I think this is a great medium for educating potential future founders around the web, so thank you for taking the time to make this. I'm sure most HN user's out there have heard of Jessica Livingston's book "Founders at Work". I just got it in the mail today and its a great read. If you enjoy this kind of interview format you will definitely enjoy this book.
I feel like I must've experienced near drowning or something, because I find the experience of drowning very easy to imagine and relate to. I don't really recall anything specific.
That's some serious mindfuckery going on there.

You cannot see colors you don't have a name for... I wonder how much this extends to other parts of our life, maybe I should go read a dictionary!
Why would you want to leave PayPal Pro, for Stripe, if you're getting a lower rate w/ PayPal? Assuming the effective rate, including your monthly fee is still < Stripe.
It's also quite ironic given all of the insults lobbed at banks and their "bad technology" in Standard Treasury's pitch deck.
Rowhammer.js: A Remote Software-Induced Fault Attack in JavaScript
Looks like this news item is made up from recent Intel's press release [1] and quite a bit of hand-waving. Take, for example, a claim that 'it would radically increase the number of people that could be supported for the same price'. We already have E7 series Xeons that support up to 1.5TB of RAM [2] (is it per socket? there can be up to 8 sockets per server) At that point, surely we would be constrained by processing and I/O, not RAM.

[1] http://newsroom.intel.com/community/intel_newsroom/blog/2015...

[2] http://ark.intel.com/products/84685/Intel-Xeon-Processor-E7-...
volatile is mostly useful for telling the compiler not to optimize out a variable. For example, if you use memory-mapped I/O, you can mark a pointer to it as volatile to tell the compiler that the hardware will be changing it and it shouldn't make any assumptions about that while optimizing. That's lower level than most people go, though, so I understand that it's not useful for the average C programmer.
I assume that's because you don't get the building back? I think they get the kid back in these particular drills.

If not, then yeah this is a terrible idea.
also interesting to see Colleen Taylor is at YC now.. :)
> Even if there was one person capable of and willing to do this all, their current job title is likely "founder of their own startup".

I'm doing a decent chunk of that, aware of the parts I'm doing shitty, and that is my job title. :)

I was talking recruiting with a mentor. He said some of his best hires were founders he met at startup events looking to regroup and earn a paycheck after the failure of their own startup. Dark—but insightful.
A lack of bit addressability means that hammering one bit would burn out a whole word/page, but it doesn't affect how many cycles it takes to reach that burn-out point, unless you've got wear leveling.

In practice, if you burn out any one bit, you need to retire a chunk of the array at least as large as a cache line. And it's not likely that you'll actually be able to directly hammer a single bit, because the endurance is still low enough to require ECC.
A simple Docker container and image garbage collection script
Also, my guess would be that the median numbers reported by BLS include many people who have had the same job for 5-10 years and are being paid 2005-level salaries and not 2015 levels. In an upward-trending market, averages/medians over the entire employment base will under-estimate the current market rate.
>"git" or "mercurial" tells me I have an team that has some level of clue.

If you're judging a team being clued in by the SCM, you're doing it wrong. There are great teams that use SVN, and know-nothing teams that use git.

The measure of clued-in should be how well does a technology match the organization's needs?
Yes, this is now common practice for all browser vendors, AFAIK.
These sound like things that could easily be said of any programming language -- anything in particular that makes TCL stand out? Pretty much all the useful features of TCL already exist in other modern (better) languages...

Why do you like TCL more than any other language (ex. Python, Lisp, etc)?
Microsoft Windows 10 review
Yes. Over the years we have worked on projects that would reduce the impact of bugs found by this fuzzer. For example we have prevented whole classes of security bugs that this fuzzer would find, which would reduce the priority of fixing them compared to a benign crash.
I have no idea what I'm doing
After driving a forklift for a few years I've decided I want to be a linux system administrator, I'm broke what do I do from here?
Yea, it looks like a useful tool to provide support while following the warnings:

Warning: Not suitable for children under 36 months
Warning: Only to be used in water in which the child is within its depth and under adult supervision
Warning: To be used under the direct supervision of an adult

I don't think it's a mistake that "under adult supervision" is said twice.
They also don't actually have any weapons.
Ask HN: What would it take to build my own laptop from scratch?
Note up front: this is much more of a curiosity thing, unless it turns out to be surprisingly realistic to put together my own.

I'm curious what it would take to put together a laptop from scratch, from start to finish, and an estimate of the cost to build a one-off custom laptop. I realize that this is incredibly broad (perhaps too much so?). The conventional wisdom is that building your own desktop is cheaper than buying a pre-built workstation, and more practical because you can spec it to exactly your needs and not pay for what you don't want. The conventional wisdom with laptops is that it is impractical to put one together on your own, so you're stuck paying for whatever comes included with what you need.

One thought that occurs to me (but I don't want to limit the conversation to just this) would be to hack together a frame around a Raspberry Pi-esque SoC with a screen. What would peripherals cost around one of these?
Curious: what camp in New England?
And on what do you base that statement?
Flexbox makes web development bearable. I use it for all my new work. Telling clients they must have IE11, Chrome, or Firefox ceased to be an issue many moons ago. It means you can also drop bloated frameworks like Bootstrap (and JQuery for that matter).
There are 27 videos in the series.
I've seen far worse, but if anything, this demonstrates just how far the Series A has fallen in today's market. A couple of examples:

"Series A Financials" (slide 14) shows a lot of money going out, but doesn't detail how the founders think about money coming in.

"Risk & Mitigations" (slide 16) is really lacking for a $10 million Series A raise, particularly one that involves setting up a new bank. "It takes longer to ship our software"/"speed up engineering hiring" is particularly amusing if you've been in software development for any length of time. "If we can't find the right people"/"work with headhunters and use contractors, as needed" will be equally amusing to anyone who has had to hire in today's market.
No confusion. Hickey seems to strongly dislike mutating shared state. Go doesn't care so much as to enforce that in the language. Hickey is in favor of clear multi-tasking conventions, but go code can do it many ways.
This is the most significant talk I've ever watched, this man has inspired me to explore fields I never would have. I've first watched a talk of his a year ago, I'm still not done reading up on all the interesting content he links to. He pretty much changed my perspective on the field significantly. Am extremely glad I found his content so early in life.

Extremely significant stuff.