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
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.