| > I do see a lot more intellectual rigor in the older techies than in the ones from my generation. My experience has been the opposite - though as this is based on observation it's obviously subjective - and opportunities for selection-bias are also present (i.e. how many of the last-generation that didn't get promoted-out of being a technical contributor was because they were more valuable to the company that way?) Your remark about automated tooling is interesting - because I feel that modern tooling (TLA+, Z3, constraint-provers, and cutting-edge languages like Haskell, Idris, and so on) really do require almost a postgraduate-level of understanding of the CS theory involved - whereas if you look at _the SE scene_ in the 1970s and 1980s - or even the mid-1990s, the tooling certainly did require you to do more planning and reasoning ahead of time (VB6, lol) but I can't see the entire industry of the time doing their modelling and verification entirely by themselves: on the contrary (and based on the horror-inducing programming code I've seen) a lot of it was ad-hoc and trial-and-error - Visual Studio didn't get built-in support for unit-tests until 2008 (or 2005 if you had the expensive edition). Also consider that the old SE processes used back then (Waterfall, boxed software, slow-moving-and-big release cycles, etc) meant there was more room for less-rigorous folks in large software dev teams. > and your calculator won't save you from a logical listake. For that, you need a spell-checker! UPDATE: Ah, you edited your post, which ruins the joke :/ |