With the caveat that I'm not a CS graduate...
I'd put 'problem definition skills' as one of the most important portions of your overlap category. It takes real-world experience to see the relevant issues to be solved -- especially business-related 'relevant' -- but mapping those issues into an elegant computer-friendly solution takes a knowledge of what's available. For a light but pointed exposé of the dangers of limited real-world experience, see The 'f' in framework
. The writer's most important point is that customers care only about solutions that solve their problems
, not about elegance in programming and programmability. This is truly where the rubber (CS knowledge) must
meet the road (the real world).
I've worked in many environments, including both those where I was peon and those where I was godlike, and my most important learning experiences were those in which my position was transformed by my own efforts into the opposite of those just mentioned. Having gone both ways, I'll have to leave you with my most important real-world
"There's more than one level to any answer."
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||