I think people with better "real world" knowledge (and that's not necessarily actual work experience, there are plenty of degrees around nowadays that don't take a classical CS approach), can potentially be better at higher level design and requirements gathering / analysis.
These people (and naturally these are broad generalisations) tend to deal with real world problems rather than complex, but still lower level algorithms. They've been asked to do things like "build a system that keeps track of our company's inventory" (and all the many considerations this involes) rather than "optimise algorithm x".
So I think their skillset is much more than source control and testing (which I'd put in the 'overlap' category - I don't think either CS or Real World people will get far without those). Obviously, it depends on what kinds of systems you're building, and what work environment you're in as to which is the most useful.
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||