I think it is normal for your job to require a lot of business-specific knowledge. This is what I think of as "understanding the problem" or "modeling." Other people think of this as "going to meetings" or "talking to people" or "design".

The nice thing about software as a hobby is that you get to choose how much of this type of overhead you want to do. At work, I'm expected to show up at meetings.

My SWAG at a breakdown:

Understanding the problem	50%
Coding	20%
Testing	10%
Maintainance	10%
Documentation	5%
Tools	5%

Of course, sometimes you batten the hatches and code like hell for a ten hours a day and design for six hours a night.

Often you can dramatically change your ratios by working more hours.

It should work perfectly the first time! - toma