Ask HN: What's a developer experience issue at work that makes you want to quit?

8 points by jamghee ↗ HN

15 comments

[ 3.5 ms ] story [ 49.3 ms ] thread
Dynamic method dispatch done in an un-grep-able way. Gets me every time.
I have short horror story for You :) (in 3 words - eat it Hemingway :))

(prefix + '-' + verb)(arguments)

You mean Jira? or other than Jira?
Yeah sorry I should have said aside from Jira
ive been using Jira at my new job and i sorta like it better than pivotal.

i might have not faced these issues yet but whats wrong with jira

Data scientists writing terrible unmaintainable code
Or computer scientists writing code with too many layers of abstraction. It can go to both extremes.
legacy code base, no documentation.
I'm with you on this one. Constantly reverse-engineering old requirements, puzzling over someone's clever coding trick, it is easy to become terminally fatigued.
My manager decided that we need to use an “ETL NoCode Solution” they used it at his last job and he said its good.

we had one 45 min demo then gave feedback like it’s not granual enough, not enough control for our use cases, no tests etc.

Months later he tells me the contract has been signed and he wants me to lead the onboarding.

i do my best thinking ill get a raise since im taking on much more work and ill get good experience, i get a decent raise but not enough to make me stay.

the tool made me absolutely miserable tbh, the support they had was useless, they over promised on what it can actually do. the amount of tool-breaking bugs it had were also too many to count. e.g: changing the mysql version connector for one data point would break all other diff ones in use.

i gave the feedback to my manager and that i think we should cut our losses short and stop the migration. he decides to do nothing

i quit :)

On another side, I was in a company building custom ETL solution, they are building 5th attempt where previous three are still in production, it is total mess.

It takes top talent to build an ETL solution from scratch.

Legacy microservices that turned into a distributed network monolith. Ah yes let's use location service to make an http call to location service for some db data.
I just witnessed this happen. A service that is nothing but a proxy for another service, plus some caching. A client library might be better.
Entire management and senior eng chain of the company fundamentally not understanding the work or the requirements needed for devs to succeed. This is a very large company you interact with daily. A major one.
I'm not a developer but I dislike offering a bad experience to the ones we have.

I run a service that provides data, I've bent over backwards to speed it up.. but there's only so much I can do until another team moves the source somewhere better