3 ms·
I tried to change careers once, going back to school to go into medicine. Took a semester off to help a buddy with a software development project and make some
by karmajunkie 11y ago
I tried to change careers once, going back to school to go into medicine. Took a semester off to help a buddy with a software development project and make some cash, and never went back. While that says more about me in general than what you're talking about, for me it was a matter of finding problems I cared more about (in my case I was writing public health software) and teams I enjoyed working with. I'm certainly in no position to judge your skillset, but say above that you feel comprable to a senior Google engineer (the relative merit of that being a whole 'nother topic!) yet you mention in another thread you have a sense of trepidation about reading code, working on only new projects, and you rarely feel satisfied with your non-trivial code. To me this suggests perhaps some room for growth as well. I had a great deal of the same feelings about my own code (even to this day on occasion) but i've developed much better elegance to my code as well as an ability to shrug the lack of elegance off as a necessary evil sometimes.
I gave up on the medicine thing because as much as I love the field of biology and human health, the lab experience wasn't so much better than coding that it would have changed my life, nor the practice of medicine so financially rewarding it would have compensated for opportunity cost as a reasonably well-paid developer. I've found that my career's had up and down cycles but overall I'm very fortunate to be in this line of work. You might as well, but I don't think you're crazy to want to leave the field either.
Whatever you end up doing, best of luck to you in the endeavor!
- confusedgeek 11y agoThanks for your detailed response. 1. I don’t ‘feel comparable to a Google senior (L4/Level4, to use Google terminoloy) engineer’ - it is a fact that my role at my company is equivalent to that. If anything, I feel an imposter, having made it to my job with all the shortcomings discussed (Google L4 engineers can typically build software at scale easily, and definitely aren’t as uncomfortable reading code as I am). It helps that I am in extremely niche field, so cannot be directly compared with other canonical L4 types. 2. Your story of the shift from medicine to software and the thought-process is useful. Not entirely easy for me to follow given my immigrant status. Any minor job title/company changes trigger a new H1/greencard, somewhat jeopardizing my chances of staying here longer term. I am not whining - just making a note here, in case someone reading this has dealt with or seen similar situations being handled before.