Live data from Hacker News

A collection of technical things every software developer should know (2017)

github.com

31–40 of 47 posts

Re: A collection of technical things every software developer should know (2017)

#31
Tangentially, am I the only one left on the planet who abhors watching videos in order to consume information?

It has been a nightmare watching the world’s information migrate over to YouTube when it used to be quickly digestible text formats.

Re: A collection of technical things every software developer should know (2017)

#32
post #8

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 no…

If you use libsodium, its very hard to screw up your encryption. If you use AES-GCM, it sounds at least like you can screw it up. Surely you'd want to use the first one?

Totally agree with you on this but I think in some settings FIPS-compliance is a requirement -- especially anything to do with the Federal government. The obvious fix is for FIPS to catch up but until then the three choices the document listed aren't great. The first two don't meet the requirements and the last choice, as you've pointed out, can be a bit of a foot gun. I wonder if AES-CBC-HMAC (i.e. Fernet) should be listed as a choice for FIPS? Like keep the original 3 and then have a sub-heading: FIPS-compliant: AES-CBC-HMAC or AES-CTR-HMAC like it did originally.

Re: A collection of technical things every software developer should know (2017)

#33

Earlier quoted context omitted.

If you use libsodium, its very hard to screw up your encryption. If you use AES-GCM, it sounds at least like you can screw it up. Surely you'd want to use the first one?

Totally agree with you on this but I think in some settings FIPS-compliance is a requirement -- especially anything to do with the Federal government. The obvious fix is for FIPS to catch up but until then the three choices the document listed aren't great. The first two don't meet the requirements and the last choice, as you've pointed out, can be a bit of a foot gun. I wonder if AES-CBC-HMAC (i.e. Fernet) should be…

That list is geared towards developers who don't have a strong background in cryptography and helping them choose a secure algorithm that is easy to implement. Because if you get it wrong, more vulnerabilities will be introduced.

Working around janky compliance standards is a whole separate topic.

Re: A collection of technical things every software developer should know (2017)

#35
post #9

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 vide…

The repository owner does not know everything, and has already forgotten many things he used to know from the list

But it’s a distilled and curated list of the resources I’ve found important to have at hand and revisit periodically

Re: A collection of technical things every software developer should know (2017)

#36

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.

It’s a time-bounded experiment with sponsorship (3 months) and it earned me roughly a 1 month rent (before tax)

Re: A collection of technical things every software developer should know (2017)

#37

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

It was written in 2017. If it was written by an LLM in 2017, I would be already quite rich

Re: A collection of technical things every software developer should know (2017)

#38
post #2

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.

I dont mind them when they are not cringy. Arm flex is cringy.

I will replace it with almost anything you want. Pick your option

Re: A collection of technical things every software developer should know (2017)

#39

Tangentially, am I the only one left on the planet who abhors watching videos in order to consume information? It has been a nightmare watching the world’s information migrate over to YouTube when it used to be quickly digestible text formats.

You are not the only one. I have a lot of people around me whom I coach who prefers info to be in a text form

Would you prefer to have transcripts for those videos in the repo?

Post reply on HN