4 ms·
I got my masters, then pursued a PhD for 6 months after which an opening in computer graphics came up in the industry. I abandoned my PHd and started a career a
by fsloth 8y ago
I got my masters, then pursued a PhD for 6 months after which an opening in computer graphics came up in the industry. I abandoned my PHd and started a career as software engineer.
The reason was I sucked in physics, did not find my PhD position motivating and loved computer graphics.
13 years later I'm a valued technical contributor in a team in an ISV creating a valuable global software packages in the CAD field.
Middle class income, could probably make lot more in US with my skillset but family situation really is not awesome for expatriation.
I'm doing OK.
With physics skillset you can pretty much make your career what you want it to be. You just need a proactive attitude to read on other fields. You need to understand the other guys mindset so you understand the overall game going on. It's usually not nefarious (although it can be), but most of the time the rules that are used are not the vocalized ones. In this empirical physics is a wonderfull philosophical background. Organizations have certain dynamic rules which half of the people are not aware of. You don't need to "play the game", but you need to understand the rules so that when the wind blows into the direction you want to go into you can grab the opportunity.
I had a pretty good idea where I wanted to be 13 years ago (R&D in a position that values quality over quantity and speed with a great team) and that's pretty much where I am now.
You need to know where you want to go, and go there. No one will guide your path. Physicists are an outlier but that math and mindset is really an asset. Just don't get stuck in fixing bugs in some legacy monstrosity, that is absolutely soul crushing. But such a position can function as a stepping stone if you are operating in the industry you want to work in.
- tobmlt 8y agoFixing bugs in a legacy monstrosity checking in! Updating my resume this week. What's an ISV?
- fsloth 8y agoThat's what I was saying - you need to understand the game. Part of this is knowing the core business terminology in you field :) ISV - independent software vendor. An entity having an ownership of a software product, usually developing the software as well. The other entity this is often compared against is the ESP - external service provider. I.e. consultants. I spent years with legacy monstrosity and it does develop important skills. If the organization is otherwise ok it might not be that bad - but generally production software is absolutely horrible. The thing is legacy maintenance is important, and there's quite nothing like it that will teach you about the lifecycle requirements of software development. But I find it much more fullfilling to maintain and develop software that is alive and well and actively kept out of the 'legacy' label. Not all old software is 'legacy'. One definition is that does it have tests. I've found an equally good definition of 'you are not afraid to modify it' and 'you can understand what changes in one place do elsewhere'. So to be clear, I was not saying "anyhing but greenfield development sucks".