3 ms·
Thank you for the response. I skimmed through the CBT definition and it seems to fit my case up to some point. Will check it more in detail. As for the 'clock
by __exit__ 8y ago
Thank you for the response. I skimmed through the CBT definition and it seems to fit my case up to some point. Will check it more in detail.
As for the 'clock is ticking' part, what I had in mind was that somehow I need to learn as much as possible now so that my future-self is better professionally. This arises from the 'fear' that I will not be a valid professional by (say) my 40s-50s, as from what I understand, software engineers by that age are a smaller population compared to the younger one, and in addition, younger engineers are preferred over older ones. Of course, I am probably mistaken, but it's the general feeling I got by reading posts over the Internet. This, again, has to do with the feeling of 'rejection'.
I'll try to reconsider my situation by taking a break. Also, will improve my learning methods from your advice.
- matt_s 8y agoI think you may be mistaken on the 40's to 50's part. What you don't see from experienced, well aged professional software engineers is they probably don't want to work in SV or at startups because they may see it as silliness (take home pay beating out lottery ticket options). They don't care much about new & shiny frameworks, etc. unless it helps solving a problem in a better way. They probably have seen new tools/frameworks come and go a few times. Maybe look for opportunities to work on tougher problems to solve. Maybe explore other options like project management or people management? Don't be fooled into thinking those are the only path to more salary though. It's also common to forget things with how many libraries and apis we have to use. A common concept in a lot of these is pushing complexity down the stack so you don't have to have it in mind when doing things. Least used things get forgotten.