There are a few reasons:

The first would be that business disciplines (particularly entrepreneurship, finance, and business analysis) interest me greatly.

Second, I've been lucky enough to have a great mentor in my youth who's an entrepreneur. He influenced me greatly and piqued my interest in entrepreneurship and finance.

Three, I figured going into a business degree would be good for building my soft-skills.

Between these factors, it just felt natural to into a business program.

Although I think a computer science degree would've been incredibly valuable, I do take pride in self-learning development.

I think being a self-taught developer is a powerful demonstration of my intrinsic motivation towards continuous, life-long learning.

And at the end of the day, I believe that all technical professionals have to be "self taught" to some degree--
Web technologies grow and mutate so quickly that it seems the learning never stops in this profession.

So I can confidently say I'm happy with being a business school grad trying to be a Dev; and having a sharp business acumen and strong customer focus will make me a very well-rounded tech professional in the end.

After working in a variety of different roles and companies in the technology industry, I've noticed a universal truth in this business: knowledge of code is powerful.

I know that the hours I've spent debugging code, and racking my brain setting up my project environment, will pay off in any role I undertake in the IT field. In a nutshell, this development experience would add a ton of value to what I offer as a tech professional.

My biggest professional/life value is lifetime learning. I feel most accomplished when I'm improving in something, or learning something new.

This translates well to the field of technology, where the learning never ceases. Learning to develop applications is a natural result of my pursuit of learning and improving as a professional.

Another of those values is that I take a lot of pride in my work. When I'm responsible for a piece of work, I'm often not satisfied unless it's completed to a standard of quality at which I can be proud of my work.

Even though this has made me slower to finish tickets in my as an Application Support professional, I think a dedication to quality results in robust and readable code.

Over the years, I've developed a deep knowledge of how I work best, when my best thinking occurs, and what type of work environment I’m most happy + productive in.

I've found that my best work comes out of long, concentrated work sessions where I can thrash away at a problem/project for hours. Once I hit my stride and enter a flow state, my motivation is highest and my mind is sharpest.

This work style has served me very well while learning to program. It undoubtedly can be mentally strenuous to be staring at a text editor for hours on end. However, once I hit my stride, I can't stop. I'll often end up hacking away at features all night.