but you should not consider faulty business logic as an optional fix

The same goes for unreadable/unmaintainable code (though that’s a bit harder).

What about dystopian surveillance tech?

The “jeans and (white) shirt” tier seems to be missing.

Shouldn’t it be “Hello world.”?

https://en.wikipedia.org/wiki/Loss_(Ctrl%2BAlt%2BDel)

Even if the code is flawless now, all it takes is a single flawed line of new code. This is of course true for all languages, but type safety helps a lot as some types of flaws would not compile.

I once had a hammer head get loose and fly off the handle.

Tech: https://strudel.cc/

• Talk to your colleagues: clarify requirements, question assumptions, get feedback, talk about best practices and why you do stuff the way you do it
• Single responsibility principle

Write your code as if the next person that works with it is a violent psychopath who knows where you live.

By teaching history, including how capitalism killed millions of people, whole ecosystems and uncountable species.