Can we pleeeeeeease stop putting emoji in the middle or end of sentences like this was a 6-year-old's training reader?

Any time I see a sentence end in that strong-arm emoji my douchebag-o-meter goes way way up.

Very nice list... I do wonder how much money the author/contributors make by having Tuple's ad at the top of this popular readme file.

I'm a little surprised by the answers in "Cryptographic Right Answers". Both libsodium and Chacha20-Poly1305 are not FIPS-compliant. "AES-GCM" is but it has important gotchas in regards to the IV and per key data volume. "AES-GCM-SIV" is more resilient but "AES-GCM-SIV" isn't FIPS compliant either but there is a proposal underway to certify it. So the cryptographic right answer is "it depends". FIPS compliance may not matter to some people but it does a lot to others depending on the context.

I think the safe answer is AES-GCM using envelope encryption?

If you are starting your career and panic reading such list, that would take years to learn, if even. Don't worry.

Most of these items are more like nice to know than should know.

Yeah it would be great if every software developer knew everything. But I doubt even the repository owner know all that is listed.

My best advice to newcomers is get your hands dirty and stay away from endless hours of courses, YouTube videos and "awesome lists".

Also remember: Even though many of these articles/books/papers/etc. are good, even great, some of them are starting to get a bit old. When reading them, check what modern commentators are saying about them.

E.g.: What every programmer should know about memory (18 years old) [1]

How much of ‘What Every Programmer Should Know About Memory’ is still valid? (13 years old) [2]

[1]: https://lwn.net/Articles/250967/

[2]: https://stackoverflow.com/questions/8126311/how-much-of-what...

I laughed at timezones

Clever ad.

You should know only what you need to know to solve a problem.

You will eventually encounter each and every item on that list, and some. Software engineering is a learning grind till the end. The projects will dictate the skills needed for it to be successful. The difficulty is that you won't be given time to learn any knowledge gaps.

A better title would have been "junior dev compiles collection of his favorite links".

:) Soon to be renamed to "a historical collection of things every software developer had to know about."

Will start with "software used to be..."

Not every developer needs to know about all of these things. I'd take this more as a "list of interesting details related to common things you might depend on", it's akin to suggesting that doctors of specific specialties (dermatologist) should know about random things that are part of other specialties (proctologist).

[flagged]

The random use of emojis tells me this was written by an LLM. If it's not worth your time to write a list it's probably not worth my time to read

> How to Win Friends and Influence People

really? in 2025?