A collection of technical things every software developer should know (2017)
1–10 of 47 posts
Re: A collection of technical things every software developer should know (2017)
#2Can 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.
Re: A collection of technical things every software developer should know (2017)
#3Very 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.
Re: A collection of technical things every software developer should know (2017)
#4Can 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.
Of all the things I’ve seen with emoji at the beginning or end of sentences, none of them are training readers for children and most of them are material by and for adults.
Re: A collection of technical things every software developer should know (2017)
#5Can 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.
Of all the things I’ve seen with emoji at the beginning or end of sentences, none of them are training readers for children and most of them are material by and for adults.
A lot of early-reading children's books embed pictures in the sentences. It helps kids learn the meaning of words or something.
Re: A collection of technical things every software developer should know (2017)
#6Can 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 second this. I feel very strongly that we have to do our best to make technical things more accessible to more people, but this trend of adding emojis to these readmes is just infantilizing. A lot of the content is interesting enough on its own, no need to candy-coat it.
Re: A collection of technical things every software developer should know (2017)
#7Can 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.
Probably not. I think it's the beginning of a major language evolution.
Re: A collection of technical things every software developer should know (2017)
#8I'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?
Re: A collection of technical things every software developer should know (2017)
#9If 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".
Re: A collection of technical things every software developer should know (2017)
#10Also 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...