After several minutes, he raised one hand.
"Son."
The boy stopped.
His father smiled.
"I understood the first three words."
They laughed.
Then the older man looked toward the machine.
"You reckon it'll work?"
The boy nodded.
"Eventually."
His father placed one scarred hand against his shoulder.
"Then take your time."
The child returned to the computer.
His father remained beside him.
After a while, the older man said something his son would remember for the rest of his life.
"There's one thing machines can't tell you."
The boy looked up.
"What?"
His father nodded toward the garage.
"Whether the person using them is doing the right thing."
The child frowned.
His father continued.
"A tool can help somebody fix a car. Same tool can help somebody cheat a customer."
The boy considered.
"Depends on the person."
His father smiled.
"Exactly."
Then he stood.
"Now come help me close the shop before your mother thinks I've forgotten what time it is."
The boy laughed.
And followed him downstairs.
Years later, after building his own technology companies and negotiating acquisitions worth hundreds of millions of dollars, the businessman would remember that conversation more clearly than many expensive business lectures.
Technology was not automatically fair because it produced numbers.
Systems were not automatically trustworthy because they displayed information neatly.
And power did not become legitimate simply because someone placed it behind a polished interface.
Every system reflected the decisions of the people who built and operated it.
He learned that first in a garage.
And the lesson eventually brought him to the driveway of a three-million-dollar mansion with handcuffs around his wrists.
His mother shaped him differently.
She was patient.
Precise.
And relentlessly curious.
At the public school where she worked, she watched children become convinced that certain opportunities were not meant for them.
Some had never met a software engineer.
Others had never visited a university.
Many believed that expensive careers required connections their families did not possess.
She refused to accept that.
Every Friday afternoon, she organized a small technology club in the library.
Students used donated computers.
Learned basic programming.
Repaired broken equipment.
And built simple projects from whatever materials were available.
Her son helped.
He carried computers upstairs.
Installed software.
Showed younger students how to solve problems.
And occasionally spent an entire afternoon explaining something that should have taken ten minutes.
His mother teased him about it.
"You're becoming a professor."
He laughed.
"No, I'm not."
She smiled.
"You explain everything like the world is waiting for your lecture."
He shrugged.
"Maybe they need to know."
She touched his cheek.
"Then make sure you're explaining things to help people, not just to show how much you know."
He remembered that too.
When he was seventeen, a local technology company sponsored a student competition.
Teams had to design software that solved a practical community problem.
His group built a simple scheduling system for a food pantry.
The pantry had struggled to coordinate deliveries, volunteers, and families receiving assistance.
The program was not elegant.
Its interface was clumsy.
The database occasionally crashed.
But it worked well enough to reduce wasted trips and scheduling mistakes.
The team won second place.
First place went to a private-school group with a polished presentation and an expensive prototype.
The boy was disappointed.
His mother attended the ceremony.
She watched him fold the certificate into his backpack.
Then asked why he looked upset.
"We lost."
She raised an eyebrow.
"Did you?"
He stared.
"We came second."
"I know."
"First place would've looked better on college applications."
His mother nodded thoughtfully.
"Maybe."
Then she asked, "How many families did your program help?"
He considered.
"About sixty."
She smiled.
"And did it work?"
"Mostly."
"Are they still using it?"
"Yes."
She nodded.
"Then I don't think you lost."
He looked toward her.
For a moment, he did not understand.
Then she continued.
"A trophy tells people somebody judged your work."
She placed one hand against his shoulder.
"But usefulness tells you whether the work mattered."
He carried that distinction into adulthood.
He wanted to build something successful.
But he never forgot that successful and useful were not always the same thing.
He earned scholarships.
Studied computer engineering.
Worked long hours.
Spent summers repairing network equipment.
And eventually joined a small software company developing systems for logistics, industrial security, and supply-chain management.
He was talented.
More importantly, he was willing to solve problems nobody considered glamorous.
When the company's warehouse tracking system failed, he spent three nights identifying the cause.
When a client discovered that an access-control system could be bypassed through a poorly designed administrative process, he rewrote the affected software.
When managers ignored complaints from technicians, he asked the technicians what was happening.
People noticed.
By thirty, he led a software engineering team.
By thirty-three, he had left to start his own company.
The company initially occupied two rented rooms above a printing business.
He employed four people.
An engineer.
A sales specialist.
An accountant.
And a former logistics manager who understood the problems customers actually needed solved.
They worked long hours.
Some months, the founder paid everyone else before paying himself.
He drove a used sedan with a broken air conditioner.
Ate too many meals from paper containers.
And slept in the office more often than he admitted.
The first product failed.
The second sold poorly.
The third almost bankrupted the company.
Then a regional shipping business asked whether the team could build software that monitored equipment access without overwhelming managers with false alarms.
The company built a prototype.
The customer liked it.
Then another customer asked for it.
Then another.
Within three years, the software was being used across dozens of industrial facilities.
The company expanded.
Investors became interested.
And the founder learned that building good technology was only part of building a durable business.
He needed financial discipline.
Legal advice.
Security audits.
Customer support.
And managers willing to tell him when he was wrong.
At thirty-eight, he sold a majority interest in the company to a national technology group while retaining a meaningful stake.
The transaction made him wealthy.
Very wealthy.
But it also left him with a question.
What should he do next?
He could have retired.
Purchased houses.
Collected cars.
Traveled.