3 ms·
It can make sense, but serial job hoppers may also keep bouncing to the next thing before learning what the medium to longer term implications are of certain te
by wisemang 3y ago
It can make sense, but serial job hoppers may also keep bouncing to the next thing before learning what the medium to longer term implications are of certain technologies or design decisions. For example operational issues and maintenance.
I’ve seen teams get screwed over by someone parachuting in to deliver v1 with shiny new tech and getting a pat on the back ($$) for a job well done. Fast forward 6-12 months and you realize the new tech debt is as bad or worse as the old tech debt.
That said, stagnation and sticking with Blub can also bring its own set of issues.
- happymellon 3y agoCurrently dealing with this situation, shiny new architect declares Kafka as "the one true way" and forces all services to use it. Fast forward 12 months and we have a terrible, complex, non-scalable, system, which should have just been a really simple REST service but instead we just have another point of failure. Oh, and they quit so have no idea that their designs were trash.