Earlier quoted context omitted.
> I’ve stagnated sharply skills wise I'm sorry, but what does this even mean? Nothing has changed in a significant way since 1996, other than ops per second and memory bandwidth. If you're an old school C programmer who knows how pointer arithmetic and memory allocation works, you're better than 99% of the total trash new-school Node.js/Django/Rails/React developers who think JSX is some sort of "innovation". Having…
Hey, by stagnating I mean I’ve barely written code in over a year, and haven’t done any significant greenfield work my whole career. The work I have done has been mostly in legacy or obsolete technologies, and by that I mean mostly old version of stuff that’s still out there. So by stagnating I don’t only mean not up on all the new hype tech, but also the caricature of a “code monkey”. Certainly on paper at least. >…
Green field code is easy-mode, not hard mode. Nothing is in your way, nobody expects anything from you (yet) because they have no basis of comparison. The real reason people want to do rewrites is that they want that greenfield experience without having to quit. It almost never works.