Exactly. Software that changes as frequently as something like a Twitter (or anything of that ilk) never has the chance to reach that kind of stability. Your thirty-year system wouldn’t have the track record it does under the same set of conditions.
> In other words, "grow as an engineer" means "parroting the lies that keep you employed"?
I’m not sure what kind of leap you’re making, but it seems breathtaking.
In any case, you’ve clearly had the privilege of working on software under vastly different constraints and timeframes. That sounds fun, and interesting, but it’s comparing apples to oranges.
Exactly. Software that changes as frequently as something like a Twitter (or anything of that ilk) never has the chance to reach that kind of stability. Your thirty-year system wouldn’t have the track record it does under the same set of conditions.
> In other words, "grow as an engineer" means "parroting the lies that keep you employed"?
I’m not sure what kind of leap you’re making, but it seems breathtaking.
In any case, you’ve clearly had the privilege of working on software under vastly different constraints and timeframes. That sounds fun, and interesting, but it’s comparing apples to oranges.