Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://social.polotek.net/users/polotek/statuses/112374085757214630">Marco Rogers (polotek@social.polotek.net)'s status on Friday, 03-May-2024 10:40:02 JST</a><a href="https://social.polotek.net/@polotek" title="polotek@social.polotek.net"><img src="https://gnusocial.jp/avatar/222890-48-20231213201011.webp" width="48" height="48" alt="Marco Rogers" style="position: absolute; left: 0; top: 0;">Marco Rogers</a><div><a href="https://social.polotek.net/@polotek/112374067372711817" rel="in-reply-to">in reply to</a></div></section><article><p>Number one is debatable. But I don't care to debate it today. It tends to make people angry. 😂</p><p>Number 2 I will absolutely agree with. I think it is part of the management role to help teams organize their work and to manage distractions. However, I don't think that is a solo management task. Engineers need to collaborate on how to be effective at manage distractions.</p><p>I am very opposed to the popular "shit umbrella" philosophy of engineering management.<br><a href="https://im-in.space/@Chip_Unicorn/112374023229088372" rel="nofollow noreferrer">https://im-in.space/@Chip_Unicorn/112374023229088372</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3030790#notice-6014751">In conversation</a><time datetime="2024-05-03T10:40:02+09:00" title="Friday, 03-May-2024 10:40:02 JST">about 7 months ago</time> <span>from <span><a href="https://social.polotek.net/@polotek/112374085757214630" rel="external" title="Sent from social.polotek.net via ActivityPub">social.polotek.net</a></span></span><a href="https://social.polotek.net/@polotek/112374085757214630">permalink</a><h4>Attachments</h4><ol><li><article><header><div>No result found on File_thumbnail lookup.</div><h5><a href="https://im-in.space/@Chip_Unicorn/112374023229088372">Chip Unicorn (@Chip_Unicorn@im-in.space)</a></h5><div> from <span>Chip Unicorn</span></div></header><div>@polotek@social.polotek.net Here is the problem:Every engineer can learn to estimate the amount of time it will take to complete something. But management does two things that ruin it:1. They turn estimation into a battle. "You said that you would be done in two months. I'm giving you six weeks!"2. They don't stop the constant flow of other tasks that interrupt engineers. If something goes down, that task takes higher priority than anything new. Saying that something takes two months of work doesn't mean that it will be done in two months. It means that it takes two months of work. Every interruption, every other task that gets assigned, every "Hey, could you look at this?" means that the task will arrive later.Those two factors utterly ruin estimation.</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Marco Rogers (polotek@social.polotek.net)'s status on Friday, 03-May-2024 10:40:02 JST Marco Rogers
in reply to
Number one is debatable. But I don't care to debate it today. It tends to make people angry. 😂
Number 2 I will absolutely agree with. I think it is part of the management role to help teams organize their work and to manage distractions. However, I don't think that is a solo management task. Engineers need to collaborate on how to be effective at manage distractions.
I am very opposed to the popular "shit umbrella" philosophy of engineering management.
https://im-in.space/@Chip_Unicorn/112374023229088372
In conversationabout 7 months ago from social.polotek.netpermalink
Attachments
1. No result found on File_thumbnail lookup.
  Chip Unicorn (@Chip_Unicorn@im-in.space)
  from Chip Unicorn
  @polotek@social.polotek.net Here is the problem: Every engineer can learn to estimate the amount of time it will take to complete something. But management does two things that ruin it: 1. They turn estimation into a battle. "You said that you would be done in two months. I'm giving you six weeks!" 2. They don't stop the constant flow of other tasks that interrupt engineers. If something goes down, that task takes higher priority than anything new. Saying that something takes two months of work doesn't mean that it will be done in two months. It means that it takes two months of work. Every interruption, every other task that gets assigned, every "Hey, could you look at this?" means that the task will arrive later. Those two factors utterly ruin estimation.

Public

Embed Notice

HTML Code

Corresponding Notice