skysight-inc/HackerNews huggingface dataset:
I really appreciate this kind of commit message. There’s some very good ones in the Mercurial logs too:

https://www.mercurial-scm.org/repo/hg/rev/3764330f76a6

https://www.mercurial-scm.org/repo/hg/rev/93486cc46125

https://www.mercurial-scm.org/repo/hg/rev/b7a966ce89ed

https://www.mercurial-scm.org/repo/hg/rev/4a0d0616c47d (all modesty aside)

Long commit messages aren’t that atypical. Have a stroll through the logs:

https://www.mercurial-scm.org/repo/hg/log?style=gitweb

Mercurial inherited this style of commit messages from Linux email-based code review (the Mercurial originator was a kernel hacker), because in that workflow your commit messages are kind of a persuasive essay for why your commit should be accepted. I believe that writing commit messages with that kind of goal in mind, thinking “why should you take this commit?” is a good motivator for writing something good and useful.
It's an arms race where people keep breaking into a specific version, Apple makes it harder, and nobody can get into the new shit for a while. There was a method for the X (dunno if updates have made it harder), but not for anything more recent AFAIK. I bet we see another one drop in the next couple years. It's just an engineering problem.
Currencies are systems of value exchange. It is the reason why the term is derived from the word "current" as in a river's current because if you follow the exchange of money over the domain of a given money, eg. the US Dollar, you see its "current" or flow as units of money are traded between customers, retailers, banks and exchanges. A currency is defined by the domain of its value in relation to other currency and its exchange. Money is a "mostly" static value, this dollar is worth this much bread. Currency is an algebra of the domain of money measured over the economy of that money's exchanges including the changes in inflation in relation to the money value of a dollar in relation to bread.
>I am guessing that the warehouse workers don't read "seattle-chatter" mailing lists or have lunch-area coffee to complain about.

They do at least get the coffee, and it's awful as expected.
I don't ask my team to track their time. I also don't require estimates in the ticket. I imagine this doesn't scale past a certain size but for us (8 people) it's worked out well.
Didn't they mention that they sampled only 5 minutes of heartbeats per patient? That would be n=1633, assuming a heart rate of 60.
This comment comes across really mean and judgmental. I didn’t read all of the original commit, but it read to me as informative and passionate with all of the frustrations solving a difficult problem comes with.

Honestly, this comment is so over the top I can’t even detect whether you’re serious or not.
I really like his licensing model, specially the META license: https://github.com/pjreddie/darknet/blob/master/LICENSE.meta
The contrast between hiring at a FAANG sized company and an early stage startup is worth underlining.

If you are big enough, you are basically looking for some level of fit and talent, and to avoid bad hires. It's hard to get right still, but it's basically a crank you turn all the time at a rate to fill your growth/turnover.

When you are hiring early stage, especially for the initial team it isn't the same at all. You have overall goals for the team but nothing is really fixed yet. Lots of the time you may be looking at three good candidates, A/B/C but reasoning along the lines of I can hire A & C, or B & C, but not A & B. B & C might not work. But B is strongest candidate, do I look for a D?

At the very early stage of hiring nearly every hire can change what you are looking for "next". And if multiple people have hiring authority, you can end up having this conversation: "We just hired X, they are great and we didn't want to miss to opportunity. Maybe they're a better fit for your team though?" It sounds stupid but happens quite often in the crazy first months/years of a startup.
Seems stupid that Amazon offers in-house care and when this guy was complaining about chest pains, only to die a week later of a heart attack, that Amazon didn't provide proper care at this point. If they are going to offer an in-house clinic, they need to staff it and run it like a real clinic. That, or don't fucking offer it and make people go off-site to a real clinic when they have problems. This is pretty simple and it's the most vulnerable angle for Amazon here, not "poor treatment of workers" which is very subjective.
Almost certainly they detected the earthquake and decided not to notify people because it was too small to warrant a notification.
As far as I know, you don't need to stop consuming dairy it can happen gradually as you are consuming it too over the course of your life.

It's not an all or nothing thing, there are several degrees to it. Some people will end up in the hospital, others with only sporadic digestive issues not that troubling at first, etc.
99% of the time you can forget about them, but when you get performance problems then you need to start digging in to what goes on behind the scenes.
It is a luxury item. In the UK dairy and meat get subsidised. A pack of sausages cost the same as a red pepper. Go figure!

At the same time farmers here moan that they aren't getting enough money per pint. They are at a loss.

Meanwhile some luxury oat milk costs £1.80 a litre. The plant milks are a nightmare when you consider transportation. Be nicer to have local bottling of these alternatives. At least traditionally dairy farms were a little more localised and smaller.
Number 4 is one of the main reasons I went the self-employment route and will never ever again apply for a real job.

My confidence is what counts for me. Why do you think that your confidence in me counts? I am not going to make myself dependent on somebody else's confidence.

No offence meant, but no, just not.
There are a lot of factors for sure but I think transactional employees would be less impacted by the bullshit because they are less exposed to it due to their not socializing as much during or after working hours.

Depending on experience, I would also expect them to be better at identifying potential bullshit and to be motivated to resolve uncertainty and ambiguity earlier in a process so that they can avoid working unnecessarily long hours.
>Amazon barely makes any profit, you may have heard.

Um... no. Accounting and tax wise, sure. But reality, no. If you dividend out all your "profit" before quarterlies to exec wages, you didn't make a profit. Amazon invested all profits into expansion. Thus, no profit. But they do make "a profit". These are the simple methods of not paying taxes. Tax dodging. It's a brand new thing. No one has ever done it before, let me tell ya'. There are better loopholes out there. I'd use the technical terms, but you're also under the illusion that Amazon is a non-profit. Might as well not bother.

>Considering how many blind spots their warehouses

He collapsed on camera. That's the opposite of a blind spot.

> the most perfectly humane company could easily have.

Misplaced item viewed on camera, 2 minute response time.

Collapse on camera, 20+ minute response time.

If they responded in the same amount of time as the item mistake, he literally could have survived the heart attack.
Coming soon a static site generator generator framework.
Okay, then why aren't all these workers quitting their hated jobs in droves? Why would they care if they get fired, when they can just get another, even better job? If there were better jobs readily available to them, then Amazon would have no power over these workers.
So first clarification is that heart failure != heart attack. Heart failure is a chronic condition where the heart is unable to pump hard enough to keep blood flowing through the body. Typically results in blood pooling in the leg, shortness of breath, etc.

The study avoids the obvious pitfall, which is to put different slices of one patient's data into both training and test. The press also reports the training accuracy (100%) when the test accuracy/sensitivity/precision metrics are all at around 98%.

Another encouraging sign is that when you dig into the 2% error rate, a majority of those errors turned out to be mislabeled data.

The study also acknowledges the following:

"Our study must also be seen in light of its limitations... First the CHF subjects used in this study suffer from severe CHF only...could yield less accurate results for milder CHF."

I think this is a good proof of concept but that the severe CHF and tiny sample size (33 patients) means that we're a long ways away from clinical usage.
Are you paraphrasing ESR paraphrasing Greenspun's Tenth Rule of Programming?

"Any sufficiently complicated C or Fortran program contains an ad-hoc, informally-specified bug-ridden slow implementation of half of Common Lisp."

Ref: http://philip.greenspun.com/research/

P.S. This is not a comment on TFA. Congratulations to the author on making Python even more interactive.
30 seconds to grab an item off a shelf in a huge warehouse, wrap it, put put in a box, tape the box shut, print and attach a label, load it on a truck, and complete all the required tracking steps? And we still haven't accounted for managing all these people, cleaning the warehouse, or even stocking the shelves.

Edit: CNN says it takes a minute of human labor as of 2016 (https://money.cnn.com/2016/10/06/technology/amazon-warehouse...). And that's shelf to delivery truck, so there is plenty more in that process that it leaves out.
And the hot side of the unit goes where?
So offsides syntax errors like Python. But immutable instead of arbitrarily dependent on context. Seems simpler and more modular to be able to look at a line of code and determine if the whitespace is correct.
GPS could be augmented by a ground-based system.

Similar to how WAAS works for aircraft, it's GPS plus a ground "enhancer".
It's just Europol publicity stunt. I thought the idea was cool but the execution lacking : the UX is sub-par imo.
Conceptual overviews
That still says nothing about the relative amounts. Are they comparable to the ones in cheese?
Hmm, kinda like when it's so cold outside and bars and night clubs heat outside areas with propane-burning patio heaters.

The fuss and how this is causing climate change can be mitigated with a simple solution: nuclear energy.
Darknet: Open-Source Neural Networks in C
Around 45 to 50 years old, systems administrator, who had a heart attack. Did some work in the server room, but nothing strenuous as far as I know. I've worked in a number of buildings with 4 to 7 K employees, and with that large a population, heart attacks and strokes happen. People also have mental breakdowns, although they are usually not dangerous. Smaller locations with 50 to 100 young employees probably never experience it.
What do you think most factory farmed crops are used for?
At last! I wanted to write something like this myself, only I identified two types so far: tutorials and reference. Lots of projects only have reference docs, some only have tutorials. Using one instead of the other is a pain. Having at least these two would be splendid for most projects.

My ‘favorite’ example (in the bad sense of ‘favorite’) is Ansible, which had only tutorial docs for its YAML-based programming language―which they didn't want to recognize as a programming language. As a result, whenever I needed to look up some feature, I had to guess where in the tutorials it's likely to be introduced. Notably, plenty of important details are delivered as side notes sprinkled liberally all over the tutorial.

(This was the situation with Ansible a couple years ago, something may have changed since.)
Mapel: Multi-Agent Pursuer-Evader Learning Using Situation Report
>I was sort of hoping that every item I order on amazon has only perhaps 30 seconds of human time going into it

Oh sweet summer child, no. Humans drive the truck to the FC, humans unload the truck and stack the pallets, humans move the pallets, humans unstack the pallets for the stowers, humans stow the goods, humans pick the goods, humans pack the goods, humans deliver the goods. Actual automation is limited only to what is cost-effective, and human labor is more cost effective than automation in most cases.
Agreed. When at some point the website that they are pointing to changes in the future they will lose all context on why a change was made.

I believe in the "plane flying across the ocean without WiFi test" or basically anywhere without Internet access. If I am on a plane flying across the ocean without WiFi, do I have the information in the git commit to understand what happened. A git message that consists entirely of a link to a website is useless in that case.
The weird thing to me was not just the delayed response by 20 minutes (reportedly), but that everyone was forced to get back to work. It just illuminates this very impersonal atmosphere bordering on the inhumane.

I'm wondering if this opens up Amazon to more regulatory scrutiny, or even punitive settlements in the future. Something like this seems like actual evidence for very negative patterns of behavior.

This seems like a new kind of "hostile workplace environment" - one where your workplace will ignore your medical needs if an accident occurs. I just wonder if this is just some older pattern that's repeating itself, it's just not widely known.
>Then assume the drones depreciate to zero in three years

I'm not entirely sure you can make this assumption. Other than the battery, which would have to be replaced in 3 years, the rest of the electronics should hold up as it's just consumer grade smartphone parts.

I guess the electric motors would be a strong replacement contender, but even then if you are buying in bulk it shouldn't hurt the budget too much.

Maybe I'm applying my hobby perspective to the industrial world, but I don't really see a drone as "broken" until it suffers a gnarly crash that breaks the frame. Everything until then can be swapped out in a few minutes, and even if the frame breaks you can transplant the rest of it to another frame. It's not like the smartphone world where everything is soldered shut to save space.
There's no ethical consumption of food when there's a population of 7B+ to feed
If anyone wants a trip down the memory lane, http://www.xwinman.org/ is still up.

A long, long time ago -- but still quite some time after it stopped being (too) regularly maintained -- I emailed Matt Chapman to ask him to include my WM in the list. He never answered, thank God, that was my first piece of non-trivial X11 code and it was absolutely gruesome, I don't know what the hell I was thinking.
NVIDIA Jetson Nano wins the edge device comparison
This is not whataboutism. Whataboutism involves failing to address the argument, and instead redirecting to a supposedly worse situation.

The parent comment has addressed the argument; in 5 of the 12 no one died. That makes the list farcical for a supposed "top most dangerous" list. The rest of the article may be valid. Personally, I don't know. I don't know anything about the layout of the inside of those warehouses, or how common it would be for a worker to go 20 minutes without seeing someone else.

I don't fully understand putting the blame on Amazon. If someone saw him collapse and ignored it, sure. I'm fairly doubtful that's what occurred, it would take an extreme level of callousness from several people to have done that. There's no info around what he was doing when he collapsed; everyone seems to assume he was in the exact same spot as that anecdote where management noticed a mistake in 2 minutes. Does it seem impossible that he felt light headed and was heading towards that AmCare facility when he lost consciousness? Or between stations or something?

This just doesn't seem that foreign to me. Lots of people work in jobs where they could conceivably pass out for 20 minutes without anyone noticing. Security workers on patrol, bartenders during slow shifts, home lawncare people, home cleaning people (if they clean while you're gone).

I'm not arguing that the working conditions at Amazon are anything other than abysmal, but this doesn't seem like a legitimate reason to be angry at Amazon.

The bit about AmCare not sending him to the hospital when he complained of chest pains and a headache is very damning, though. I'm curious if that opens them up to liability. I was under the impression that as soon as someone says the words "chest pain" you're supposed to call 911 and get them an ambulance.

I am not employed by or paid by Amazon.
In addition to this (and going a bit off topic). I've been adding checklists to Github PR templates (it's really easy[1]) for things like, "Did you re-read the relevant API docs? Do they need to be changed?" and it helps me a ton.

[1] https://help.github.com/en/articles/creating-a-pull-request-...
That reminds me of Windows Phone.
Climate change, scarcity of drinking water, oil losing its intrinsic value, endless conflicts. The Middle East is in for a wild ride.
I went to both Hugo and Jekyll sites. I did not see an explanation. Maybe I will try to build something and then I will understand.
>> Even if objects are perfectly encapsulated, with enough complexity, because other objects will depend on that information, ...

I would argue that when other objects from different parts of the code depend on the same state and there is no clear hierarchy or data flow direction between those objects, then that is going to cause problems regardless of whether the language is OOP or FP. The problems will manifest themselves in different ways but it will be messy and difficult to debug in either case (FP or OOP) because this is an architectural problem and not a programming problem. It will require a refactoring.

OOP helps to reduce architectural problems like this because it encourages developers to break logic up into modules which have distinct, non-overlapping concerns.
I'm glad my near-exact pain has been experienced by others. I had an undefined function call of ' ' in a ruby script years ago. Finally, I turned to a hex editor at the suggestion of a colleague. The culprit was non-ascii whitespace that ruby decided should be a function declaration. Copy pasta error out of a hipchat code snippet.
How to define TypeScript types for process.env to have auto-completion
Take a nosey at Slaughterbots, a fictional 7min video;
https://www.youtube.com/watch?v=9CO6M2HsoIA
This is the one I've been using to good effect: https://github.com/IgnoredAmbience/yahoo-group-archiver

no Mongo database required, just plain old .eml files

You do need to pull some cookie values out for the authentication to work, and the Readme is pretty sparse, but it does work.
This message says much more about the author than it does about the commit.
The Marshall Plan was a huge carrot, but came 4 years after Bretton Woods (which implies that Bretton Woods was not enough - or at least, not fast enough).

Also, the fact that the US had more soldiers in Britain than Britain did was a huge fact in their inability to keep the Empire together. I agree completely that the Indians wanted independence, but the sheer might of the US limited the British ability to hold on to it. In fact, the Suez crisis just a handful of years later (1956) demonstrably showed that the Americans were going to get what they wanted when they did not back the British takeover of the canal.

That being said, it is a very complicated picture, and all of these clearly were contributing factors.

Had the US not had all the money (good point, btw), and the European powers infrastructure not been so damaged, the negotiations would have been very different. At least, that's what I believe. For instance, the ability of countries to set up import tariffs, while exporting to the US without tariffs clearly supported lower cost labor, which the colonies had in spades. That gave the colonies more power to fight off their weakened colonial masters. That shift in power came at the most inopportune time for them - while they were capital poor and rebuilding.

Keynes was a mountain of a man, but the US could not afford to let him run the show - as with any display of power, that's just not done. Even though Keynes may have been right about some aspects, the US had reason to distrust the Brits, as the US clearly knew the Brits would not give up their hegemonic place unless the US took it firmly. Under that thinking, the US was smart to shunt Keynes off to the corners (despite his huge influence). I think that the Suez Crisis showed that the Americans took the right approach here.

Excellent conversation - I love to see the vast knowledge of folks like you on HN !
As a practicing technical writer I can testify that these content types are a common way to organize your documentation collection and identify gaps.

It’s a useful exercise to list each doc as a row in a spreadsheet, and then mark whether each doc is a tutorial, guide, conceptual overview, or reference, or a confused combination. Many times you’ll see that you have explained how feature A works but have no tutorial that shows how to use feature A, or vice versa.
The author seems highly irresponsible. You don't just play around with mushrooms that you pick yourself from the woods - and you especially not cook / eat them, without double / triple checking them. When you are in doubt - you simply avoid eating them and taking risks.
What happened to him is 100% his fault and was easily avoidable, I cannot have sympathy for that.
It's batshit crazy to ask workers to "sacrifice" for their job. Unless they're co-owners. Talking 5%, minimum, of the company, and even that seems low to me to start asking for ownership-level commitment, which is to say anything at all beyond what any normal job would reasonably expect. Otherwise you're just taking advantage of people. Congratulations, you're an asshole.
Thanks for sharing this guide. It's fitting like a ring to finger as I am in the process of setting up documentation for the features of my app [1] because I realized that as an early-stage startup one of the best ways to teach your users how to use your product is by writing great documentation. I'm finishing the setup of this site within my landing now using Gatsby, on the main domain, so that it can also help to bring in more traffic from search engines.

On the same topic, today I was listening to a podcast [2] titled "Getting traffic to a new website without blogging" which is excelent to match using Divio's guide.

[1] https://standups.io

[2] https://podcasts.apple.com/us/podcast/episode-344-getting-tr...
On a related note “Last year in Beijing, during a heatwave, 50% of the power capacity was going to air conditioning”

https://www.theguardian.com/environment/2019/aug/29/the-air-...
It would be cool to have a documentation style that embeds reference in the tutorial à la Tufte notes.
How do you surface them when you need them, though? git grep?
Ah thanks for the explanation.
Up into the atmosphere, presumably.
...In addition to: Intel x86 (including 8086), AMD64/x86-64, PowerPC, PowerPC64, SPARC, ARM, AArch64, MIPS and the JVM. Supported operating systems include Linux, FreeBSD, Haiku, Mac OS X/iOS/iPhoneSimulator/Darwin, DOS (16 and 32 bit), Win32, Win64, WinCE, OS/2, MorphOS, Nintendo GBA, Nintendo DS, Nintendo Wii, Android, AIX and AROS...
IMO the repo is the code

However, I would have done a simpler commit and linked to an issue where I explained the problem/solution in more detail
While it’s always a difficult moral quandary to sort out the ethics of a given employer, there are plenty of opportunities in the software world that won’t make you complicit in treating working class people the way that Amazon does:

https://bits.blogs.nytimes.com/2011/09/19/inside-amazons-ver...

https://nypost.com/2018/04/16/amazon-warehouse-workers-pee-i...

https://www.theverge.com/2019/4/25/18516004/amazon-warehouse...

https://www.independent.co.uk/news/world/europe/amazon-used-...

https://www.ft.com/content/b0c22a35-f553-39ec-8b89-d5986d02b...
That was back in July. I'm genuinely curious to know how many of those employees that showed solidarity are still employed by Amazon today?