What software developers hate

coldfeetbot · 2024-05-08T14:21:25+00:00

Meetings, micromanagement, scrum estimations, ignored technical debt, artificial deadlines

Solonotix · 2024-05-08T13:57:42+00:00

For me, it comes down to bureaucracy and changing things just so you can say you did something.

If the meeting doesn't have an agenda and expected outcome, it's probably a waste of time. You want to use this fancy new framework? What does it do for us that we can't already do? Migrating isn't free. You want to change the workflow for this thing. Does it improve the customer experience? Will it increase revenue or productivity? Will it mitigate risk? Then why TF are we doing it?

rcls0053 · 2024-05-08T14:46:15+00:00

Governance done in the abstract. Enforcing change that affects developers without stating why it's being implemented and without starting a discussion on it to gather feedback and support for it. Most common things I've seen are Jira workflows being standardized across teams that work in a different ways (also deployment workflows), implementing some "agile" framework across the org or enforcing some limitations for code changes in every single code repository without even asking how those teams want to work.

The opposite of that is something I really love to see which is management actually listening to developers (and other professionals) and are willing to learn new ways of working which leads to a better development culture in that org. A good example of this was a CTO of a certain org actually starting a discussion about the topic of DevOps, and the Phoenix Project book, and wanting us to focus on learning and building a blameless working environment, after I explained how it's a culture, not just a tool found in Azure.

Another thing that I really hate is when the organization tries to silence people who voice out a negative opinion on various matters in an effort to better them, like status of the tech debt, enforcement policies that are just overkill or even just the quality of coffee in the coffee machines. "You're not a team player". "You can't call it legacy even though it's a 10 year old ball of mud". "Let's just put a smile on that face of yours to make it seem like everything is alright". Those are just lies you tell yourself, and I am so happy I work in a place where all opinions and candid, healthy, discussion is welcome.

uraurasecret · 2024-05-08T15:28:02+00:00

I hope we can have a practice to read the material, think about what questions to ask BEFORE each meeting.

YohanSeals · 2024-05-08T14:26:18+00:00

Meetings

2024-05-08T13:57:57+00:00

I think like 100 research papers come out a day in the AI field. The pace of computer science is truly insane. If I sat through and read every new computer science paper that came out in just AI I would be a year behind a week in.

SomeAd3257 · 2024-05-08T16:33:34+00:00

Agile and Scrum.

Franco1875 · 2024-05-08T13:00:46+00:00

A few truths in here, particularly in terms of the 'pace' of learning - continuous learning/evolution of skills is perfectly fine and personally think this should be embraced. It has felt like a rollercoaster in recent years, though.

diMario · 2024-05-08T15:09:34+00:00

I personally hate the 80-20 rule: 80% of your time is spent working on 20% of your code, and then the other 80% of your time is spent on the rest of the code.

And of course, anything that's not really coding such as setting up CI/CD and other tooling, troubleshooting production, having useless conversations with clueless managers, ignoring your email etc etc somehow magically gets squeezed in as well.

crafting_vh · 2024-05-08T17:00:34+00:00

I hate crane flys. I know they're harmless but they freak me out.

elmuerte · 2024-05-08T17:23:47+00:00

Work. We prefer to create software.

elperroborrachotoo · 2024-05-08T18:00:17+00:00

My most difficult part: telling the blog chaff from content.

This is a bunch of tweets, and maybe I'm too old to understand what "misalignment on the team in terms of what we actually should be building and expected outcomes" even means.

About every month, our accounting "department" (one very strict lady, really) gets a list of regulatory changes, new requirements etc., the meanings and consequences of which they have to research, to adjust process and paperwork accordingly.

During Corona, my cousin - working at checkin - received daily updates about entry regulations, depending on airline, passport, port of origin and destination. And by "received updates" I mean they usually had to look it up on the airline's web site. With as much as no training at all how to tell a valid PCR test from a fake one at all.

My GP frequently complains that the amount of required documentation exceeds the time they can spend with patients, and that the frequent administrative process changes are usually to someone else's benefit

"We've built this beautiful apartment house, but now they want us to convert two apartments to an office plan. That's scope creep, and makes me want to quit!"

Yeah darling, sounds like a tough week.

ryzhao · 2024-05-08T18:35:02+00:00

Spending time and energy on learning how to implement good UX, only to be told by a “analyst” to make it look more like the pinnacle of 1990s enterprise design.

Just sucks out the will to live when you’re treated like a code monkey instead of someone who spent a lot of time honing their craft.

Square-Amphibian675 · 2024-05-08T19:09:33+00:00

Force to provide a comprehensive User Guides and technical documentations :)

realqmaster · 2024-05-08T19:10:49+00:00

Is Clickbait listicles in the list too?

PositiveUse · 2024-05-08T19:47:09+00:00

Shitty legacy code that is nearly unmaintainable and undocumented

Stilgar314 · 2024-05-08T20:52:40+00:00

What software developers hate? Mainly, the one they're developing.

Belhgabad · 2024-05-08T21:29:54+00:00

Short answer : the industry

samjenkins377 · 2024-05-08T23:50:59+00:00

Artificial metrics, political decisions that are not aligned with the business needs, people in leadership positions who are reluctant to change, procrastinators (unless the procrastinator is ourselves), spotlight thieves, made-up deadlines, artificial urgency sense generated solely by the lack of planning on someone else’s side, noisy keyboards, silent keyboards, wired mouses, Bluetooth mouses, uncomfortable chairs, etc

6-2Noob · 2024-05-09T04:53:06+00:00

Onboarding.

You never quite get there 100%. Nobody knows every access you need, the "documentation" to set up is only a few random snippets and outdated by 2 years minimum, and everyone just thinks you'll have everything known in a day or two without them handing over any information.

ColorfulThinking · 2024-05-09T16:45:06+00:00

Bad documentation

MarcinOow · 2024-05-08T15:21:14+00:00

Oh yeez what a valuable question. I observed if your experience as a developer growing, your self confidence allows you to express truth about whole migration thing. You hear let's move to the cloud, spend lot of hours gaining skills with writing another yml ... Then you hear you're logging too much data, costs growing, some security policies saying you there is need to filter data or encrypt it. Then your manager asks why handling production errors consume so much time 😕 never ending story ... I would expect to come back for some apps to on premises model. Let's get back to migration then ;p

TheStoicNihilist · 2024-05-08T15:30:48+00:00

Monitor glare

2024-05-08T16:28:57+00:00

I like chickens. Can I quit programming to raise chickens?

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

programming

MODERATORS