feld on Nostr: nprofile1q…33633 I'm willing to bet less than 10% of the employed workforce of ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq45uz8hvqy9v3hgyhqxqhq3gdwrxzuhawwd60a9xtcr7t64zkgg6sw33633 (nprofile…3633) I'm willing to bet less than 10% of the employed workforce of programmers care about this definition of "engineering".
The problem is that when you are involved with or exposed to open source communities you end up biased because all of the people you encounter care deeply about these things especially if they come from academia.
Everyone else? They just have "a job". They wake up, go to work, complete their tasks in the most efficient way possible, and then they clock out and go home. They have no emotional attachment to their code or their work.
This is especially true the further you get away from things that are so closely related to "the web". Go look at people who work in industrial or utilities. I worked at a power and gas utility on their security team and had to interface with programmers who have been sitting at the same desk for 15 years. They're "senior" Java developers, but know nothing outside the most narrow scope of their work. My favorite example of this was asking the dev what TCP ports their application needed open so we could schedule the network/firewall changes. They've been writing networked applications for years and yet they didn't even know what a TCP port was.
These people exist everywhere. It should terrify you, really.
The problem is that when you are involved with or exposed to open source communities you end up biased because all of the people you encounter care deeply about these things especially if they come from academia.
Everyone else? They just have "a job". They wake up, go to work, complete their tasks in the most efficient way possible, and then they clock out and go home. They have no emotional attachment to their code or their work.
This is especially true the further you get away from things that are so closely related to "the web". Go look at people who work in industrial or utilities. I worked at a power and gas utility on their security team and had to interface with programmers who have been sitting at the same desk for 15 years. They're "senior" Java developers, but know nothing outside the most narrow scope of their work. My favorite example of this was asking the dev what TCP ports their application needed open so we could schedule the network/firewall changes. They've been writing networked applications for years and yet they didn't even know what a TCP port was.
These people exist everywhere. It should terrify you, really.