fantastic. I've heard of bits and pieces of this but this is the first article I've read which lays out the entire timeline with all the firsthand sources you could want. thanks for the effort!
You think this was written by AI? I'm curious, why? Anytime I'm about to read a long post I generally paste it into a few detectors for sanity, but none of them flagged anything for this one. I read the entirety and…
https://damrnelson.github.io/github-historical-uptime/
One check of their LinkedIn.
Completely fair - but at least my PoV comes from having actually worked as a SWE, you know? I feel like the best understanding this fellow can have is purely secondhand from watching the success / failures of his…
There's something so off-putting about academics giving industry advice when they haven't spent a day working as an engineer at a company. > Care deeply about your craft. Refactor code until it is clear and elegant.…
fantastic. I've heard of bits and pieces of this but this is the first article I've read which lays out the entire timeline with all the firsthand sources you could want. thanks for the effort!
You think this was written by AI? I'm curious, why? Anytime I'm about to read a long post I generally paste it into a few detectors for sanity, but none of them flagged anything for this one. I read the entirety and…
https://damrnelson.github.io/github-historical-uptime/
One check of their LinkedIn.
Completely fair - but at least my PoV comes from having actually worked as a SWE, you know? I feel like the best understanding this fellow can have is purely secondhand from watching the success / failures of his…
There's something so off-putting about academics giving industry advice when they haven't spent a day working as an engineer at a company. > Care deeply about your craft. Refactor code until it is clear and elegant.…