News for hackers. Stuff that matters.
Re:Things I’ve learned in my 20 years as a software engineer by chii on Friday October 08, 2021 @06:37AM (#28797706)
you can replace the word "software" with basically any other professional work and that is still the same. I don't know what you can learn from the fact that it's a social service.
Re:Things I’ve learned in my 20 years as a software engineer by wccrawford on Friday October 08, 2021 @07:33AM (#28798051)
I've met a lot of people who are writing code to satisfy requirements and collect a paycheck. They're good people, but just don't automatically think about the end user. They stop when the requirements are met, instead of when the user will be happy.

That's what they're supposed to learn from that, IMO.

Re:Things I’ve learned in my 20 years as a software engineer by chii on Friday October 08, 2021 @08:57AM (#28798706)
> They stop when the requirements are met, instead of when the user will be happy.

that's because they are doing software "for other humans" - aka, their manager and PM, who gave them the requirements.

So the problem is not the software engineer, but the person who creates those requirements to be fulfilled.

Re:Things I’ve learned in my 20 years as a software engineer by lazide on Friday October 08, 2021 @09:52AM (#28799305)
I think what the parent may have been complaining about is essentially myopia in interpreting things - ‘well, this technically checks the box of what they ask for’ while willingly avoiding thinking about the larger context of what is being attempted or trying to understand requirements that don’t make much sense.

Don’t get me wrong - it has it’s place, and if everyone always tried to understand everything, there are a lot of organizations and situations it would be crushing - but it’s also very frustrating in many situations for those who want high quality products.

It’s the ‘not my job’ syndrome, essentially.

Re:Things I’ve learned in my 20 years as a software engineer by dragonwriter on Friday October 08, 2021 @11:33AM (#28800392)
> I think what the parent may have been complaining about is essentially myopia in interpreting things - ‘well, this technically checks the box of what they ask for’ while willingly avoiding thinking about the larger context of what is being attempted or trying to understand requirements that don’t make much sense.

I think what your post’s parent was pointing out is that in lots of environments, such myopia is just an engineers job definition, for which they will be punished if they stray. Interpreting end-user needs is someone else's job.

Re:Things I’ve learned in my 20 years as a software engineer by lazide on Friday October 08, 2021 @01:57PM (#28802116)
I think we just violently agreed, and even repeated the same last line?
Re:Things I’ve learned in my 20 years as a software engineer by wccrawford on Friday October 08, 2021 @02:27PM (#28802453)
I'm not asking that develop to go against the requirements. But it's often possible to satisfy requirements without satisfying the user, even though it's actually possible to do both.
Re:Things I’ve learned in my 20 years as a software engineer by jimbokun on Friday October 08, 2021 @11:28AM (#28800343)
Some organizations are structured such that it is difficult for an engineer to do anything else. An engineer doesn't always have access to the end user, unfortunately.
Re:Things I’ve learned in my 20 years as a software engineer by boffinAudio on Friday October 08, 2021 @06:39AM (#28797720)
Well, all economy is human economy, so yeah .. okay.

You can learn from the fact that its a social service by actively NOT resisting the truth of this fact.

Incorporate it into your thinking with every commit you make and you will become a better programmer over time.

(Corollary: those developers who forget this fact, make shitty software...)

Re:Things I’ve learned in my 20 years as a software engineer by Jensson on Friday October 08, 2021 @07:32AM (#28798040)
Everyone agrees that software is to serve humans. What they disagree about is how to best make software that serves humans.

For example, lets say you write an API that translates text. Should you assume the text the human sent in is correct and return an error? That way you can make better translations when they send the right data. Or should you try to be helpful and automatically fix spelling errors you think you've found in order to make the API more human friendly? Would make it easier but reduce accuracy.

You seem to be in the second camp, reduce power of API and make them easier to use. But lots of people think that the best way to serve humans is to make more powerful and strict API's.

Re:Things I’ve learned in my 20 years as a software engineer by boffinAudio on Friday October 08, 2021 @07:38AM (#28798082)
Either option is fine, as long as your user agrees.
Re:Things I’ve learned in my 20 years as a software engineer by Jensson on Friday October 08, 2021 @07:47AM (#28798138)
You have more than one user. Some of them will want power, other will want ease of use. You can't satisfy everyone without making multiple products.
Re:Things I’ve learned in my 20 years as a software engineer by TeMPOraL on Friday October 08, 2021 @08:42AM (#28798546)
More than that, there may be a whole stack of software components between your API and your users. In this sense, quite a lot of software is written for computers and not other humans (or, your users are other software devs).

This is to say, "all software is written for humans" is too general to be useful - the important issues are all in the details.