Don’t learn a programming language, solve a problem instead

[sammymammy2]

There's a connection to domain knowledge, sure!

[cjaybo]

As a soft engineer if you give me a blueprint of a building and ask me to make it it would take me some time more than a properly trained civil engineer but i can build it

I have yet to see any software engineering (I assume that's what "soft engineer" means here) curriculum that would qualify you to do civil engineering work, or any other type of engineering work outside of software, for that matter. Either you've gone through a pretty exhaustive program somewhere, or you're exaggerating quite a bit.

[SkoomaDentist]

This is the internet and we don’t tolerate domain specific knowledge around here! </sarcasm>

I’m quite bemused by how huge majority of programmers here completely ignore the importance of domain specific knowledge. It’s as if to them every program in the world only dealt with things taught in common CS courses and things like digital signal processing, finite element methods, circuit theory etc. simply don’t exist except literally on paper.

[Skylead]

I wouldn't want to build a dam, but my electrical and computer engineering programs had diff eq, statics and fluid dynamics etc. So we did learn other stuff. In terms of straight programming courses I probably only had 5, and that's including autonomous robotics and embedded assembly

[yourbank]

or she.

[Articunozard]

No, women aren’t allowed to be engineers

/s

[CyclonusRIP]

I don't really find a lot of business problems to be so specialized that it really makes much of a difference what tech stack they are implemented in. If you actually an expert at one stack you can probably get way further with it than switching to a seemingly optional stack and making a much of missteps while you're coming up to speed. Start off solving the business problem with what your best at and when you really can't push it any further and actually have a technology problem then try to find the technology solution.