What is the goal of engineering?
What's the goal of engineering?
To build and design systems that solve problems!
Every engineer you ask jumps to that definition. And when you ask "But why?" they're stumped.
If you don't have a goal beyond the tech, how do you know you're achieving it? π€
That's what we dug into in this week's Senior Mindset Mastermind group coaching call. How do you know you're on target, aligned with the business, and not wasting time in areas nobody cares about.
See the full video and transcript on SeniorMindset.chat π. Comments welcome :)
We found 3 areas:
1. What is the goal?
My favorite answer to that question comes from a business graphic novel βΒ The Goal
Each business or initiative can define its own goal. That's the Objective and Key Result (OKR) that drives Empowered teams. We talked about those in an earlier session.
You can look at your work and ask "Is this getting us towards the OKR?". If the answer is No, you are wasting time.
2. The core tension of engineering
Daniel mentioned that he feels a tension between building to his high standards of amazingness and the business objective of shipping. We dug into that.
It's the main balance engineers have to strike!
As "real" engineers like to say π "Anyone can build a bridge that stands, but it takes an engineer to build a bridge that barely stands". A bridge that's no more expensive than it needs to be.
Or as I like to say βΒ The Code is not The Goal.
Err on the side of quality when you're building an asset and on the side of speed when it's an experiment. Ask which situation you're in. Lots of pain when you're building an asset and the business is antsy to test their experiment.
3. You do have time to build it twice
If you don't have time to do it right, when will you have time to do it over?
Later. When your business has grown and there's more people, more money, more revenue, more feedback from users.
Your perfect plan won't survive contact with the user. Best to try fast and see what happens. Fix if it's worth fixing.
As Mike Tyson, a legendary boxer, would say βΒ "Everyone has a plan until you punch them in the mouth"
As George Patton, a legendary general, liked to say βΒ "A good plan, violently executed now, is better than a perfect plan next week."
Iterate. Iterate. Iterate.
The first time you're building something there's a 99% chance, you're still figuring out what and how to build. Writers call this "the vomit draft".
Ship. It's the only way to know whether your solution works. You can fix it later.
Cheers,
~Swizec
PS: civil engineers can move entire buildings, don't tell me you can't move a few components around π
PPS: Want to improve your senior level thinking? Consider joining the Senior Mindset Mastermind. You get access to the full archive and we meet every 2 weeks