3 ms·
I once wondered this after working on a not-too-interesting contract position for 18 months. It seemed like my abilities had atrophied. On top of that, I then t
by karmakaze 7y ago
I once wondered this after working on a not-too-interesting contract position for 18 months. It seemed like my abilities had atrophied. On top of that, I then took another year off from work. At that point I thought for sure I was past my prime.
When I finally did go back to work, it was easy to get into the hardest change was unlearning previous source control systems and getting my head around Git. [It would've been so much easier if I just read about its internal structures than articles.]
I still expected to peak or plateau but that hasn't happened. There are certainly things that I don't do as much or well--like consuming vast amounts of information rapidly--but I more than make up for it by carefully choosing a path that usually pays off in a couple iterations. Still love to learn new ways of doing things and slowly expanding into less technical areas like matching problem understanding to a tech solution. I've never been impressed with architecture which is often poorly executed as to be in-the-way as much as it helps. Can't say I've worked on projects so large that it's been critical.
Microservices is hard and gets a bad rap but when done right can be an awesome experience. I've recently started making full-stack monorepo microservices apps and couldn't be happier.
I figure at some point I should start down the less technical people management track but there's no need for it to happen any time soon, I can keep up with the youngin's just fine. I've been developing software for over 40 years.