I don't think the analogies of animals in the wild or groups of hunter-gatherer is correct to the modern companies. A better analogy is the teams who built pyramids or armies who empowered Alexander or the medieval peasant settlements who regulated societies.
It's not about acting on your own or achieving something for yourself. It's about building something which is only possible with collective effort of hundreds or thousands of humans. The size of such organization needs hierarchy, management and process.
Think of what processes and management was used for pyramid building. And what would have happened if the workers worked without a boss and process.
I concur the analogy misses this reason for teaming up in large groups completely.
All our current advances are the direct result of working in large, communicating groups, which crucially need a way to transfer knowledge across generations. The YouTube channel “How to make everything” comes to mind, where the resources, processes, machinery… required to make something as mundane as a hairdryer is very tricky for a single individual.
However, I also agree, to some extent, with the point the author is trying to make, even though the arguments and analogies are shaky.
I don’t believe the author is arguing the pyramids would ever have gotten built if everyone did whatever the hell they want. But I also don’t believe the pyramid builders were terribly happy.
In a world where we have solved (or have made significant progress to solving) big categories of problems, it might be worthwhile to consider what our “pyramids” are. Are you working on something life-altering? Some marvel which will stand for hundreds of years? Most people probably aren’t. I know I’m not.
So I find it easy to emphasize with the feeling that it’s more “healthy” to just make whatever the hell you want (be it as a programmer, or just as a human being). After all, a lot of innovation has been a direct result of people fucking around on their own. I’d enjoy a planet where potential Einsteins would not have to work two jobs to survive, in lieu of which they would have time to think, experiment, write, …
Maybe it comes down to:
- Individual freedom is ideal to invent things (someone had to be Alexander)
- Collective pooling of humans is necessary to actually build said things
That collective effort resulted in something very impressive, but there are lots of achievements in the present day which are, organizationally, at least as impressive, and which do not seem to require hierarchy (though they include various hierarchies). The chain of processes and activities that result in a modern supermarket and all its products, for example, has no overarching boss, and some of the steps along the way are handled by self-employed people (truck owner-operators, for example).
> Think of what processes and management was used for pyramid building
For what, a glorified tomb?
I fail to find anything in history that advanced the sciences or the arts through "collective effort of hundreds or thousands of humans". It's only for war or to consolidate power in the hands of the ruling class, never for the benefit of society at large.
If I hear the argument of "naturality" and "natural design" I explode. We are "naturally" meant to die at 21, after getting whatever illness, never to move with massive transport, not even speak. 'cause all we naturally are is monkeys, right? AaaaaRGHHHH This argument makes me nuts
There's a lot more nuance to the "natural" conversation than the assumption that we should go back to stone tools and all die before we hit 25. I've not really seen someone with that general belief, and I'm one of them myself, argue for such an all-or-nothing approach.
I had the exact opposite reaction. Around that time I came across two of his OSCON Talks on the IT Conversations Network and loved them. I must have listened to them hundreds of times and forwarded them to a lot of friends and colleagues.
I'm curious as to why? Regardless of the rest of his output or how you feel about him, this essay seems somewhat interesting (at least to me). There are many examples of where this applies and small teams appear to have an advantage (eg. Posthog).
None of what pg writes here is factually wrong per se, but he is obviously making a bigger deal out of a lot of these things than they really are (that is, he was obviously writing this to convince more people to start and join startups - hopefully at YC).
Some people (most people?) are perfectly happy with just working a stable job within a giant corporation. Either because they are capable of still finding fulfillment from work despite not having so much control (the kind of control that people who start businesses tend to crave), and/or because they find their fulfillment outside of work entirely.
Working for a large corporation feels like being a small fish in a big pond. Your actions make as much of an impact as a tiny leaf rustling in the Amazon forest. I've worked at, both, startups and large mega corporations and I can tell you the difference is night and day.
I'm completely self taught as a software engineer. Since I started I had a passion for writing code every single day. My ideas at first were huge and ambitious but as time passed I noticed they became smaller and more "grounded". But that also correlated with my trajectory in my career. The first few jobs I had were small contracts. Working for myself and hustling against overseas engineers charging 1/100th what I wanted to charge. Then, I went to work for a government agency.
I had big ideas of cool solutions we could build to old problems they were dealing with. I implemented a genetic algorithm that reduced the time it took to estimate how to move water from one location to the next from 15 hours down to 30 seconds. But, we couldn't push the solution to production until several committees could meet and discuss it at length. I left that place after a year and now, 10 years later, they're still struggling with their old technology and slow paced processes.
I then went to work for a startup that wanted to do facial biometrics for fraud prevention. When I arrived they had 7 marketing people, a paying customer, but no actual software developed. Me and a few other engineers wrote the core of the application in a few days and then spent the rest of our time there fleshing it out into a real product. We were working 60 to 80 hours a week, nights, weekends, the whole enchilada. It was exhausting physically and emotionally but it was the best job I ever had. I had complete freedom to design everything from the ground up, got stuff pushed to production seconds after I committed my code, and got to develop some pretty innovative solutions for liveness detection and geo-fencing.
I then roamed around for a few years, salary hopping, from corporation to corporation until I landed at a big company. The work was easy and the pay was good. But year after year my love of software engineering started to die. There were no challenging problems to work on, the solutions were cookie-cutter implementations for every project, and the politics were exhausting. What should have taken 2 weeks of work would stretch to 2 months due to unnecessary meetings, and status updates, and leadership constantly changing their mind. And worst of all, I wasn't learning anything new or growing as an engineer.
Toward the end, every single team became a "modernization" team where all they would work was updating legacy software to "modern" tech stacks. This was obvious busy work because leadership had nothing better to do with the hundreds of engineers they had hired. Eventually, when I had enough money saved up, I decided to retire.
But I always missed working at that startup. The rush, the challenge, the real world solutions we were building that were used by real people and making an impact on their lives was amazing. Now that I'm retired and get to choose what I want to work on I think fondly of those times and wish I could recreate that experience.
Beholding to a boss or to owners. Not a whole lotta difference unless everybody is a sole proprietorship. And that would be way too hand to mouth for most people.
Some people want to try to die rich and unloved by 40. Some people work to be able to afford what they want to do. Different strokes, eh.
I don't think the analogies of animals in the wild or groups of hunter-gatherer is correct to the modern companies. A better analogy is the teams who built pyramids or armies who empowered Alexander or the medieval peasant settlements who regulated societies.
It's not about acting on your own or achieving something for yourself. It's about building something which is only possible with collective effort of hundreds or thousands of humans. The size of such organization needs hierarchy, management and process.
Think of what processes and management was used for pyramid building. And what would have happened if the workers worked without a boss and process.
I concur the analogy misses this reason for teaming up in large groups completely.
All our current advances are the direct result of working in large, communicating groups, which crucially need a way to transfer knowledge across generations. The YouTube channel “How to make everything” comes to mind, where the resources, processes, machinery… required to make something as mundane as a hairdryer is very tricky for a single individual.
However, I also agree, to some extent, with the point the author is trying to make, even though the arguments and analogies are shaky.
I don’t believe the author is arguing the pyramids would ever have gotten built if everyone did whatever the hell they want. But I also don’t believe the pyramid builders were terribly happy.
In a world where we have solved (or have made significant progress to solving) big categories of problems, it might be worthwhile to consider what our “pyramids” are. Are you working on something life-altering? Some marvel which will stand for hundreds of years? Most people probably aren’t. I know I’m not.
So I find it easy to emphasize with the feeling that it’s more “healthy” to just make whatever the hell you want (be it as a programmer, or just as a human being). After all, a lot of innovation has been a direct result of people fucking around on their own. I’d enjoy a planet where potential Einsteins would not have to work two jobs to survive, in lieu of which they would have time to think, experiment, write, …
Maybe it comes down to: - Individual freedom is ideal to invent things (someone had to be Alexander) - Collective pooling of humans is necessary to actually build said things
That collective effort resulted in something very impressive, but there are lots of achievements in the present day which are, organizationally, at least as impressive, and which do not seem to require hierarchy (though they include various hierarchies). The chain of processes and activities that result in a modern supermarket and all its products, for example, has no overarching boss, and some of the steps along the way are handled by self-employed people (truck owner-operators, for example).
> Think of what processes and management was used for pyramid building
For what, a glorified tomb?
I fail to find anything in history that advanced the sciences or the arts through "collective effort of hundreds or thousands of humans". It's only for war or to consolidate power in the hands of the ruling class, never for the benefit of society at large.
> It's only for war or to consolidate power in the hands of the ruling class
Consider Egyptian and Mesopotamian irrigation and flood management, Persian and Roman roads, Chinese canals...
If I hear the argument of "naturality" and "natural design" I explode. We are "naturally" meant to die at 21, after getting whatever illness, never to move with massive transport, not even speak. 'cause all we naturally are is monkeys, right? AaaaaRGHHHH This argument makes me nuts
Or, as Terry Pratchett so eloquently put it in The Fifth Elephant:
> “Not natural, in my view, sah. Not in favor of unnatural things.”
> Vetinari looked perplexed. “You mean, you eat your meat raw and sleep in a tree?”
I think this is fair criticism. It's hard to read this blog cause its premise is based on an "appeal to nature" fallacy.
It's flawed criticism because it's rooted in an all-or-nothing perspective.
There's a lot more nuance to the "natural" conversation than the assumption that we should go back to stone tools and all die before we hit 25. I've not really seen someone with that general belief, and I'm one of them myself, argue for such an all-or-nothing approach.
It's about balance.
> We are "naturally" meant to die at 21
Not really? Historical life expectancies were low because it was so common to die in infancy and childhood (thus dragging down the "average").
For people who made it to 20, it was common to live past 60.
I have been tired of this guy since I first saw him speak in 2006
I had the exact opposite reaction. Around that time I came across two of his OSCON Talks on the IT Conversations Network and loved them. I must have listened to them hundreds of times and forwarded them to a lot of friends and colleagues.
http://web.archive.org/web/20130729210111id_/http://itc.conv...
http://web.archive.org/web/20130729231533id_/http://itc.conv...
I'm curious as to why? Regardless of the rest of his output or how you feel about him, this essay seems somewhat interesting (at least to me). There are many examples of where this applies and small teams appear to have an advantage (eg. Posthog).
We weren't meant to have windows made of glass. Such items are entirely unnatural. According to pg, we must be wary of them.
None of what pg writes here is factually wrong per se, but he is obviously making a bigger deal out of a lot of these things than they really are (that is, he was obviously writing this to convince more people to start and join startups - hopefully at YC).
Some people (most people?) are perfectly happy with just working a stable job within a giant corporation. Either because they are capable of still finding fulfillment from work despite not having so much control (the kind of control that people who start businesses tend to crave), and/or because they find their fulfillment outside of work entirely.
Working for a large corporation feels like being a small fish in a big pond. Your actions make as much of an impact as a tiny leaf rustling in the Amazon forest. I've worked at, both, startups and large mega corporations and I can tell you the difference is night and day.
I'm completely self taught as a software engineer. Since I started I had a passion for writing code every single day. My ideas at first were huge and ambitious but as time passed I noticed they became smaller and more "grounded". But that also correlated with my trajectory in my career. The first few jobs I had were small contracts. Working for myself and hustling against overseas engineers charging 1/100th what I wanted to charge. Then, I went to work for a government agency.
I had big ideas of cool solutions we could build to old problems they were dealing with. I implemented a genetic algorithm that reduced the time it took to estimate how to move water from one location to the next from 15 hours down to 30 seconds. But, we couldn't push the solution to production until several committees could meet and discuss it at length. I left that place after a year and now, 10 years later, they're still struggling with their old technology and slow paced processes.
I then went to work for a startup that wanted to do facial biometrics for fraud prevention. When I arrived they had 7 marketing people, a paying customer, but no actual software developed. Me and a few other engineers wrote the core of the application in a few days and then spent the rest of our time there fleshing it out into a real product. We were working 60 to 80 hours a week, nights, weekends, the whole enchilada. It was exhausting physically and emotionally but it was the best job I ever had. I had complete freedom to design everything from the ground up, got stuff pushed to production seconds after I committed my code, and got to develop some pretty innovative solutions for liveness detection and geo-fencing.
I then roamed around for a few years, salary hopping, from corporation to corporation until I landed at a big company. The work was easy and the pay was good. But year after year my love of software engineering started to die. There were no challenging problems to work on, the solutions were cookie-cutter implementations for every project, and the politics were exhausting. What should have taken 2 weeks of work would stretch to 2 months due to unnecessary meetings, and status updates, and leadership constantly changing their mind. And worst of all, I wasn't learning anything new or growing as an engineer.
Toward the end, every single team became a "modernization" team where all they would work was updating legacy software to "modern" tech stacks. This was obvious busy work because leadership had nothing better to do with the hundreds of engineers they had hired. Eventually, when I had enough money saved up, I decided to retire.
But I always missed working at that startup. The rush, the challenge, the real world solutions we were building that were used by real people and making an impact on their lives was amazing. Now that I'm retired and get to choose what I want to work on I think fondly of those times and wish I could recreate that experience.
Beholding to a boss or to owners. Not a whole lotta difference unless everybody is a sole proprietorship. And that would be way too hand to mouth for most people.
Some people want to try to die rich and unloved by 40. Some people work to be able to afford what they want to do. Different strokes, eh.