On March 5, 1975 Steve Wozniak attended the first meeting of the Homebrew Computer Club. A small group of engineers and computer hobbyists started the club to discuss the latest news in the world of computers, especially building personal computers. At the time, computers were giant expensive machines. Unless you were at a university, in the military, or part of a think tank, you would have a hard time getting access to one.
Wozniak was too shy to talk during that first meeting. However, he listened to the group discuss the Altair 8800, the first personal computer that was sold as a kit to hobbyists, and the microprocessors that made this computer possible. That night, after the meeting, Wozniak had an ah-ha moment.
He realized that the type of microprocessor used in the Altair 8800 could be paired with a TV terminal and keyboard that he previously built. By taking these three components he understood that he could design and build a computer that worked as simply as a typewriter or calculator.
In order to use a personal computer at the time you had to use toggle switches, punch cards, and printouts. Wozniak’s vision and design for a personal computer would be the first computer to use a keyboard and TV screen to show user inputs visually. This new computer design changed the way personal computers would be built forever. This computer was called the Apple I.
Steve Wozniak is a builder. He solved a problem by taking his vision for the personal computer and bringing it into the world. What Wozniak intuitively did is a skill that anyone can learn: building.1 2
The Basis of Building
Building is done with a purpose.
We build houses so people have a place to live. Companies build cars and planes to help people move around. People build their bodies to transform how they look. Entrepreneurs build businesses to bring products and services of value to people who want them. We build skills and resumes to move up in careers. Countries build armies in times of war. We build relationships for fulfilling social connections.
Building solves problems.
Look around. Someone built almost everything around you to solve a problem. Your phone, computer, desk, car, and house were all built to solve problems.
Building is creating.
When you build, you bring something into the world that did not exist before. Taking a vision you have for something and bringing it to life is satisfying. You feel a sense of accomplishment and pride when you build.
Steve Jobs once said:
“Life can be much broader once you discover one simple fact: Everything around you that you call life was made up by people that were no smarter than you. And you can change it, you can influence it… Once you learn that, you’ll never be the same again.”
This quote expresses that you have the power to change the world around you. I’d like to put a twist on it:
Everything around you was built by people that were no smarter than you. And you can build things too…
The world needs builders to solve the problems of today and the future.
How to Build
Building is a problem solving process with three steps. It is like a three-legged stool, if one leg is missing the stool won’t function properly. Following this process will ensure you are solving the right problem and that your solution (build) works as needed. You can apply these three steps to anything you need to build.3
- Understand
- Design
- Build
Understanding is the foundation of the building process.
You first need to understand the problem you are trying to solve and why it needs solving. Ask yourself, “What is the purpose?” You don’t want to fall victim to the trap of, ‘If you build it they will come.’
A business that designs and builds products without understanding the problem they are trying to solve won’t be in business long. A student who does not understand a homework assignment likely won’t come up with the right answer.
Einstein is quoted saying:
“If I had an hour to solve a problem I’d spend 55 minutes thinking about the problem and 5 minutes thinking about solutions.”
Do not discount the value of understanding. Understanding takes time, but it is worth it.
Design provides a roadmap and limits rework.
If you try to build a house, but skip design you’ll end up with a mess and a lot of rework.
Poor design does not solve problems; it causes them.
Don Norman, a cognitive scientist, design critic, and author of The Design of Everyday Things said:
“Good design is actually a lot harder to notice than poor design, in part because good designs fit our needs so well that the design is invisible.”
Design is your problem solving approach.
Contractors use blueprints to build houses. Writers use outlines to guide their writing. Animators use sketches to bring characters to life.
Well-thought-out design saves you time and improves the building process.
Building is the execution of good understanding and design.
At this stage it is time to take all the legwork you’ve put in and build.
Building takes many forms. Different builds require different steps and skills. Building a house is different than building a computer. However, you build everything one step at a time.
The World Needs Builders
The world needs people to build things.
Sam Altman, former president of Y Combinator, said, “No matter what you choose, build stuff and be around smart people.”
If you don’t know what you want to build you can help others build things. Most projects are not built in isolation. Architects, contractors, electricians, plumbers, carpenters, and more all contribute their skills and experience when building a house.
Building is a powerful skill. It allows you to create something real where only a vision existed before. When you build you change the world.
Footnotes
- Dolcourt, J. (2016, August 10). Apple’s 40-year legacy began with this ‘Eureka’ moment. Retrieved June 19, 2020, from https://www.cnet.com/news/steve-wozniak-on-homebrew-computer-club/
- A Chat with Computing Pioneer Steve Wozniak. (2006, September 29). Retrieved June 19, 2020, from https://www.npr.org/templates/story/story.php?storyId=6167297
- Thank you to Ralph Lee at Lob for sharing their building process framework that helped inspire this article.