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

[–] [email protected] 21 points 11 months ago* (last edited 11 months ago) (1 children)

Also that urgency is rooted in job insecurity, not even customer impact. They just don't want to look bad.

E: which I mean fair enough, me too, but still.

[–] [email protected] 8 points 11 months ago (1 children)

But if you do your job properly, you don’t end up in this situation.

[–] [email protected] 7 points 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.

[–] [email protected] 19 points 11 months ago (3 children)

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.

[–] [email protected] 12 points 11 months ago (1 children)

Welcome to the professional world where everything is iterative and and 95% of your clients (internal or external) are data illiterate and don't want to learn whatever self service tools you build.

[–] [email protected] 12 points 11 months ago (1 children)

Yeah it’s going to wild I can already tell. I know your right to as it’s only a small company I work for, less than 10 of us and they all complain about stupid things the clients do.

I have a colleague who is the contact for a dude that takes a picture of a site with his phone, so he photographs the monitor. Which I know isn’t that unusual, but wait.

He then emails this to himself, perhaps to have it on his desktop. Proceeds to print off the image, but not just the image, but the image as it appears in the email. THE ACTUAL EMAIL.

Then he will annotate the printout and I shit you not, will take another photo, but this time of the printout. Inception level shit.

He then sends that in by ~~carrier pigeon~~ email.

[–] [email protected] 10 points 11 months ago

Sorry to break this to you.....but this won't be the last time that happens. In fact, it'll probably happen on more projects than not.

[–] [email protected] 1 points 11 months ago (1 children)

that just normal software development with contacts and waterfall. usually with agile it's meditated to some extend, because with agile the customer is on board and cannot say afterwards i didn't want it.

[–] [email protected] 3 points 11 months ago

We don’t do agile, my boss usually keeps it all in his head and I have to pry it out of him what he wants done.

Also, I think you dropped this “a” from one of your words. Hehe