So much this.
I’m in my first professional role and the first project was completed and aside from my boss I was the only other dev. So I was naturally excited for their (clients) feedback on it.
Well fast forward a couple of months where they really didn’t interact with the application much and then came the queries and then not understanding how to use it. Find boss sets aside 10 days for me to write some documentation with screenshots of all the journeys (free of charge).
Again, tumbleweeds. Then all of a sudden it’s boom emails a plenty.
Can you fix this, this is a major bug kinda emails. Like it isn’t a bug, you don’t know how to use it.
Now we are dumbing down the software to make it more align with what the business is used to, which is fine but even my boss has said (as I over think and want to reply to things instantly) that just because they have come to life doesn’t mean we drop everything else to tend to them now.
derfl007@lemmy.wtf 11 months ago
Behind every ❗️❗️❗️🚨🚨🚨URGENT🚨🚨🚨❗️❗️❗️ there is a person who’s about to miss a deadline and, instead of working on themselves to prevent that from happening in the future, makes it the developer’s deadline to miss
pomodoro_longbreak@sh.itjust.works 11 months ago
Also that urgency is rooted in job insecurity, not even customer impact. They just don’t want to look bad.
jaybone@lemmy.world 11 months ago
But if you do your job properly, you don’t end up in this situation.
pomodoro_longbreak@sh.itjust.works 11 months ago
Yeah but we’re all learning, so a certain amount of grace is called for.
Anyway, not to counter my own point. There’s a line, is what I’m saying, and it’s blurry.