3 ms·
> Absolutely not ... That is micro-management and you said it yourself that it retracts from your usefulness to your superiors. I think I also said that I'd be
by dahart 10y ago
> Absolutely not ... That is micro-management and you said it yourself that it retracts from your usefulness to your superiors.
I think I also said that I'd been wrong about that, didn't I? I was there and I don't think it was micro-management. It ended up being a valuable experience for me that has made me a better engineer. Given the amount of overhead and the details of what happened, the "why" is an interesting story with a surprise ending in my book.
> Have we forgotten brain context switches penalty? ... This is a somewhat directly measurable loss of productivity.
We have not forgotten, it just turns out to be often negligible compared to the penalties of solving the wrong problems and failing to work as a team. Not always, but often enough that context switches definitely are not the biggest impediment to productivity.
> You also admitted this is about trust but also insisted programmers shouldn't treat often check-ins as lack of trust.
You misunderstand again, I was demonstrating that I used to think that it was lack of trust. I now know that it was not a lack of trust, frequent time-based communication is a necessary part of getting a job done right. I was given more trust than I'd realized, and my complaints about overhead actually eroded some of that trust. I am pretty sure that asking managers to talk to you less, and complaining about estimates is more or less guaranteed to make managers trust you less. Assuming that requests for communication equals a lack of trust will take you to bad places. But hey, your mileage may vary, maybe I'm wrong. You don't need to listen to me, you are on your own journey and you will learn your own lessons. Let me know if you find out differently.
> The part that's concerning me here is that you seem to want to shoe-horn a singular process on different kinds of people. If you were my supervisor, I'd not be okay with that.
What singular process is that, do you imagine? Communication? You are absolutely certain that what I've talked about is more rigid and limiting than what's in the manifesto? You are so sure I'm wrong that you feel justified in starting to make your arguments personal? Would you bring what you wrote above to your next job interview and expect it to improve your odds?
- pdimitar 10y agoI apologize if you felt this was personal. As an Eastern European for me the slightly heated odd discussion isn't hostility or personal attack at all. I do understand the disconnect however. You have my apologies if you want them. =) I think we're both generalizing extreme cases. I don't find myself in a strong disagreement with you -- only on semantics and/or specifics. As for an interview, I am very open about what things I don't find okay if I manage to detect them during the interview. I don't however go out of my way specifically to list my requirements since that comes off as being a douchebag and I very much prefer adaptation and mutual compromise if we start working together. I am not afraid to lose an opportunity if I get red flags. The interview is, after all, a mutual process. > Assuming that requests for communication equals a lack of trust will take you to bad places. No, please. I never said that. I am saying the following: if things go really well and expectations and promises aren't broken, I'd expect you to ease off the regular meeting requirements. Nothing more, nothing less. Enforcing a fully linear and regular process is in my eyes unrealistic and I'll return to my previous analogy once more -- it's like pretending that the weather is solid 20^C every day, 365 days a week. Communication and trust are paramount. Everything else comes after that. I have long ago put myself in the shoes of the managers and I do understand their needs. What I don't understand is the insistence of flat processes without any adaptation to (1) the current work load and (2) individual specifics.