3 ms·
It's not just about rebellious. It's also about just about "just do something about it" without asking the boss/teamleader. The problem is often just how much f
by _trampeltier 5y ago
It's not just about rebellious. It's also about just about "just do something about it" without asking the boss/teamleader. The problem is often just how much free time you have on work to do such things. Another problem is, if you fix small things allways by yourself in the background, the real problem might stay forever.
- lbriner 5y agoThis is true but also where wisdom comes in. It should be OK to spend 5 seconds saying, "I saw X, is it OK for me to fix it?", which allows people to know of a problem they might not know and also for management to say, "Don't bother, we are going to replace that next month". As a more experienced engineer, I am more accustomed to what is reasonable to "just go and fix" and what needs dicussion. I have devs who sometimes spend 2 or 3 days+ doing something that could have been done much quicker if they had discussed what they planned first instead of trying to be helpful!
- varjag 5y ago> It should be OK to spend 5 seconds saying, "I saw X, is it OK for me to fix it?" "Let's have a meeting about this in 10 days."
- rightbyte 5y ago> I have devs who sometimes spend 2 or 3 days+ doing something that could have been done much quicker if they had discussed what they planned first instead of trying to be helpful! My experience is that you might get suggestions that are nowhere near how you planned to do it and it wrecks your mental picture of how it should be done. Discussions ofent lead to backseat development.