Live data from Hacker News

Ask HN: What are the most annoying things in software development?

news.ycombinator.com

21–30 of 41 posts

Re: Ask HN: What are the most annoying things in software development?

#21
post #19
post #18

Earlier quoted context omitted.

The underlying layers of networking failing- 1. Too many requests for an NIC to handle, 2. Certificates expiring, 3. Firewall changes closing an active port down, 4. A router failing, 5. Congestion, interference in wireless networks resulting in excessive packet loss. Hardware failing- HDDs, RAM, routers crashing, cables at datacenter being accidentally unplugged, racks being misconfigured during upgrades, maintenanc…

I can just import a 3rd party Javascript library to deal with these right?

> What are the most annoying things in software development?

The idea that everything can and should be done in JavaScript.

I know the parent comment was sarcastic, but it reminded me of this trend.

Re: Ask HN: What are the most annoying things in software development?

#22

Earlier quoted context omitted.

You mean e.g. requirements that change over time or requirements that get added during the project?

Both would be somehwat equally annoying in that they change the scope of the project.

Requirements are like deadlines. Made up things to keep us controlled.

Re: Ask HN: What are the most annoying things in software development?

#23
As a developer it seems I am subordinate and I am not privy to any business decisions or direction which is information that is not communicated, and we are often not consulted.

Never do I here, oh we are thinking of going in this direction. What do you think?

Rather it is "We ARE doing this, and we need to get it done in 2 months, how can you make it happen?"

Re: Ask HN: What are the most annoying things in software development?

#24

As a developer it seems I am subordinate and I am not privy to any business decisions or direction which is information that is not communicated, and we are often not consulted. Never do I here, oh we are thinking of going in this direction. What do you think? Rather it is "We ARE doing this, and we need to get it done in 2 months, how can you make it happen?"

> As a developer it seems I am subordinate and I am not privy to any business decisions or direction which is information that is not communicated, and we are often not consulted.

Either your company has a bad culture, or your Product Manager doesn't believe in a collaborative process or you are not working for a small enough company. :-)

Re: Ask HN: What are the most annoying things in software development?

#25

Earlier quoted context omitted.

Both would be somehwat equally annoying in that they change the scope of the project.

Requirements are like deadlines. Made up things to keep us controlled.

Requirements keep management controlled, exposing them to the concept that change has cost (manager here).

Re: Ask HN: What are the most annoying things in software development?

#26
post #25

Earlier quoted context omitted.

Requirements are like deadlines. Made up things to keep us controlled.

Requirements keep management controlled, exposing them to the concept that change has cost (manager here).

Setting the scope of the work is what is keeping management controlled.

E.g. "In Version 1.0, it will talk to these 3 services only..."

But that is different from 'requirements' which I take it as 'things that are required' and have a non-negotiable connotation about them.

E.g. "It must work with all of our services"

Since it is not know which requirements are actually required and which are BS, it may be better to call requirements 'requested functionality' and what is planned to be delivered 'project scope' and drop the requirements word altogether.

Re: Ask HN: What are the most annoying things in software development?

#30
Some things here (meetings, bad managers, etc.) are all too true, but not unique to software development/developers!

The most frustrating is when I am completely convinced a change I make is going to resolve some failed tests, and then I run the tests, and something still doesn't work. Or I fix something and cause another problem. I enjoy the challenge of getting everything right, but just feel betrayed when I'm convinced I do it right and I'm wrong.

Can't outsource that, though. What I would love to outsource is the actual writing of the testware. I like thinking up all the test scenarios, but wish I could do a brain dump and have someone else write the testware.

The other thing I wish I could outsource is any documentation creation or review. Probably because I can think a lot faster than I can write, and then also feel like I have to take extra time to document things precisely because I might not be able to have a dialog with whoever is reading the docs.

Post reply on HN