4 ms·

Who said I don't see C's in a lesser light? And yes, I used this post as an opportunity to rant about managers in a vertically structured company, but I see no

Who said I don't see C's in a lesser light? And yes, I used this post as an opportunity to rant about managers in a vertically structured company, but I see no reason why the type of manager I prefer could not exist at Zappos. In fact, it seems like it would be more likely to occur, given that they would no longer outrank the creators.

kybernetikos 11y ago
Without me, my keyboard will achieve nothing. Without a manager, a good developer will go on trying to create value. The purpose of the manager is not to squeeze productivity out of a developer as you might blood out of a stone (although some seem to think it is), but to try to make sure that the developers are working on the right stuff for the company. In a healthy organisation, that can be done as part of a dialogue with the developers and takes the form primarily of communication.
- marknutter 11y ago
  > The purpose of the manager is not to squeeze productivity out of a developer as you might blood out of a stone (although some seem to think it is), but to try to make sure that the developers are working on the right stuff for the company In my experience that responsibility has fallen on the CEO or the Product people.
- wushupork 11y ago
  I have to disagree here. Much waste is created by founder developers precisely because they can code, but they are not necessarily creating value ( I'm just as guilty ). Good managers / the business, call it whatever you will figure out the priorities, the desires of the stakeholders, help prioritize and more. Any producer (not just a developer) left to their own devices builds what they want to build, and that's not necessarily valuable to the customers or the business. So I agree with your second part, but not the first.
  - kybernetikos 11y ago
    > Any producer (not just a developer) left to their own devices builds what they want to build, and that's not necessarily valuable to the customers or the business. For a good developer "what they want to build" in the context of their job is at least somewhat informed by what they think will be valuable for their company. Now, it's completely true that developers might be prone to particular kinds of getting it wrong (let's build a framework!), but that's true for any kind of person including managers. Point being, managers are there to help make sure that the producers are informed and aligned about the wider context.

kybernetikos 11y ago

Without me, my keyboard will achieve nothing. Without a manager, a good developer will go on trying to create value. The purpose of the manager is not to squeeze productivity out of a developer as you might blood out of a stone (although some seem to think it is), but to try to make sure that the developers are working on the right stuff for the company. In a healthy organisation, that can be done as part of a dialogue with the developers and takes the form primarily of communication.

marknutter 11y ago
> The purpose of the manager is not to squeeze productivity out of a developer as you might blood out of a stone (although some seem to think it is), but to try to make sure that the developers are working on the right stuff for the company In my experience that responsibility has fallen on the CEO or the Product people.
wushupork 11y ago
I have to disagree here. Much waste is created by founder developers precisely because they can code, but they are not necessarily creating value ( I'm just as guilty ). Good managers / the business, call it whatever you will figure out the priorities, the desires of the stakeholders, help prioritize and more. Any producer (not just a developer) left to their own devices builds what they want to build, and that's not necessarily valuable to the customers or the business. So I agree with your second part, but not the first.
- kybernetikos 11y ago
  > Any producer (not just a developer) left to their own devices builds what they want to build, and that's not necessarily valuable to the customers or the business. For a good developer "what they want to build" in the context of their job is at least somewhat informed by what they think will be valuable for their company. Now, it's completely true that developers might be prone to particular kinds of getting it wrong (let's build a framework!), but that's true for any kind of person including managers. Point being, managers are there to help make sure that the producers are informed and aligned about the wider context.