Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Doing too much work on one's own before looping in others

thezbook.com

Post reply on HN
Print view View original

11–20 of 395 posts

Re: Doing too much work on one's own before looping in others

#11

Post by bryanrasmussen »

alexfromapex wrote: post #7

I'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.

Or if teams are uncommunicative you can end up with not getting a usable response on concerns raised, need to march at some point and without feedback you decide to march in the direction that seems most reasonable to you. Later on it turns out that was right into the swamp.

Re: Doing too much work on one's own before looping in others

#14

Post by Steltek »

alexfromapex wrote: post #7

I'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.

I think there's a new phenomenon that needs to be addressed: poor WFH communication channels. By encouraging radio silence, so as to not "interrupt anyone", things get missed.

Also some people feel the need to tightly control group chat. Either content (no "offtopic"), membership, or # of rooms. Some chat platforms encourage this by restricting who can create/manage rooms or how rooms are linked together (discoverability).

It's an unexplored area of knowledge for most people in the new WFH life everyone's leading.

Re: Doing too much work on one's own before looping in others

#15

Post by ilrwbwrkhv »

juice_bus wrote: post #5
theandrewbailey wrote: post #3

Earlier quoted context omitted.

I'm not sure what IC means. Integration Consultant? Industrial Control?

I believe IC is "Individual Contributor" in this context.

A most bizarre terminology the industry has come up with. Almost feels a bit derogatory.

Re: Doing too much work on one's own before looping in others

#16

Post by spmurrayzzz »

ziggus wrote: post #12

Why the conflation of 'engineer' and 'developer'? That's a bit confusing.

I'm curious, what about that semantic differentiation is confusing for you?

At least in my experience, "Software Engineer" is a standard title for the kind of work the author is describing in the article and is often used interchangeably with "Developer".

Re: Doing too much work on one's own before looping in others

#17

Post by disposableuname »

theandrewbailey wrote: post #3
zachlloyd wrote: post #2

I'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?

> as both an IC and a manager

When juxtaposed to manager, it usually means individual contributor - someone being managed rather than doing the management.

Re: Doing too much work on one's own before looping in others

#19

Post by disposableuname »

alexfromapex wrote: post #7

I'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.

The original post contains

> It can also happen if the team culture is toxic and engineers fear getting criticism early in the design process.

I think the author would agree with you.

Post reply on HN