3 ms·
Thanks for your long answer! I agree that Wall St. is not an option. I wouldn't want to develop risk analyses or the next ultra fast trading bot anyway. Not tha
by davrosthedalek 14y ago
Thanks for your long answer!
I agree that Wall St. is not an option. I wouldn't want to develop risk analyses or the next ultra fast trading bot anyway. Not that I don't like thinking about finance, but not all day :)
I don't want to make this a "please hire me" post. But since you mentioned specific skills: I would say that I have a higher affinity to software development than most of my colleagues. For example, I am currently the "offline analysis coordinator", and it that role I wrote pretty much the entire analysis framework. I also dabbled into web applications: Our slow control, i.e. the experimental control software, is a web application with postgresql backend written in Python (Flask). I kind of liked that, and I think I will wrap this up and put it on github.
But I digress.
You made an interesting comment about relationships, and you are certainly right there. On the other hand, academia doesn't make it easy there too. You are guaranteed to move a lot, and especially in experimental nuclear science, a lot of the places are in less than stellar areas.
What made you come back to make your PhD?
- CyberFonic 14y agoThanks for asking: I started my career as a "real" engineer - safety boots, hard hat, big SUV, million dollar a day decisions. I morphed into financial engineering guy (with engineering skills you can model and understand any complex system) and I've always been involved with ICT - SCADA & telemetry along with concrete footings and steelworks. Over the years I became very frustrated about the lack of real engineering in what passes for software engineering - obviously by this time my exposure was to fund managers, insurance companies, merchant bankers and the software based systems there. So I decided to make a mark in that corner of the universe. I'm still working on my PhD, but also do consulting, involved in a startup and teaching SE courses at postgrad level. I guess my point is that I really wanted to do something about a problem that wasn't being well addressed. Typical engineer personality - see problem - go about fixing it. Try to not make it worse!