In my opinion,expertness on these areas especially developing software doesn't depend upon a traditional degree like MBA.Check Google Play,Windows MarketPlace or iPhone app store,how many of them have done their MBA?
I am a student of CS doing Bachelors degree which will complete within 2 months,i already got an offer to join as project manager in a soft. company,so that clearly indicates they would not prefer my degree.Yes,it may prove a little bit useful for Business analysts or Unit Managers on their relevant field.But i oppose developing any kind of software doesn't depend on doing MBA or not.
I've often wondered sitting in presentations where some managers come up with some of the unintelligible gobbledegook the come out with. Do MBAs provide a secret dictionary of management speak, or how do they come up with the stuff?
The first thought I had was "it doesn't fit, it's like apples and oranges", but there is an underlying approach for people who may be better professionals in business administration than in software engineering. This has nothing to do with clever and poor brains. Each profession requires specific personality skills that have a serious impact on professionalism and success. Instead of analyzing this, I will give you a simple (and possibly silly) example.
If you believe that "converting a string to lower case is faster than upper case" is 100% accurate, then you may have a better career in business administration for a very simple reason: it’s not 100% accurate, it was just promoted by millions (blogs, forums, comments...) just like a commercial ad. "Word of mouth" in any form is not software engineering.
If you got my point then you may see the distinction between born-to-code professionals and IDE users. And if you do this, then you may find a lot of people with different roles in the industry that potentially may be better professionals in business administration, and quite often (sometimes hopefully) in another industry.
In a college there shouldn't be MBA's or bus schools that self-select for obedience to the corporate state which treats managers like royalty and engineers like foot-soldiers able to take credit for victories and blame the more accomplished people for defeats - particularly in large companies. It's a soft skill and that's what Dilbert is about. That's why the commodified education system wants idiot savants at best technocratic systems managers and blue collar researchists, illiterate, with selective consciousness and non-forward thinking values for profit. So I also resent the ad-hoc techno-hubris with this culture's ideas about progress and hyper-complexity dependent on oil and other contracting non-renewable resources.
A sociopath wants to control others. A lot of careerist a-holes sacrifice creativity and quality of ideas and skills which creates unproductive un-nurturing work environments. Ideas out of MBA schools about efficiency and neo-liberal global bottom lines with service based neo-colonial Indian IT cartels for example are not necessarily accounting for externalized costs due to politics, language barriers, and naturally a lack of work quality. An MBA yes man tends to be about typical short-term thinking for the managers benefit at the expense of quality which has evolved at this point into abusive path dependent hierarchies that have destroyed a livable future.
The best programmers are often cross-field people. I haven't experienced that in the MBA space though I know some are likely out there although likely lacking in depth of character. And try complaining to HR about a bad manager in a large company these days.
Every time they release a product they should be made to work with it in situ at a real user's desk for a week giving them the opportunity to learn why everybody hates their fancy UI and illogical menus!
If your intent is to move up the corporate hierarchy and manage a bunch of developers, PM's, SA's, or what have you, and have sufficient respect of the marketing managers, finance managers, senior managers, etc. to get heard, then by all means get your MBA ticket punched. If you want be a top notch developer, be the engineer and focus on your MS in Computer Science, or other technical field. You can't teach MBA's to code. Period. You can only give them enough knowledge to be a major pain in the behind. Coders should either aspire to be MBA's or top engineers. Very few can be both. I know, I've tried.
Well, I'm a "Dimplom Informatiker" (it's like master of computer science) with a emphasis to business. I think that understanding business processes is a very fundamental keypoint in architecture. In further education a made my TÜV certified project manager.
I think the knowledge of those tools is very important but everyone with a diplom or master degree should be able to work that out.
Well, to some extent. Everyone should at least finish high school...
After that a smart brain, a good attitude and a bit of experience will get you further than any diploma could.
Unfortunately people who are hiring don't see it that way...
So far I've seen the best educated people write the worst code. It's sad really...
I think having an MBA in information systems is a good idea for everyone dealing with software development. I have done MBA in information systems in 2011 and I am still coding(and other technical stuff).
IMO, having an MBA gives developers a different perspective, The perspective of looking at software as business solutions. Most developers tend to think about the code and application without having the holistic view of the business application or schedules, deadlines, estimates. Studying about why these other things matter gives an edge to the developers and they can actually start thinking themselves as internal entrepreneurs(with a code to sell internally) in the organization rather than mere developers.
Twenty years from now you will be more disappointed by the things that you didn't do than by the ones you did do. So throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore, Dream. Discover.
I'm currently working on an MBA and have spent many years in software engineering. My primary goal is to gain a business education and migrate from engineering into business leadership and management.
The MBA is useful for understanding business principles and also gives you a better awareness of "non techie" work in a larger ecosystem. It surprises me how many of my peers have no clue as to how their code works outside of their cubicle. Sad, but true. You can develop the best possible solution, but if you can't sell it, then it's game over.
For the general rank and file engineer writing code all day, it's probably not useful. However, for those in senior level positions, project managers and BA's it would be considerably more useful. At that level you need to deal with contracts, marketing, managing people across organizations, operations/supply chain, and other business issues.
This question assumes that an MBA is the best way to understand business. It might help developers communicate better with the pure business side folks who all went that path. However, in my perspective, this question is a bit off because it assumes a method for reaching a desirable goal. I'd ask:
Should developers understand the business of how their company succeeds/fails in their market?
Should developers understand the business of their company's customers?
In both cases, I think the answer is yes, but the second of these seems more directly relevant to our jobs, even as developers.
I suspect that in business school, they teach you that Product Managers define what developers will develop, Solution Architects define how it will be developed, and Developers code exactly what the PM and SA told them to. This is a nice theory, but for most of us it's a fallacy or some BS (Business School) fantasy. Developers almost always do both of these tasks all the time. How many times have you gotten arm-waiving requirements from a product manager and had to figure out what the customer actually needs? The PMs often even get the problem wrong, or come up with out-of-architecture demands that would ultimately be a disaster to implement. Solution Architects can provide some guidance about high level architecture, and may be great collaborators when it comes to how to develop a solution, but again, we'd grind to a halt if we waited on them for architectural guidance.
I think the truth is that if you're a developer, you're most likely to be playing all these roles all the time. It's one of the very coolest things about the job. Do you need to understand your customers' business to do it well? Yes. But will you learn that better by going to business school, or by talking with your customers? The answer seems pretty self-evident to me.