[namaria]

Oh most definitely. Maybe my sarcasm was a bit too subtle.

I definitely think that teams should think about what to log. Otherwise go with a live image kind of system like Smalltalk of LISP. The whole event sourcing paradigm and trying to just log everything and look at it later strike me as a poor reconstruction of that concept.

There is a tragic aspect to the "Worse is Better" essay that I see play out everywhere: there is a way to do something correctly but just throwing something together wins the race to market. Winner takes all and we're stuck with ossified bad decisions from the past. The idea that we can fix it later is just a lie. You can't do the foundation later, you'll be stuck with a structurally unsound edifice and forever holding it together under a completely unnecessary cognitive load.

[whstl]

Oh I got the sarcasm, I was just agreeing.

And I also agree about worse is better. To me the most tragic part is that "worse" has become almost as costly as doing "The Right Thing", mostly due to the extreme flexibility and rush to the market from vendors and libraries. Our foundations weren't as sketchy when the concept was invented.

[namaria]

It has definitely gotten much worse. The only thing keeping me sane is hacking solo projects in languages with great tooling. I don't think I can even stomach interviews anymore, let alone the whole application process farce.

[whstl]

I remember doing an interview with systems design using microservices and mentioning at the end "Well I guess that's it but if this was my personal project I would just have a single server and no native cloud bs".

The guy basically answered "Oh, same. I just ask for people to do microservices because that's how the CTO wants".