Doing too much work on one's own before looping in others
1–10 of 395 posts
Re: Doing too much work on one's own before looping in others
#2I'm the author of the post - would love any feedback / similar experiences / contrasting opinions!
Re: Doing too much work on one's own before looping in others
#3I'm the author of the post - would love any feedback / similar experiences / contrasting opinions!
I'm not sure what IC means. Integration Consultant? Industrial Control?
Re: Doing too much work on one's own before looping in others
#4Re: Doing too much work on one's own before looping in others
#5Re: Doing too much work on one's own before looping in others
#6I'm the author of the post - would love any feedback / similar experiences / contrasting opinions!
I'm not sure what IC means. Integration Consultant? Industrial Control?
Individual contributor, in other words a worker as opposed to management. The author's using engineer to mean software developer; they're the workers in this context.
Re: Doing too much work on one's own before looping in others
#7I've been guilty of this at times but what I would add is a certain type of environment encourages this behavior. If the business or teammates are very reluctant to let engineers work on what they want or give harsh feedback it encourages people to retreat into their safe space and try to create something they feel is worthy of feedback.
Re: Doing too much work on one's own before looping in others
#8> the biggest mistake I see engineers make is doing too much work on their own before looping in others.
Re: Doing too much work on one's own before looping in others
#9I've been guilty of this at times but what I would add is a certain type of environment encourages this behavior. If the business or teammates are very reluctant to let engineers work on what they want or give harsh feedback it encourages people to retreat into their safe space and try to create something they feel is worthy of feedback.
Y-e-p. It's not like these retreats happen in a vacuum.