3 ms·
At my previous company we had the same problem, where people from all over the company would come up to us developers constantly asking us to do things which we
by grecy 15y ago
At my previous company we had the same problem, where people from all over the company would come up to us developers constantly asking us to do things which were great, but not really what we were supposed to be doing. Like you, we never got around to doing something that we said would only take a day.
One week we all decided to keep a notepad and paper next to our desks and keep a log of every time we were interrupted and asked to context switch and do something random. It was so bad, before the end of Monday our boss was so dumbfounded he completely re-jigged everything so it wouldn't happen like that again.
We ended up calling one developer pair the "consulting developers" each week, and only that pair could be interrupted. There was a huge sign above their desk advertising them for the week. We sacrificed one for the good of all, and it worked really, really well. AFAIK, they are still doing that.
- badclient 15y agoThis is great to hear. It is pretty much the problem/solution that I've diagnosed and stated in another post: I think the root issue is they need a developer who just does tech support for the other 10 non tech people. And then a developer who can actually build shit quietly. I will push this stance more aggressively having read your post.