Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the parent post was spot-on.

> an engineer who’s expected to attend all the meetings and also be able to turn around designs and code is just not going to be as effective

Then maybe they are having too much asked of them. Or perhaps the meetings are actually more important than the coding tasks and that is why they get priority.

People need to learn how to delegate and how to let go. There is only so much time in a day. Either you delegate production tasks to someone else, or you let go of control and let people make decisions in meetings without your input. Both are valid responses to time pressure, and usually you need a mix of the two.



>Or perhaps the meetings are actually more important than the coding tasks and that is why they get priority.

If that is the case. Then the programmers KPI and perfomance review should be based on how many of these meetings they attended.

Hell if meetings really are more important and add to productivty. How about paying meeting attendance bonuses?

No one will put there money where there mouth is because they know it's a waste of time to have a meeting that could be an email.

They need to look busy to justify their own salary




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: