[rvasa]

tl;dr - Yes, it opens more options.

== Long version == Depends on: (i) the job, (ii) quality of CS degree, (iii) career ambition/plans, and (iv) companies/people/culture, (v) project, and (vi) your ability/motivation/persistence.

A lot of basic programming can be picked up over time if you are keen. For many people, structured education is helpful when learning more complex material -- concurrency, compiler construction, advanced data structures, optimisation.

Some companies insist on a CS/SE degree (esp. consulting). Some projects state that all engineers must have formal qualifications.

There are a lot of Dilbert bosses out there -- they do not know/care/will-ever-know about Github profiles. There are bosses that just want stuff done. If you ever have to work for them, a paper with shields on it helps.

[fritzvd]

Exactly. The more technical and broader hollistic look of a computers, performance is something I think a CS is expected to be mindful of. But it does not mean they all are.

I think it also depends on your drive and your niche. I am in a GIS world and am very enthusiastic about programming. Where most people are more interested in the application than in the backend. If you know your target group you can cater for them specifically and understand their problems better.

So of course it depends (as always), but to be able to program and know another field is VERY valuable I'd say. To have a CS grad in the group too, but it would serve a more specific purpose.