No one criticizes the manifesto itself I believe. But there's a huge difference between the abstract idea and principles of the manifesto, and an actual implementation that usually differs from company to company. So, yeah, the idea of babies is nice and all (everyone loves the manifesto), but you need to change diapers and that gets dirty. No one likes to changes diapers (no one likes Agile).
This should be emailed to dang. hn@ycombinator.com The most anyone here could do with it is add the users to uBlock but that would hopefully be a waste of time if they are disabled by dang. Most appear to have negative karma already.
He. I've been running always everything one or two versions behind latest (for my personal laptop, not servers). That means mainly OS (e.g., macOS), but as long as I can avoid automatic updates, I do so.
I believe the chances of having a bricked laptop because of a bad update are higher than the chances of getting malware because running one or two versions behind the latest one.
> It’s both. If you’re an engineer and you push out shitty code that takes down 911 systems and ambulances, you f’ed up.
This is wrong. If a company is developing that kind of software is the responsibility of the company to provide a certain level of QA before they release software. And no, it's not that "engineers are pushing out shitty code", but that the shitty company allows shitty code to be deployed in customers' machines.
I think it gets harder to remember exact syntax details the more experience you have and the more you have worked with different (but very similar) programming languages. I get what OP means: if you have worked with Ruby, JS, Python, Go, PHP, Kotlin, etc., you can easily misremember things like the order of parameters for a given function, whether if conditions require parenthesis, to use {} or [] for maps, etc.
If you have just started your career and are full invested in 1 or 2 programming languages, sure this may sound alien to you.
I get it. I've done a ton of languages too. But, like, that's so ridiculously easy to handle in an interview, right? "I think it's like this [show example], but maybe the hash rocket style is Ruby and it's actually colons. Either way, you get the idea."
If your interviewer finds that problematic, well, that's on them.
