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.