Honestly, I'm in two minds about it. If I didn't have the domain knowledge I do (I did a masters in another field before starting cs, and since have performed r

Honestly, I'm in two minds about it. If I didn't have the domain knowledge I do (I did a masters in another field before starting cs, and since have performed research in many varied fields of interest) I wouldn't be half as successful or have anywhere near the range of experiences to draw on. Of the ~50 or so coders I've hired over the years for my co, the best were always ones with domain knowledge from another field. They weren't the best coders from a technical point of view, but were the best at being able to deliver working software to clients faster. More often than not the ones without extra knowledge were unable to grasp the domain problems, and their solutions always needed rejigging. Edit: By being unable to grasp, I mean that the distance from their solution to the optimal solution was always quite large. More often than not their design, while designed for extensibility was flexible in a dimension that didn't move towards the optimal solution. So the extra engineering time was wasted. I don't know that I would hire a pure CS grad again, and all the interns I have now I strongly recommend they concurrently study other fields. Computers are a means to an end. I suggest studying both the means and the end.