Not sure I follow the DOS/Windows analogy. Unless you spent all your time designing GUIs, a lot of those skills carried over. Especially with the advent of VisualStudio (also developed to replace engineers), you could drag and drop a window layout, double-click an button and continue coding as before. There was a small mental leap necessary to write event-driven code (instead of using a superloop), but that’s an afternoon-long “a ha” epiphany, not going back to school for a new degree. Ditto for MVC-like layering.
And the DOS/Windows analogy is further baffling since Windows-native coding has mostly come and gone. Even “native” Windows apps are typically Electron — web pages captured in a window
Unless the author is saying we must always run to stand still, which they seem to reject early on.
This is a really good read, not sure why its not being appreciated more
Well thought out and well done, thanks for sharing
Guess it just kinda pisses everyone off by not “taking a side” on this set of issues but its a rock solid blogpost for anyone IMO
Yeah I thought so too! I am not sure why it’s not appreciated more either, it was a great read!
UNIX schedulers became better and better, and eventually nobody needed to set process priorities and nice levels anymore.
I use nice levels.
Because you want to, or because you need to?
Some people are just nice by nature.
