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.
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.