skysight-inc/HackerNews huggingface dataset:
I wonder if the shock of going from a first world country to a third world country contributes to these problems.

Imagine for a second you're a white male growing up in rural America. Your first experience with the rest of world is a Iraq...

It must be traumatizing.
You're implying that minimum following distance <= stopping distance. A brief Google search yields a stopping distance of 315 feet for travel speed of 70 mph.[0] We don't train drivers to leave a football field of space in between cars traveling at highway speed. At least where I live, the legal standard for minimum following distance is that a driver "shall not follow another vehicle more closely than is reasonable and prudent".

If Driver #3 can't see Car #1 past Car #2, and Car #2 is traveling at highway speed, I think it's a stretch to say that Driver #3 could be faulted.

[0] http://www.driveandstayalive.com/stopping-distances/
Definitely a valid approach. Usually people digging for historic non-merged requests will still find the closed requests either in Google or GitHub search, so I close them by default just to keep open PRs more focused.
I can't comment on Google's culture, but:

>Design documents turn every feature into a half-assed, lowest-common-denominator risk-minimized shell of itself.

Sounds like a sentence written by someone who is an engineer and not a support staff or a user, i.e the people who have to deal with the fallout of every feature change and every engineering decision. I could just as easily substitute "feature driven design" into most of your points above.

Requiring someone to put thought into the design of a product and to subject that thought to rigorous scrutiny is, on the whole, a good thing. One that leads to products end users want to use.
NFS on Linux defaulted to UDP for what seems like a really long time. There were perf issues with TCP (can't remember what they were).
https://crates.io/crates/rusoto is one of the bigger AWS SDK crates. There's been some interest in Rust on Lambda, but I forget if there's a tutorial or something.
Well, I usually say that it needs tests, and in my crowd that's equivalent. :-/
Moonlighting managers ain’t got no time for bullshit
While I agree on that I think the point of the parent was that No Man's Sky would never have been created if it was designer first.
I work on many things for software projects for my own personal gain. I don't particularly care if someone is planning to do something similar in the future. I need this thing now, for whatever project I'm currently doing.

I implement it, and sometimes I may send a PR to see if the maintainer wants it. I don't particularly care if it gets accepted or not. However I think giving them the option to pull if they want it, is a good idea.
I'm here now... had to put my kids to bed; some nights it takes an hour or two (nights when all three act like the Tasmanian devil!).

It's fixed now :)
These guys are always hiring for the same position. Either they're too picky or people end up leaving once they join.
That's pretty much the best scenario, I think. If you won't be offended by the fact that I may not consider the PR appropriate for the codebase, I appreciate the time you took to post it for consideration (and thank you!).
Sure! Sent!
TL;DR everyone expected an IPC increase with Kaby Lake and Intel brought more performance only via higher clocks. They're either having issues innovating, betting that Ryzen will not be all AMD is talking it up to be, they're a bit caught with their pants down, or some combination. IMO worst-case for them is they push Coffee Lake and Skylake-X out sooner and drop prices across the board (especially on HEDT >4 core stuff) to compete with AMD.

Then once enthusiasts have access to <$2k PCs with 8 cores and the power of 2x1080GTX we can realistically power 4K VR @120FPS. Having games to actually make people want VR would also really help, so far not many AAA titles to use with it.
also another tip -- you can click on the city name in the left corner to load the same view in google earth (if you are curious about what you are looking at!)
There were versioning file systems in the 1960s (MIT's ITS among them, and I think Univac's EXEC 8, though I can't find a reference) [1]. Often, new writes to a file bumped a version (or cycle) count in the file system. I don't know, but I wouldn't be surprised if there were tools to do diffing and patching much like modern VCS systems.

[1] https://en.wikipedia.org/wiki/Versioning_file_system
> Within 24 hours after first launching the game

That also doesn't seem to fit within Consumer Law... We'll see how long it takes for this one to come up.
Cool beans thought so but wanted to be sure before I blew that much money. :)
If you do the obvious work to convert UDP to a reliable streaming mechanism, you will generally more-or-less reinvent TCP, only probably more poorly, and would probably be better off just using TCP. UDP is a good choice when you have options or requirements that TCP can't accommodate. For instance, the classic case of streaming audio has both; it both requires timely delivery and has some very sophisticated techniques for dealing with missing packets with a lot of local intelligence about human perception and such built into the codecs. If you can drop packets without issue, if future packets completely supercede past packets (FPS network gaming for instance), there's a lot of possibilities, but if you're just going to recreate reliable streaming you probably be net losing on account of the effort spent doing that instead of something useful, and bugs in the implementation.
I was wondering how did SUV rolled because for that to happen you need force getting applied on car that is on Y axis (the +X axis being the forward direction) which will ultimately produce the torque causing the roll. After looking at video at low speed, here's how we got that force vector:

1. Hatchback hits on tangent producing torque and spinning SUV by 90-degree.

2. SUV collides with barrier which produces force vector that is normal to collision surfaces and slightly off forward direction.

3. The driver now seems to have pressed on breaks really hard which produces another force vector. But this vector is now quite off original forward direction because car had been rotating.

So the moral of the story is that if SUV is rotating and you press on breaks really hard, you will get roll. This is purely because SUV has higher clearance and so even small force can produce enough torque that will cause roll. It looks to me if driver hadn't pressed on breaks really hard, the rolls could possibly been avoided or reduced.
> I always wondered why nobody used UDP for bulk data transfer

That would be odd. It's not true. There's TFTP all the way up to UDT.
I'm reading van der Kolk's best-selling book on trauma right now - The Body Keeps the Score [1]. It's good. My therapist recommended it to me as the best book on trauma out there right now. Lots of good, current research, his personal experiences actually healing trauma, and hope that people can get better. My wife has PTSD (veterinary school and previous relationships) so I'm trying to understand, and it's helping.

[1] https://www.amazon.com/Body-Keeps-Score-Healing-Trauma/dp/01...
in a way that forces you to type a PIN into the phone rather than the other way around

Could you explain more what you mean by this? Presumably it's not typing a phone into a PIN...?
It's very common for netflow data to be mirrored and multiplexed. Syslog, too.
Neoclassical synthesis is still taught because, even though it's flawed, we have nothing better. Economists know that the assumptions behind neoclassical models aren't always fulfilled.

All science is always done with models and we just use the best models we have, while taking into account their limitations. People don't usually object to this in other fields, but in economics they do because they have stronger Opinions about economics than the natural sciences and the models sometimes disagree with their Opinions. If they had a better model, economists would welcome it, I'm sure, but they don't and they still want to keep their Opinions, so instead they blabber about how the current models are flawed. They're not wrong.

The Marxian school is a dead end and the Austrian school lacks scientific rigor. There's no point in teaching along with neoclassical synthesis things that are less rigorous than neoclassical synthesis while also having less breadth. If they were taught, the situation would be similar to what it is in psychology, where dubious approaches like psychoanalysis are taught alongside cognitive psychology.
not one person, a group acting without concern for the individual. sacrifice, die for the greater good. turn the enemy's strength against them.
> Sounds like a sentence written by someone who is an engineer and not a support staff or a user

Do support staff and users sign off on design documents? "No" is the universal answer. Are you claiming that engineers aren't reasonable human beings who can take support staff and user concerns into account on their own? What makes you think the people reviewing design documents can do that?

Is it that you just trust a subset of engineers to understand the big picture? Are most engineers just drones? You shouldn't hire people who don't give enough of a shit to take the big picture into account.

I am an engineer. I am also a user. I do support my software. I've been programming for twenty years. I find that "rigorous scrutiny" hurts more often than it helps. Maybe this rigid scrutiny was more appropriate in a world with release cycles measured in years, but we don't live in that world anymore. When you ship every week, you can easily undo mistakes, and you're better off erring toward iteration.
I was quite surprised to learn about the attr function [0] that allows you to query the selected element's attributes, but it's actually been around for a while now and is supported by most (/ all?) browsers. Pretty nifty.

[0] https://developer.mozilla.org/en-US/docs/Web/CSS/attr
Debbie Reynolds has dies at 84, day after the death of daughter Carrie Fisher
The Global Assassination Grid [video]
DNS strikes me as something relatively painless to deprioritize. Small packets, not all that latency-sensitive for most use cases.
Where would you place "Elements of Statistical Learning" in relation to these, if you know?
Is Nick Fury onboard with this?
> Sanitizers aren't part of ANSI C.

Nobody claimed that they were. I only mentioned that there are C implementations that protect against these kinds of things in the runtime and that the standard does not force the implementation to not do any checks.

> Besides, gcc and clang are just two of many C compilers.

The reason that I mentioned them was because they are two most popular ones.
There's probably not much preventing a society similar to what you describe from arising. I've had some thoughts regarding this, in no particular order;

- Surplus non-elite human stock will be used for mass colonisation of solar system/extrasolar bodies where mortality is high (aside: and possibly beneficial, in terms of accelerated evolution due to reduced reproduction cycles).

- The elite/AI cabal at the top will subject the unknowing masses to physiological and psychological experimentation for their own ends. (this one is probably already happening :)

- A mass uprising of the disaffected non-elites will enforce some kind of Butlerian Jihad (it's just a union to keep the AIs out!).

- Elites will be benevolent overlords who take their stewardship of the species seriously, and we all live blissfully in massive space-elevator-anchored orbiting ring habitats with UBI and free soylent, while the mysteries of the universe are probed until the end of time.
I don't think you can be a developer in 8 - 12 weeks, as mentioned in this article. Software Development is a skill as much as anything else, and there is no time frame. All you can use to assure yourself is if you have practice, and the confidence in yourself by that practice. For some people that confidence comes after a year, maybe even two years. But then again, that confidence can even come in 2 months.
as long as you use headers, it has a button that does it in one click? (The only part is you have to make sure to keep it up to date manually)
I'm pursuing my lifelong quest for the perfect, the absolutely driest martini to be found in this or any other world. And I think I may have hit upon the perfect formula. You pour six jiggers of gin, and you drink it while staring at a picture of Lorenzo Schwartz, the inventor of vermouth - Alan Alda as the character of Hawkeye Pierce
I'm....skeptical.

https://queue.acm.org/detail.cfm?id=2655736
Native C++ references are technically unsafe, so code that uses them would not qualify as "strict" SaferCPlusPlus code. In the case of your example, the "double&" is technically not kosher. The easiest way to make it safe would probably be to use a (safe) iterator instead of a native reference. So instead of

double& dangling = data[0];

you could make it

auto not_dangling_iter = data.begin();
// not_dangling_iter += 0;

C++ references are the one unsafe element that does not have a "compatible" safe replacement. Unfortunately, you have to convert your references to pointers (or iterators). I don't think there is a way to create a "safe" reference with an interface compatible with native references. Apparently C++ will at some point add the ability to overload the dot operator, but I'm not sure that will be enough to be able to emulate C++ references.

And while I can overload the & (address of) operator to "prevent" you from getting a native pointer to a "safe" object, I don't know if there's a way to prevent you from getting a native reference. If you wanted to somehow enforce a prohibition on the use of unsafe C++ elements (like references), that would probably require some sort of static tool that is not yet available. But should be fairly straightforward to implement, I think.

But if you just want some confidence in the safety of the code you write, it doesn't take much effort to reliably avoid using C++'s unsafe elements.
To agree with the GP, I've had dozens of people come up to me and ask me for a recommendation on what to buy "to make things with hardware". That's literally their description, and how much they know about the subject. The answer to that is "the WeMos D1 mini"

Not once has someone asked me "what are various boards I can use if I want to program the ESP8266?". Literally zero times have I met someone who would know what to pick between all the different options and didn't know the term to search for on eBay.
We just don't have many institutions left in the us to care for people after trauma, and the few we have are as impersonal as possible. It's hard to come back to ones family after seeing terrible things. Honestly I can't help but feel that the lack of community in modern life tends to exacerbate all these problems. If you don't know your neighbors there can be little to latch onto other than places and things. The image from the Hurt Locker of the guy meandering through the grocery store comes to mind. What is all this excess for, when there's such suffering happening in the world?
>Requiring permission to do work is the enemy of progress and engineering dignity. It creates a presumption of incompetence and an atmosphere of low trust that punishes people who want to push the envelope of what's possible.

Its not a permission to do work, its permission to merge the results of the work to master. Those are different.

>Google's design document culture is bad.

Then why do we have JEPs, PEPs, and rfcs in perhaps every other major project out there?
>I'm of the opinion that there is an infinite amount of jobs; as we as a species always want our current situation to be better than it currently is

One of the unspoken problems with the tech revolution is that there are a lot of people who are simply not smart.

Remember, that for every genius, for every "above average" guy, there's the guy who's below average, a bit slow.

Until 1960s, you could be the hotshot lawyer, doctor, scientist, businessman or engineer, or you could work as a farmer, factory worker, tailor or water-carrier.

In a few years/decades, one will need outright brilliance to find jobs.
Here is a nice article about dev board comparisons.

http://frightanic.com/iot/comparison-of-esp8266-nodemcu-deve...

wemos has a smaller form factor, but lacks breakout, has the ch34 and is headless so maybe not suitable for beginners like i think of the nodemcu.

edit: also I'd like to add that the nodemcu and sparkfun thing already have a esp32 upgrade available where the wemos has not.

But hey, just my opinion.
well a lot of people may realize they don't really have a design, but will think that they can build one up as they work
Would love to get this as a daily newsletter.
Had a similar issue on a galaxy s4 in cold weather (particularly when launching the camera app). The battery was ~3+ years old though.

After doing several hours research into buying a new phone (iphones and androids), I settled for now on upgrading the battery in my old phone to a larger 5200 mAh battery. It introduces a slight bulge, but after the first few weeks I've been extremely happy so far. The phone works 2 days under heavy use, 3+ under light use, and changed how I perceive it - essentially I don't think about charging during the day anymore, and don't worry about remembering to charge at night / while catching up on news in bed.

My assumption is that this is a better solution because it's drawing current from more cells in parallel, meaning less strain on the battery itself (there's an equation for this, but basically more current on individual cells drains a battery's capacity exponentially faster). It's also one less thing to think about carrying compared to carrying a separate usb charger.

I'm hoping there's still going to be phones with removable batteries to enable larger 3rd party ones to be installed, or that 'smart battery packs' on the iphone or moto z someday allow for current sharing between the internal+addon batteries.
this is a write up of a year of doing code based sketches -- last year I started to do a sketch per day here:

https://www.instagram.com/zach.lieberman/

I am happy to answer any questions about this if it's helpful
I think I mentioned this elsewhere: It is not about the exact stat comparison between self driving cars and humans. It is actually about

1) the perceived and real adaptability of humans. (given an 'unknown' situation, what does the machine do?)

2) Non epidemic nature of faults in humans. (one version update bug nuking all teslas - we have seen this happen in software, no reason they can't happen in self driving software)

3. Non epidemic nature of coordinated events in humans (GPS satellites fail or leap seconds occur and suddenly all self driving cars go nuts - usually doesn't happen amongst humans).

4. Ethical decision making concerns from machines which are considered 'cold' and 'calculating' and whether that can be construed as murder. (Would the machine choose to kill the pedestrian family over car's current occupants in a purely two choice scenario?)

5. Degree of 'control' considerations. (Would you enjoy a remote turn off switch that denies you entry to your house / mobility etc.)

6. Anonymity considerations. (That's why money economy is still a thing. Possibility of 3rd party tracking vs. knowing about tracking are two different things).

FWIW, I am not against either situations, I am just collating info :)
We write design docs at Google to communicate ideas with each other. They're useful for promo committees because effective communication between engineers is something that is prerequisite for effective engineering.

Of course a full design doc is not needed for every change. Many changes are small and straightforward. Only big things, where the team needs to discuss and understand options. Or bigger things, where directors etc need to sign off (not really design docs anymore, but same basic thing).

The fact is that, on average, design doc+code takes less time than code without design (that is, without communication). Again, only for certain kinds of changes. Things go faster because problems are found, approaches are adjusted, or unmotivated features are axed.
> ship all the chunks over with a sequential number

Except that if you ship them too fast, they will at best simply build up in a buffer somewhere (e.g. near a bottleneck link), or more likely they will overflow causing many of your packets to be lost. So not only did the recipient not get them (and you have to figure this out and resend them later), but you also wasted a bunch of resources sending packets only to have them dropped.

And if you send them too slow, you are leaving some potential capacity on the table. So you need to send them fast, but not too fast.

So you add some additional logic to implement flow control and congestion control. And that's TCP, pretty much.
Even though I am convinced that the holocaust did happen, I'm not sure that Google should be tweaking their algorithms until they show the results Google wants you to see...
Haskell vs. Ada vs. C++ vs. Awk vs (1994) [pdf]
NFS used to default to UDP for the same reasons that games still would use UDP, it just needed the data as quickly as possible since it was blocking IO. Now a days, we don't need UDP for NFS because networks are a lot faster and the advantages of TCP start to over rule UDP.
What really is Amazon's business model? (2013)
I'm using google chrome, but it doesn't work for me. Suggests using Google Chrome, because webGL. Chrome 55
Thanks to Netflix, my 8-year-old and 5-year-old think it's a good show. It's cheesy, but it's hard for me to get too, err, emotional about it when I compare it to the other things I watched at the same age. (I never did see that when it was out.)

My wife was on the verge of putting the parental veto on it, but the kids moved on to other things. I didn't mind it so much, but the Netflix version has the Legend of Zelda stuff yanked out (presumably licensing issues), which probably helps out overall, as I gather that part of the show was legendarily (pun intended) annoying.
It doesn't really work for general anxiety, but I personally have a lot of physical symptoms of anxiety -- racing heart, tightness in the chest, pain, etc -- which mimic (but aren't) cardiac symptoms. The propranolol (once or twice a day) completely cuts these out. When the psychological symptoms of anxiety are too much, I have Xanax I can take as needed, but that's only every other day or two.

The only drawback is that it can make me a bit more tired, but only if I'm already quite exhausted. Outside of that, it's virtually side-effect free for me.
> I believe SUV's have lower fatalities per mile driven.

I would be interested to know how this compares with other vehicles if 'fatalities per mile driven' included fatalities that involved non-SUV occupants.
What's going to be the value of mass produced art work? Will teens just attend concerts with robots playing guitars? Will kids just give up learning music because a computer can do it ? If that's the case, there's probably not going to be much incentive for people to get out of bed.

The point of creativity is not about money (though people think that's the case), it's really about expression. Sure you can monetize the product, but that's not what happens when people go out dancing together. It's about community, communication and enjoyment.

Besides, who is to say that people wouldn't actually prefer a hand crafted rug created by a master craftsperson? Or watch their daugher play a concert?

We have mass produced rugs in our house now, but if I could afford it, I would have the hand-crafted rug, they're really nice.
Although to be fair, given that with TFTP each packet must be acknowledged before the next one is sent, you're actually achieving a way worse throughput than TCP. Not a very good example on how to use UDP efficiently IMO.