Yes, there&#x27;s a point where it gets very difficult to get a new job without retraining yourself.  When I started programming professionally in 2000, the hot frameworks were Java Swing 1.3 and MFC 6.0.  I could probably get a job in these, but there&#x27;s about zero chance it would be doing cutting-edge stuff, or even anything other than maintenance programming.  C++ &amp; QT is probably in this category already.<p>If you have an adequate cash cushion and accept the need for it, though, re-training is not that scary.  Six months and you can come up to speed with whatever the latest hotness is, and then you&#x27;ll have a leg up on new grads (because you&#x27;ve seen all the ways software projects can fail) <i>and</i> on grizzled hires who don&#x27;t have experience with the latest tech.<p>The tech industry moves fast enough that it&#x27;s not always worth staying at the bleeding edge.  Jump to the bleeding edge when you retrain, and use the time in the middle to work on soft skills and things that don&#x27;t change as rapidly, like back-end development, domain knowledge, and fundamental CS.  You can save a lot of time by skipping technology generations entirely.