4 ms·
This the most interesting response to date. Not because of the reason you're here, but I can see the parallels to what I used to do in reverse. I spent over a
by HeyLaughingBoy 10y ago
This the most interesting response to date. Not because of the reason you're here, but I can see the parallels to what I used to do in reverse.
I spent over a decade writing software for a medical device manufacturer and was at a fairly senior position. On any given day I had to interact with biochemists, mechanical engineers, electrical engineers, production floor technicians, technical support, or customer hotline people. Most of these had little or no interest in software, or the internal operation of a very complex instrument. But yet I had to find a way to translate the reason for some obscure fault or weird behavior into whatever their frame of reference was so they could either understand it and fix it, or explain to the "customer" (internal or external) what went wrong, why, and how to correct the problem.
Just had to say that because a lot of my support tasks seemed very similar to your remark about receiving a technical document and having to make sense of it to understand its applicability from a legal perspective.
- stult 10y agoI think what you and I are experiencing is the core trend of software development away from purely technical challenges toward domain-specific adaptation of existing technology. Not that there aren't cutting edge coders building innovative tech. There's just a massive amount of non-innovative tech work which is now easily achievable because the infrastructure and labor pool are up to the challenge at affordable prices. Building a website or an app isn't usually a technical feat anymore, but rather a routine activity. It's like construction, just nailing beams to other beams, with everything standardized. The bulk of the work ends up being collecting and refining requirements to ensure that the tech serves the business needs. You don't need brilliant coders to achieve that. You need people who are moderately competent in understanding the tech and are extremely fluent in understanding the business challenge. That's why domain-driven development is kind of hot right now. It drives people from the tech end toward attaining fluency in the domain and people from the domain toward attaining fluency in the tech. You came from the opposite end as me, but we're driving toward the same middle, which is someplace where people understand how to take a set of business needs and translate them into functional code. It's nothing new, really, it's just spreading to encompass a much larger percentage of the workforce than ever before because tech is becoming so pervasive.