3 ms·
I don't think the book applies at all to the hacker news crowd. "The E-Myth Revisited" basically advocates turning every business into McDonald's. That's fine
by gwbas1c 9y ago
I don't think the book applies at all to the hacker news crowd. "The E-Myth Revisited" basically advocates turning every business into McDonald's.
That's fine if someone wants to start some kind of tech consulting business; but that's not the kind of business that I see promoted on Hacker News.
The "The E-Myth Revisited" describes how to plan a business where labor is low-cost and unskilled. With software, (and hardware, to a degree,) when you write a program, the program is done. Most of your labor goes into R&D that is not repeatable according to what "The E-Myth Revisited" advocates.
At least with hardware, the low-cost unskilled labor can go into manufacturing, but that is now mostly outsourced.
At most, "The E-Myth Revisited" can be applied to the sales and support part of running a tech business, which is what Oracle does very well.
- colefichter 9y ago> With software... when you write a program, the program is done. Most of your labor goes into R&D... Not by a long shot! The vast majority of the lifetime cost of software is in the maintenance (daily operations, upgrades, new features, bug fixes, integrations, rewrites, etc).
- apatters 9y agoIf you think of skill as being the ability to operate the business, growth does in fact require you to hire people who are less "skilled" -- specifically technicians who are specialized in one area of the business' operations (preferably even better at it than you are), and who can handle that part of the business for you. Gerber goes into this with his description of how to support business growth by building out a hypothetical org chart even when you're the sole person in the business, and gradually replace your name next to most of the job titles with someone else's. This is pretty much how you'd build out an engineering team of 50 or 500 people, too. And within any kind of org - sales, engineering, support, whatever - eventually you're going to get large enough that you can be more efficient by sequestering simple work into simpler roles, which gets done by cheaper, junior people. All 100% applicable to the audience here which is filled with people who are trying to found and grow companies. Your comment implied that perhaps you think sales and support are low-skill roles, which makes me wonder if you have any experience working in those areas or managing people which perform those functions? I can assure you they take a very high level of a different kind of skill, and you would grow those teams more or less in the same way you grow an engineering team: starting with yourself, defining specific functions and duties, sequestering simpler work into lower skill roles for efficiency, and hiring people to fill those roles one by one. Exactly like Gerber describes.