HNHacker News
TopNewBestAskShowJobs

confusedgeek

11 karma · joined July 30, 2015

submissionscomments
confusedgeek··on Career options out of programming?
To your first point (management) - could you tell me more about how or point me to people who've made the transition themselves?

To your second point (research lab)- I began my career in research and have worked at two world-class industry labs, including Microsoft Research. You are right that these jobs are less about code - explains why I did well. :) After five or ten years at those firms, you'd be surprised at how many people in those places are truly satisfied with their jobs.

At my last job, an industry research lab that I quit to do product development with my current valley company, I couldn't meet a single soul in a building of a 1000 who seemed happy and excited enough to jump in the morning and get to work. Microsoft Research was a different story - but every happy, thriving individual I met there was in love with their field. I was similar for a couple of years, but couldn't sustain that. Wanting to be part of the corporate rat race as someone else pointed out, may have been a factor.

confusedgeek··on Career options out of programming?
Thanks, your analysis is spot-on. I'll work on the 'to do' items you suggested, particularly the last one.
confusedgeek··on Career options out of programming?
That's correct. I am in the US but not from the US. Like I mentioned in my response to karmajunkie's comment, that does make career changes slightly tricky for me.
confusedgeek··on Career options out of programming?
Thanks 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.
confusedgeek··on Career options out of programming?
"It sounds like you're unwilling to ride through the phase of uneasiness, of I-don't-know-how-to-do-anything-with-this-stupid-new-tool, of feeling dumb and clumsy, for long enough to become proficient. Look, I don't like having to do that, either." Many thanks for this - this is a great analysis, followed by just the reminder I needed. With this in mind, I will force myself to learn a couple of new things. I guess if I do that often enough, I'll have enough data-points to prove to myself that something that was once unknown and made me feel dumb can become a power tool.
confusedgeek··on Career options out of programming?
To add to that, reading new code is unnatural too. So far in my career, I've only built new things, and refined them based on my colleagues' input. But unlike my colleagues, who can dive into a piece of software and augment/change it adhering to the style of it, I am usually lost with any code that I didn't write.
confusedgeek··on Career options out of programming?
Thats a good question - I can't really articulate it well, but here's an attempt. (a) Design / Scaling: I guess I like solving small coding problems that translate math or logic into code. It is building software at a non-trivial scale that bothers me - anything that I've designed that was over 2000 lines was fugly code, and I can find numerous design flaws with the code I write and all the alternatives to it. At the end of my work assignments I am often dejected thinking - "I can't ever design something non-trivial cleanly." (b) Not being as good with new frameworks/tools: I am a loyal C/vim/shell person, no IDEs. I am very efficient at my shell+Vim development environment (which was shoved into me in school when I didn't have a choice), but I shy away from trying anything new because it feels unnatural or scary.
confusedgeek··on Career options out of programming?
I had a McKinsey offer - rejected it to take up my first job which was in technical research in California. Most consultants spend time building powerpoint - some of them are exceptional and eventually do well - like the ones who are now top-notch biz-dev folks at valley tech companies. But thats a small fraction.