Well, I mean I don't want to judge all startups.
In fact if you take any of this offhand advice as gospel, well I wouldn't.
Maybe I should have scattered "probably" and "often" about the place.
1:
------------------------------------------------------------
When you read the book, ole Fred is not a fan of large engineering units. Forget two pizzas (Bezos is from New York, two pizzas for him is ~10 people).
Fred's view is actually:
1x captain/tech lead,
1x co-pilot,
1x ops guy equivalent,
1x business analyst equivalent who can be sent to meetings (he worked for IBM).
(And then two secretaries. And an copy editor for the documentation, because no internet.
No internet! The documentation must be written!
The lead developer needs to follow my favorite advice of all time:
Can't write? Imitate Hemingway.
And a full-time librarian for the punch cards. And a full-time employee just to maintain the minicomputer that was your debugger.
Because hey, the book was written in 1975.
The internet doesn't exist, email doesn't exist, the engineers almost certainly can't touch type. And anyone without an attractive female secretary was nobody.
The pimply faced youth's job as config wunderkid and unofficial court jester fills most of those roles these days)
2:
------------------------------------------------------------
If you think of all the amazing software that has been made by one person...
How many people do you need to make amazing software?
What are you even making?