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

Instead of loafing, you could also collect more context. Talk to various stakeholders to better understand the context of the problem. Read about company policies or market developments that made this necessary.

Boring stuff, I admit (the reading at least; I enjoy talking to stakeholders), but it can give you a much deeper understanding of what you're working on.



I agree with your advice but have to remark that often times stakeholders are not open to talk to techies. I loved those who were but most weren't.


They need to maintain kayfabe, otherwise all the BAs, PMs, POs, EMs would become flight risks.


Then don't tell them you're a techie.


Pretty difficult when you are hired as a programmer and are introduced during an all-hands meeting. :D




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

Search: