Live data from Hacker News

I have a theory that software drives people insane

graybeard.ing

11–20 of 206 posts

Re: I have a theory that software drives people insane

#11
post #4

Software development untethered from the practical realities of the customer / user is what drives people insane. When developers are required to interact with the customer on a regular basis , the freewheeling effects described in this article are damped massively. The potential for insanity goes off the charts when the development team is siloed away in solitary confinement and the only interactions with the client…

Talking to the users, allowing them to show you what they are trying to do with your software, almost feels like cheating, because of how easy things suddenly appear to be when uncertainty fades away.

Obviously, the number of uniquely different users has an influence, and users most often do not truly know what they need, but that's our job to tease appart.

Turns out the users most often benefits from small changes that reduces friction toward achieving their goal. Any time saving will be appreciated, but only if it can be trusted to work. Nothing worse than the dread of knowing an action might or might not work randomly.

I use most software today with a constant sense of fear that the next action will break something and waste my time. Undo probably doesn't work properly anyways

Re: I have a theory that software drives people insane

#12

> Not in the "wash your hands every thirty minutes like Howard Hughes" kind of way, Hold on, this isn't that crazy in today's day and age. I used to wash my hands basically only when using the restroom or before eating. Since the pandemic though, I started upping that a lot (not every 30 minutes, but pretty frequently) and since then almost never get sick.

The Cochrane review of "physical interventions to interrupt or reduce the spread of respiratory viruses" that infamously does not find a significant effect for masking does find significant effects for hand washing.

Re: I have a theory that software drives people insane

#13
post #4

Software development untethered from the practical realities of the customer / user is what drives people insane. When developers are required to interact with the customer on a regular basis , the freewheeling effects described in this article are damped massively. The potential for insanity goes off the charts when the development team is siloed away in solitary confinement and the only interactions with the client…

I think this goes both ways.

More actual interaction between end-users and programmers makes the end-users better at reporting bugs and describing what they want (and at having an idea how complex a certain request actually is).

Because the multiple translations from customer wish to project manager language to backlog items are all lossy.

Re: I have a theory that software drives people insane

#14

> Not in the "wash your hands every thirty minutes like Howard Hughes" kind of way, Hold on, this isn't that crazy in today's day and age. I used to wash my hands basically only when using the restroom or before eating. Since the pandemic though, I started upping that a lot (not every 30 minutes, but pretty frequently) and since then almost never get sick.

Anecdote: During the pandemic I added washing my hands every time I get back to my office building (and specifically after interacting with surfaces the public interacts with) to my usual hand washing (after bathrooms and before eating, just like you). I keep a towel in my hand for any door handles between the restroom and my office door. Since doing this I feel like I've noticed fewer illnesses, too.

Re: I have a theory that software drives people insane

#16
The insanity the author is describing sounds like normal corporate BS to me. Everybody wants to "raise concerns," everybody is looking for an idea to take credit for, everybody has a reason your idea won't succeed. I'm pretty sure this is the same whether you're making software or advertising campaigns or plastic cups.

I once tried to explain a pointless debate over the definitions of "acceptance testing" versus "regression testing" to a non-tech person, and they said that was the most relatable thing I'd ever told them about my job.

Re: I have a theory that software drives people insane

#17
I’ve always thought that this principle explains all sorts of cultural phenomena, from the tech industry having a poorer work-balance compared to others (the pace of development is only limited by how many hours you must sleep!) and programmers seemingly having worse engineer’s disease than in other disciplines (if software can do anything and know everything, how could we, the lever-makers, be any less than our creations?).

Re: I have a theory that software drives people insane

#18
post #11
post #4

Software development untethered from the practical realities of the customer / user is what drives people insane. When developers are required to interact with the customer on a regular basis , the freewheeling effects described in this article are damped massively. The potential for insanity goes off the charts when the development team is siloed away in solitary confinement and the only interactions with the client…

Talking to the users, allowing them to show you what they are trying to do with your software, almost feels like cheating, because of how easy things suddenly appear to be when uncertainty fades away. Obviously, the number of uniquely different users has an influence, and users most often do not truly know what they need, but that's our job to tease appart. Turns out the users most often benefits from small changes t…

"What problem are we trying to solve?" is a question I have to ask constantly in corporate development environments, and rarely does anyone presenting the task to be done actually know the answer!

It's very frustrating.

Re: I have a theory that software drives people insane

#19
post #4

Software development untethered from the practical realities of the customer / user is what drives people insane. When developers are required to interact with the customer on a regular basis , the freewheeling effects described in this article are damped massively. The potential for insanity goes off the charts when the development team is siloed away in solitary confinement and the only interactions with the client…

The problem is it's often the devs themselves who request the siloing. I used to assume otherwise, as I think the way you do. And then I had a lot of my devs rebelling because I was keeping them from their "real work" by having them deal with users.
Post reply on HN