4 ms·
I'm not sure what it is, or if it's justified, but I've always hated having to explain what I'm doing and why. I think that I will involve people as needed and
by lawnchair_larry 10y ago
I'm not sure what it is, or if it's justified, but I've always hated having to explain what I'm doing and why. I think that I will involve people as needed and when needed, and assume others will do the same. Most senior engineers I've worked with have been this way.
Are there effective teams who don't do anything like this at all?
- adrianratnapala 10y agoI often have this feeling -- but it is because it's impossible to explain a mass of technical background to connect my current work to buisiness goals (assuming there even is such a connection). That's a process problem. Teams I was on with this problem needed to get better at spreading such background knowledge (e.g. by having code review).
- clifanatic 10y ago> Are there effective teams who don't do anything like this at all? I'm pretty sure that the only effective teams are the ones who don't do anything like this at all.