Why is that bad? You write better code when you actually understand the business domain and the requirement. It's much easier to understand it when you get it direct from the source than filtered down through dozens of product managers and JIRA tickets.
Having had to support many of these systems for sales or automation or video production pipelines as soon as you dig under the covers you realize they are a hot mess of amateur code that _barely_ functions as long as you don't breath on it too hard.
Software engineering is in an entirely nascent stage. That the industry could even put forward ideas like "move fast and break things" is extreme evidence of this. We know how to handle this challenge of deep technical knowledge interfacing with domain specific knowledge in almost every other industry. Coders were once cowboys, now we're in the Upton Sinclair version of the industry, and soon we'll enter into regular honest professional engineering like every other new technology ultimately has.
Not sure why this is being downvoted. It’s spot on imo. Engineers who don’t want to understand the domain and the customers won’t be as effective in an engineering organization as those who do.
It always baffles me when someone wants to only think about the code as if it exists in a vacuum. (Although for junior engineers it’s a bit more acceptable than for senior engineers).
Customer interaction has imo always been one of the most important parts in good engineering organizations. Delegating that to Product Managers adds unnecessary friction.
Having spent more hours than I care to count struggling to control my facial expressions in client-facing meetings your assertion that that friction is unnecessary is highly questionable. Having a "face man" who's sufficiently tech literate to ask decent questions manage the soft side of client relations frees up a ton of engineering resources that would otherwise be squandered replying to routine emails.
Nextgrid|15 days ago
themafia|15 days ago
Having had to support many of these systems for sales or automation or video production pipelines as soon as you dig under the covers you realize they are a hot mess of amateur code that _barely_ functions as long as you don't breath on it too hard.
Software engineering is in an entirely nascent stage. That the industry could even put forward ideas like "move fast and break things" is extreme evidence of this. We know how to handle this challenge of deep technical knowledge interfacing with domain specific knowledge in almost every other industry. Coders were once cowboys, now we're in the Upton Sinclair version of the industry, and soon we'll enter into regular honest professional engineering like every other new technology ultimately has.
SoftTalker|15 days ago
Insanity|15 days ago
It always baffles me when someone wants to only think about the code as if it exists in a vacuum. (Although for junior engineers it’s a bit more acceptable than for senior engineers).
secondcoming|15 days ago
Insanity|15 days ago
forgetfreeman|15 days ago
optimalsolver|15 days ago
https://www.youtube.com/watch?v=hNuu9CpdjIo
whoisthemachine|15 days ago