Hacker News new | past | comments | ask | show | jobs | submit login

The biggest takeaway from The E-Myth for me as a software engineer was the idea of making a job easy enough for the least qualified individual to do it. The example they use is how to train completely untalented 15-year-olds to make burgers at McDonalds. McDonalds doesn't need to hire chefs.

In software engineering, I've seen teams look for years for a candidate with X years of experience in technology Y. In many cases, you don't need an expert, you just need a smart person.

Build up a library of books/articles as well as sample code and exercises. Then hire smart people rather than experienced people. We had a git repo with exercises in functional programming and scala along with unit tests and day one involved checking it out and getting started.

Also, simple code is more accessible to the "least qualified individual". You may sacrifice performance, but you will be able to scale more effectively as an organization.




Really interesting point: Sacrificing short term performance for long term efficiency


Someone once told me that the key to scaling is tolerating inefficiency.

Example: Instead of a front end team and a backend team, have two full stack teams. If they are working on similar parts of the codebase, don't stop them. It's better for both teams to build the same piece of functionality and throw one away than to have one team dependent on the other. Many teams grind to a halt when they say "We could build this in a week, but let's let the other team do it because it will only take them a day or two."


Wouldn't the equivalent of burger flipping be Java development, perhaps in a standardized framework ?


In one sense you are correct. And many companies have found great success in that model.

In another sense, burger flipping doesn't require certifications.




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

Search: