3 ms·
> Learned as junior: New tech solves old problems. > Understood as senior: New tech creates new problems. This is one all the people who push "new and shiny"
by JustSomeNobody 7y ago
> Learned as junior: New tech solves old problems.
> Understood as senior: New tech creates new problems.
This is one all the people who push "new and shiny" need to learn.
- giancarlostoro 7y agoI mean, yes and no, sometimes an old systems so bad it really needed to be killed off and replaced. Or would you rather everyone stick to coding in VB6? I rather we all use C# instead of VB6 ;) I'm not implying we only ever use C#, I know there's other languages, just illustrating a shift in the MS windows development ecosystem that was for the better.
- JustSomeNobody 7y ago> I mean, yes and no, sometimes an old systems so bad it really needed to be killed off and replaced. I don't believe this is the spirit in which this was meant. If the old system is out of date and there are buggy libraries that aren't being maintained, that is a WHOLE different issue.
- kerng 7y agoVB 6 is probably not a good example. Even nowadays many languages don't have features that VB6 offered incl. WYSIWYG. Debugging capabilities of modern languages/environments are still often not even close to what VB6 offered 20+ years ago. C# certainly is outstanding but I think Microsoft made a gigantic mistake by killing VB6 the way they did. Microsoft's prevented a large amount of people to write applications, since a new ecosystem like C# or VB.net was significantly more difficult to learn and understand. In retrospect Python or Node probably took VB6's place, so Microsoft just lost out on a huge market there. Bad management decision.