Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Whammo (2555)

Whammo
  (email not shown publicly)
http://www.coept.us/

BCWarnock

Journal of Whammo (2555)

Thursday February 27, 2003
10:29 PM

Dichroic

[ #10831 ]

"In a white room
With black curtains
Near the station"
-- Cream

Opinion collection: where is an appropriate balance point between programming knowledge and domain knowledge?

Or to put it another way, what's the minimum amount of domain knowledge a programmer should have - or vice versa - to (generally) be successful?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I depends on the domain, it depends on what you're doing. If you're responsible for the build environment, you may not need to know as much. If you're the architect, you'd better know a lot. It depends on how much domain-specific language there is to pick up before you can communicate effectively with domain experts.
  • Opinion collection: where is an appropriate balance point between programming knowledge and domain knowledge?

    Like dws said, it depends on the domain. The balance isn't really between domain vs. programming knowledge within the programmer, but the balance of deep domain vs. shallow domain jobs in the market.

    In my experience, there are a great many jobs in the world that require a solid knowledge of general programming with little domain specific knowledge. An intelligent programmer can ramp up to sp