Comment

Comment by bgro

I'm probably doing standups wrong, but I find it useful for devs to (briefly) talk about what they're working on. Bring up something you're struggling on and maybe I can jump in and help. Let people know you're working on a hotfix today, so try to not bother you. Get early feedback on priorities from the PM if you're going down the wrong path or a customer changed their mind on something you didn't hear about.

I also like to have a casual dev text chat going throughout the day so you can post things like "Why isn't customer history appearing on this page?" "That page uses a one-off modified version of that query that doesn't grab history because we don't need to display it there. It used to increase load time by 30%."

Sometimes the flow of this is just easier in person, and a dedicated short meeting where everyone speaks up about their own work doesn't feel as much like backseat accusations.

It does require people actually feel comfortable asking for help, and it requires people to volunteer their guidance.

As I see more and more devs and different work places, I can't believe how common it is to just sit in your corner and struggle while refusing to ask for help and refusing to speak up when someone on your team is actually asking for help.

Is this communication failure the norm at your places of work? What's the deal?

parent bgro 4 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton