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

> So it's important to figure out what kind of manager you have, and try not to be the slow guy on a team full of quick-hack people. You won't look good and nobody will be happy.

I'd also add that it's important to understand the context in which your team is working.

If I were managing this hypothetical team in a pre-product-market-fit startup I could see the 'slow' person as a potentially greater risk than the others. Not because of speed per se, but because he may be investing too much time in directions that don't help the company learn about their market, and he may be building grand architectural visions that are hard to delete when we realise the product is going in a direction that person didn't anticipate.

On the other hand if I were managing the same hypothetical team in a highly defined context, for example a mature product or an open source library with a large userbase, the 'quick hack' people would need to change their ways.

Obviously this analysis is incredibly shallow and would need a ton of conversation and observation; I'm just making the point that different phases of product market fit require very different approaches & it's worth being aware.



Kent Beck talks about this need for context awareness a lot in his 3x (Explore, Expand, Extract).

https://www.facebook.com/notes/kent-beck/the-product-develop...

https://www.facebook.com/notes/kent-beck/comparing-explore-e...


Beck could have saved time by following tech strategy legend Simon Wardley ;)

http://blog.gardeviance.org/2012/06/pioneers-settlers-and-to...


Also note that Wardley was pushing past PaaS into serverless and per-function billing back in 2005 with Zimki... lightyears ahead of AWS, until it was designated 'non core' by Canon.




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

Search: