skysight-inc/HackerNews huggingface dataset:
I agree with that too. There needs to be a lot of pure narrative in addition to the auto-collected API Docs. My big project has User Guide (with intro, vision, tutorials and how-tos), Developer guide (with architecture description, requirements specs, implementation overview) and then auto-collected API docs with all the details of how it's currently implemented. In the "notes" admonitions throughout the API docs, there's a some historical information and description of why it is the way it is and how it should ideally be (as appropriate). This feel like it works pretty well. Then again, I wrote a lot of it so I'm biased.

There should be a roadmap somewhere as well, possibly in a Wiki or the developer docs.
Wonder if there's some more ideal way to lay out those so they are less of a tangled web. This graph makes me want an adjacency list.
Contrary to the author's point, I don't think a git commit becomes more beneficial to the readers by adding a human context.

Building "compassion and trust" actually distracts readers from the essence of the commit: what happened and why. I am not discarding the importance of human element in collaborative endeavors but maybe such area should be pursued outside of a version control system.
My ethics expectations of Kaggle competitions
Somewhat relevant: CPU Time Jitter Based Non-Physical True Random Number Generator by Stephan Müller

http://www.chronox.de/jent/doc/CPU-Jitter-NPTRNG.html#toc-Ap...

https://pdfs.semanticscholar.org/af73/17c970fd416646b2e46659...
My personal favorite is one where I actually fixed a bug by flipping one single bit.

https://bazaar.launchpad.net/~rbanffy/maas/bug-1443627-incre...
Show HN: const [err, result] = await Ω (fnThatMayThrowError)
Older technology is probably much simpler though. It might actually be possible to train someone, or for that someone to learn from a manual.
My experience is quite the opposite. I can throw together Haskell code and refactor it much quicker than equivalent C++/Java code. And I have a lot more experience with C++/Java than Haskell.
I'm not religious at all but this is one of my favourite pieces: Erbarme dich, mein Gott https://www.youtube.com/watch?v=BBeXF_lnj_M
hence the "also" in the comment, one imagines.
That list is totally farcical.

There are all sorts of companies (most of them small because you can't do this kind of thing at scale without being sued) that put their employees in actually dangerous situations. There are nursing homes and hospitals that make the untrained janitor clean up bodily fluids (more than just your normal crap on the bathroom wall). There are construction operations where all sorts of safety corners are cut in the name of time. Industrial facilities where the maintenance and repair staff put themselves in danger in order to minimize downtime. Examples like that abound. And then there's all the wage theft (that I'm ignoring because we're talking physical danger here).

I'm not saying Amazon et al don't run their employees as hard as they can get away with but if you're gonna pick a dozen companies that are the worst the ones that are at least in the gray area of complying with the law shouldn't make the list.

Edit "totally" is probably too strong of a word by the general point I'm making stands.

Do any of the down-voters care to explain why they disagree? I'm genuinely curious as to why this is such an unacceptable opinion around here.
I do not share your experience, because in my experience the auto-generated docs will be kept in sync with the code/API while a separate specification will become outdated over time.

This does of course require human-readable description in all the endpoints. But that's the same as only an autogenerated function signature in code documentation vs an added human-readable description.
When reading code, you want somthing simple and to the point most of the time (if that). Yes, it's nice to be able to tunnel down into the details - but this was fixing a bug, the code should just have a short description and more so - the reference number of the bug and if you need to, you can look that up on your bug tracking solution and get that detail.

Big problem with detailed comments, things change and comments (like code) can become obsolete/redundant and not reflect the code as the code got updated, but the ocmment did not.

No solid solution really and gets down to preference and also mindfulness of the life of code/comments.

Would be great to have code that you could rightclick and get the documentation, some woudl even prefer being able to write documentation and that gets turned into code, others would love code that could could be autodocumented. Get's down to taste, preferences and more so, experience. See, every programmer over time will eventually encounter a situation on somebody else's code that they are maintaining, fixing or replacing and find that the comments do not reflect the code. You eventually get down to the stage that you almost actively ignore comments based upon such experiences.

So whilst a detailed description in the form of a comment is good, it can and should be elsewhere, either the initial spec and program documentation or in this instance - bug tracking software system and just simple short line with bug reference or indeed just bug reference.
That is... wonderful. I've spent some time dealing with locales in C and other places that depend on the things being discussed in the commit. Just reading it bring back some of the rage I felt.
Safe as in safe from host interference? Not at all. But if your VM is running on a malicious host, you have bigger problems honestly.
From replies it seems my two sentences weren't as clear as I thought. I'll try to refine it:

A property of bitwise xoring random variable `x` with a constant (or otherwise non-random but independent) value is that the entropy of `x` is preserved in the result.
Good docs take a dedicated tech writer who cares to write them. A passionate dev may or may not be a decent tech writer.
Stopped reading after 2nd photo. Not only distracting, its intelectually insulting. The premise of entire article is.

Must be a chick thing ... :S

https://youtu.be/OgmGzpIs-XU?t=100
Here's some research that suggests sounds are important for slot machine gambling:

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4225056/

Made me wonder what the physical machine equivalent of your idea would be.
We teach them every detail of everything they need to know in their technical school when they come into the military.

Old equipment is actually interesting to work on -- difficult, but interesting. It's also very valuable for understanding modern hardware at a deep level that isn't often taught anymore.

How many people do you know who have actually replaced and aligned the heads on a UYH-3 or run end to end tests on serial data channels that traverse thousands of feet and multiple switchboards from a UYK-43?
A separate specification works much better as long as that specification is also enforced during the build.

A separate openapi spec that is not enforced can quickly become outdated, then an auto-generated from code is better.
I should have added to the title that this is from 2018. Apparently it's a swarm of 2018 drones.

Does anybody know of a blog post where this is explained? In particular, choreographing the movements of the swarm looks terrifyingly hard.
Make them smaller and give them a sharp pointy end. Ask the public to name it. Reject “Stabby McDroneface” as “it sounds like a joke”. Be surprised by the first amateur reproduction. Use the moral outrage to ban all drones — even those tiny little drones that can’t life a single jelly baby. Realise drones are still useful and make and expensive license scheme that doesn’t really scale up because it’s organised with industrial era thinking instead of information era thinking. And what is old is new again.
CO2 is fungible: one CO2 molecule is the same as another.

What I am skeptical of is that the offsets really are preventing an equivalent amount of CO2 from being released elsewhere.
In the scientific community, we talk about how different foundational principles or axioms change the heuristics of physics and that is what this article was about. Convention A leads to Riemannian coordinates and the big bang. Convention B leads to Cartesian coordinates and tired light. There is nothing mystical about Cartesian logic. It was reborn during the enlightenment. When people try to think in Cartesian ways about Riemannian theories, as most people tend to do, trouble arises.
Any stream cipher?

If you use the same symmetric key and nonce, the output bit stream should be the same every time.

This is how OpenBSD's arc4random(3) started out: using the output of RC4 and stirring the entropy pool regularly to ensure forward security. (They've since switched to ChaCha20.)

* https://man.openbsd.org/arc4random.3

Remove the stirring and you've got deterministic output. Security comes from the entropy of the initial conditions.
That’s crazy. Maybe strawberries aren’t as easy to identify as I thought.
A few cubes away from me one of our guys put his head down on his arms on his work surface. No one noticed, but he died. The guys holding a meeting in the cube across the aisle from him felt bad about it, but they thought he was taking a nap.

Any large employer will have people die on the job.
Ask Facebook. They are running Haskell at massive scale.
Not a commit but from the same author, so you may enjoy: https://github.com/wm4/dingleberry-os/blob/master/README.rst

It does go off on a few tangents, but it's an interesting read.
> Each of these travelers, on average, emits more than 3 tons of carbon dioxide per year, a substantial amount,

Conservative estimate puts every person at around 300-500kg CO2 emission by breathing.
Just to put things into perspective.

Ships produce way more emissions then flying.

I really wish they stop producing those misleading articles muddling the water and focus on real polluters.
-Ofast enables fast-math optimizations and generally is not standard compliant. I hope projects do not deliberately enable it without thinking (as they say, it is hard to make stuff fool proof because fools are so resourceful).
I wrote a ton of COBOL (mainframe and MicroFocus COBOL on AIX) back in the day in my early IT career (late 90s, early 2000s) around the Y2K conversion. It was a fun language because you could pick up someone else's code and be productive right away. It was hard (but not impossible) to do things in COBOL that weren't pretty straight forward.

One of the big drawbacks we had though, and this may have changed since, was that COBOL wanted every variable and structure to be fixed length and defined up at the top of the program. So it was not really a good fit for the modern world of the web, JSON, etc. where you don't always know the length or structure of your input in advance. The versions of COBOL we used wouldn't have been able to process a blob of JSON and pull out a particular key for example without having the full JSON structure defined beforehand.

I always joke w/my colleagues that my copy of "COBOL For Dummies" on my bookshelf is as good as my 401k as a retirement plan.
>Actually, it doesn't even matter. I also block Spolsky's image at the table tennis table.

That picture isn't even that bad, the one that shows up in firefox's recently viewed, with him making a creepy smile, is way worse.
If americans could reduce their emissions, that would be a great start. The US emits a lot per capita compared to other countries.

I'm worried that in the future, eco-terrorism might actually become a thing...
Startup Company Action Plan Template
I was there when the name was selected. It turns out "blaze" suggests speed, which is why it was a popular name for other software, and some of it was registered as trademark.
and/or reinvest them according to the team/organization stories.
But it basically only shares the name.
Mark V. Shaney by Rob Pike (1984)
Spoonshot – Your creative spark for early-stage F&B product development
Our bleeding-edge technology combines the power of AI, food science, and large, diverse data sets, to provide you with validated inspiration for future products that will not only be on-trend but ahead of them.

http://www.spoonshot.com
We are focused on chat based automations for agile teams. Our customers are typically product/project managers looking to save time and get better engagement from their team.

https://hiberly.com/ looks cool. It may be interesting for our customers as well. Good luck!
Ironically, i'm now curious about kissgyorgy's life story. How did they get so touchy?
...plus they tend to get outdated and out of sync with the code pretty fast!
You mean Omphalotus olearius and Hygrophoropsis aurantica? First one could be very nasty, maybe not deadly but very painful. Easily possible to confuse with Cantharellus cibarius, See https://www.wemjournal.org/article/S1080-6032(15)00475-5/pdf
Yes indeed but not the way you think. There are many highly experienced developers out there who would love to use Haskell in their day job but currently can't. So your problem will be processing all the highly qualified CV's you will receive.
Just getting my amiga/commodore 64 500 3.5/5.25 setups back up and running, 75% of data is demagnetized away. Looking around sourcing any of these formats is more or less impossible today. HOW did they ever managed to keep 8 inch disks in a read and writable stage, without exhausting possible read/re-writes?

Secondly, how does one replace a 8 inch drive (most likely MFM interfaces) with a solid state disk?
The article makes it quite clear that this is not about people dying like you mentioned, but about delayed medical attention in large Amazon facilities that result in potentially preventable fatalities.
How Does the Browser Execute Asynchronous Code?
It's not a contrived example. I see it all the time in Java codebases, and it drives me mad. I always flag it in code reviews and demand an explanation: "what purpose does this comment serve? What would be unclear if we removed it?".
When I saw your post I thought it would a Mom and Pa farm down the road with 5 cows, but this actually looks like a small (to medium?) size factory farm to me, well marketed.

Those huge structures are I imagine grain silos to store feed -https://www.google.com/search?q=de+backer+family+dairy&rlz=1...:

How many cows do they have? Apparently farms with more than 100 cows make up just 0.3 percent of the total dairy farm population.

You can clearly see that it's a factory-like installation. Are all those people part of the family or full-time employees? I bet several are employees.

At least it does not come from across the world it's local so less impactful.

> use to make the richest ice cream that you’ll ever taste.

The other day I tried one of those plant-based Magnum ice creams, I couldn't tell the difference and actually liked it more.
Yes, something like that would be great! But does it come packaged nicely? So that I can compile it out of the box on windows, linux, macos, android?
I may have been exaggerating about my wife's responsibilities.
agree 100%. I don't know of any truly sustainable farms that don't involve some nonhuman animals in the value chain. The problem is not that industrial farming is less efficient when incorporating animals, it's that we're calculating efficiency in terms of fossil fuels in > Calories out.

There are all sorts of alternatives to that paradigm, but none allow us to compare a single metric for both. The nature of the debate reminds me of the apocryphal drunk, looking for his car keys below the streetlamp even though he knows he didn't lose them there.
No... It's distracting because it doesn't make sense. It's a post about hiring technical staff full of pictures of a woman eating ice cream - it makes no sense. If it was a post about setting up a JavaScript framework filled with pictures of chimpanzees dancing it would be just as distracting.

Also the half-eaten one grossed me out.
> with associated difficulty in finding talented engineers

This is a myth. There are now many experienced developers who currently can't use Haskell in their day job but would love to. If I decided to start another business, picking Haskell would give me access to a lot of top talent who would otherwise not be interested.
Sorry, I misunderstood then. But still, personally I think it's about as relevant as if the post was about dark matter, and someone commented "well, dark chocolate is also quite hard to detect if the fridge light goes off".
My experience has been that having names for things makes it easier to think and communicate about them; including in documentation.

For example, once I learned the term "tail" I no longer had to say "every element except for the first one".

As another example, learning about "complete" versus "partial" functions gave me the vocabulary to better understand and communicate about certain types of errors.

Does anyone know of any resources that describe different types of useful vocabulary such as this?
Exploding chemicals setting things on fire if mishandled (anywhere from factory to actual show). As opposed to small drones falling? (Those are most likely micro-drones)

I think much safer is more precise.
Lets introduce noncompete for companies. If a person who worked at company A is hired by company B then company A is forbidden to compete with company B for 24 months.
Pascal! My favorite language
I think it’s way more often than people think.

I’ve overheard coded conversations by my DEI department about holding off on hiring candidates because the ones they found immediately weren’t “diverse” enough.

Of course, that doesn’t make sense. A single entity can’t be diverse.

Instead, “diverse” is a code word for “not white male.”

Look, I don’t want to work in a boys club, either, but there has to be a better way to do diversity right.

And the thing about hiring is, as long as you don’t say the illegal thing out loud, and you use that coded language, you can do whatever you want.

Not truly illegal, but I also think that companies with poor 401k and healthcare benefits have no interest in improving them even if the business becomes wildly profitable because the kind of employees who know better are either older or not docile enough, i.e. they’re not going to drink the kool aid and work long hours and give up competitive compensation just because they’re “changing the world.”

The last thing a startup wants is a transactional employee who considers employment an exchange of cash for time. They want “believers.”
Do not doubt experts on this field. What he's saying is true.

> Biological systems are hard to understand and to modify, but maybe that's more due to redundancy that has evolved than to systems that are coupled like bad software systems.

No, it's not. It's all highly interconnected. There are no nice decoupled modules. If someone is showing you a module from biology which seems to have no interactions, he's leaving out information.

The only reason biological systems are not as fragile (although they also are. E.S. Collizi did some interesting research on why) as you think is precisely because they are so interconnected and redundant.

Furthermore, you seem to misunderstand why we don't see fragility. It's not because we get sick instead, but because nearly all of the nontrivial mutations are highly lethal, and the fetus dies in utero and you get a miscarriage. Most miscarriages happen so early the mother doesn't even notice.
Was he old? was it a heart attack? I mean, just a random death? I think this has to be highly unusual at a desk job.
> you have to understand first why ProtonMail choose Switzerland.

A quick look at their Wikipedia page tells me that it was created by people who worked at CERN, and that it is headquartered in Geneva.

So it's possible that the answer could simply be: Because that where the founders live (and it is also more advantageous that neighbouring France).
I agree that the actual list is not purely based on risk of serious injuries. It’s a list to cover the scope of OSHA issues which means it’s less arbitrary than you might think.

Anyway, it has some interesting info. “903 Latinx workers died on the job in 2017 representing a 15 percent increase since 2012, and 17 percent of all U.S. fatalities from workplace trauma.”
Since there are multiple complaints about the photos in this thread, I think I should point out that the photos appear to be a metaphor for the hiring process. All of those highly-diverse ice cream cones look dazzlingly yummy, but we can only pick one.

It's totally okay if you didn't get the metaphor... there's lot's of symbolism that goes over my head in lots of media, but I don't think it's fair to say the photos aren't relevant to the content.
Related: Greg Ward - Documenting history, or How to write great commit messages: say what, not why. https://www.youtube.com/watch?v=Jb6ij4eRu6c#t=378
Learning things is how you keep your brain sharp.
But what will I put on my Lucky Charms if we don't have milk?

Seriously, the worst thing for me about doing away with milk/cream/etc. would be having to get all new recipes. Especially for baking. Milk is in so very many recipes and you can't just switch it out for soy milk or almond milk.
Electric vehicles are our future, if we want to curb climate change.

Unions are against this because the skills required to work on these new vehicles requires a higher education, which many members don't possess, and will put them out of a job.

This is just another example of the unions holding back much needed progress all in the name of money. It's sad some people won't have a job with the transition to electric vehicles, but the same thing happened with the horse and buggy.

Maybe they should spend some of the union dues on education/training for their members, instead of striking.
I discern this situation is slightly different. Let's say an incident around ICE caused protests and riots. After the riots continue, a major Tencent executive speaks out that he supported the riots comparing the ICE detention centers to interminant camps. Immediately after this, Trump asks the Tencent CEO to fire this executive for his interview on Chinese TV or the US will pull all Tencent games. In this situation, I believe Americans would be angry at the government and politicians. Some would agree with Trump and some would disagree, but I believe most people in America would not advocate banning a product or company due to one of its executives saying something that did not align with a political view.
I do not believe that the five eyes have the ability to break modern encryption. But they probably have influence in Iceland in general. But I doubt they spoof the whole island. That would probably very noticeable.
It might be, but I can’t justify the price to myself at the moment.
Not true when the company that laid you off constantly posts job openings with your exact job description. You're forgetting about things like age discrimination, too. For example, I'm in my 50s and had a long history with my previous employer. Promotions, bonuses, etc. However, big companies in the US do layoffs to get rid of pension liabilities. I had no pension at this company, but because of my age I was tagged. Why? Age demographics...including those without pensions in the layoff rounds let the company show they were not violating the WARN Act and others (in the US) by singling out only pension holders.
Perhaps the title/premise might best be summarized as based on everything we know we can detect heart failure form monitoring one's body for one heartbeat.

Along with doing a lot of good and making a lot of early catches, I suspect that relying on AI to do medical analysis is going to bring into sharp relief just how much medical science DOESN'T know about the human body and its mysteries. I think we're a long, long way away from handling medical science over to AI and the real fun of AI-guided exploration is about to begin.