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

I disagree: I'm a programmer; I have "some" ideas and I "implement" them. Works for me.


I disagree: I'm a programmer; I have "some" ideas and I "implement" them. Works for me.

I am also a programmer and it also works for me.

But grandparent was addressed to OP, who has already self-identified as a PHB, a totally different audience.

When another programmer talks about "implementing some things", I know exactly what he's talking about. He's going to dig down at his terminal and make things happen.

But when a PHB says the same words, it has totally different meaning. Why? Because these are "fluffy" words which infer different things from different sources. A PHB "implementing some things" probably means project plans and meetings, not coding in the trenches.

I think that the most important thing for OP to do is to stop thinking like a PHB and start thinking like a programmer. In his case, this means focusing on specific details and digging more than 1 level below the surface, 2 things at which PHBs are notoriously weak. If he continues to think "some" and "implement", he'll never shed his PHB skin and grow the new programmer persona he'll need. That's all.


You should try having "a few" ideas and "whipping them up". It's changed my whole perspective.




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

Search: