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

It is unprofessional for someone to just assume their co-worker has done a bad job, no?


I think documentation feels like a bit of a sink, as written documentation starts degrading (in terms of being up-to-date) as soon as it gets published, and it gets extremely frustrating going through docs and not feeling like you can "trust" what you're reading


It depends on whether you have better people skills or better reading comprehension. I use whatever source gets me the answer fastest as I am skilled in both. That's not true for everyone, but being able to use a decision tree where you have both options is a big part of being a 10x programmer IMHO.

Is your PM/BA/Coworker so overwhelmed they can't think straight (Mind your P's & Q's)? -> Go look at the docs.

Can you politely insert yourself into a conversation with a coworker given their bandwidth and their ability to understand functional and technical requirements and quickly explain what is required? -> Schedule a short meeting.


Not if every other coworker they've ever had has done a bad job at this particular thing, no. That's just rational




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

Search: