|
The reason I’m considering it is because I’m trying to envision myself in 10-20 years and thinking who I would be happy to be. Right now, I don’t believe what would make me happy is to be a principal/staff engineer somewhere necessarily. Don’t get me wrong, I love programming, but I see it as me getting paid to solve problems, and not getting paid to write good code, and I think there are other ways to solve those problems. For example, I think the biggest problems in my organization are managerial and organizational rather than technical, and I feel like the type of training that would come with an MBA can help one solve those issues, including communication, planning, product validation, people management, etc. That said, my entire reporting chain up to and including the CEO doesn’t have an MBA, so it’s not like it’s a prerequisite. The other path I’m considering is an MS in CS/SE because while I’ve been an engineer for a few years, my undergrad is in Mathematics, and I’m worried it’ll be a limiter later on to not have a CS degree, but also only a BS. |
I was a decent enough software engineer and while I love to build things, I felt there was more.
Almost all company problems tend to be managerial and organisational rather than technical, which is a fascinating discussion in my MBA classes. You will definitely get the space and time to think about these things and your theories on how to solve them.
However, I will say that to solve those problems, you have everything you need today. Your knowledge, wisdom and experience can help guide you but fundamentally, these problems touch the aspect of humans behaviour. A great book is “How to win friends and influence people” - I’m recommending it not to influence anyone but it’s a good eye opener to human behaviour. The MBA will help with theories but it’s not fact of course.
I’ve also thought about an MS in CS for fears of being limited in the future as well but will respond back when I have more time. Or if you’d like we can have a chat over Skype or email.