Hacker News new | past | comments | ask | show | jobs | submit login

One little piece of advice: your priority is giving work to your reports. Avoid at all costs that they're idle. To achieve that, you must plan to be idle yourself half of the time, so you can attend them when they need it (they will.)

The other half of the time is to explain your bosses what your team is doing, so if you're thinking of programming yourself, think again.

Edit: for both halves you absolutely need to know at all times what everybody's doing, how they progress, what obstacles they're finding.




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

Search: