Learning Again
After 18 years in embedded I moved into robotics. Choosing to be a learner again gave me a direction: helping solo makers finish real hardware products.
I have spent 18 years developing embedded software. I solved hard problems, connected hardware to software, and made products run reliably. Over time the experience piled up, and problems that once felt hard slowly became familiar.
Then at some point a thought came to me. Am I still growing? Or am I repeating what I already do well, just a little more smoothly each time?
I wanted to keep growing. I wanted to meet new problems, learn things I did not know, and become someone different from who I was yesterday.
There is a word for this: unlearning. It sounds like forgetting what you learned. The way I understand it, unlearning means doubting the frames of thought that experience built in you, and changing them willingly when you need to.
Experience is a real asset. It can also become a limit. It is easy to believe that what worked before will still be right in a new place. Eighteen years is long enough to pile up quite a few beliefs like that.
Satya Nadella at Microsoft said we should be learn-it-alls rather than know-it-alls. The longer my career runs, the more weight those words carry for me. Finding out what I do not know yet may matter more than proving what I already know.
That thinking is also what led me to move into robotics.
Robotics is where AI meets the physical world. AI and operating systems, real-time control, communication, sensors, actuators and the hardware itself. Very different technologies have to mesh and run together inside one system.
It is a field where my experience is useful, and where that experience alone is not enough. There is a lot to learn from scratch, and things I thought I already knew have to be seen from another angle.
That is what I liked about it. Rather than keep doing what was familiar, I wanted to go through learning, once more, something I am not yet good at.
So why do I keep wanting to grow like this?
Looking back over 18 years, some of the work was as hard as developing the product itself. Problems that came up in mass production, failures after shipping, bugs that showed up in the field but would almost never reproduce in the lab, and then the updates and maintenance.
Making a product work and seeing a product through to the end, taking responsibility for it, turned out to be different jobs. Problems I had not thought of during development often surfaced only after the product was out in the world.
These days AI lets one person or a small team build far more complex products than before. Hardware is still hard. You design the circuit, write the software, go through verification and certification, move into production, and then think about running it afterward. Doing one stage well does not get you to the end.
Then this thought came to me.
What if someone else did not have to repeat the trial and error I went through over 18 years? What if a person who started alone could take their own idea all the way to a real hardware product?
As that thought kept going, what I want to do slowly took shape.
Helping people who make things alone finish a hardware product, from start to finish.
But to show someone that path, shouldn’t I be someone who has walked it first?
In Making What I Don’t Fully Understand I wrote that I want to stay the person who puts their name on what they make. Becoming that person comes first. Helping people like me comes after.
So I set one more goal: to finish one robot from start to finish, on my own.
Building the robot is not the final goal in itself. By finishing a hardware system where many technologies are tangled together, I want to find out how far my experience so far will carry me, and where it falls short.
Whether I can then turn what I learn into something other people can use is a question for after that.
Not long ago I wrote that I don’t know my philosophy yet. I still find it hard to say clearly what my philosophy is.
What I can say is that the plain wish to grow, which is all I had at first, seems to have found a direction as I kept asking myself why I wanted to grow at all.
Looking back, moving into robotics was a choice to leave a familiar world and become a learner again.
I am not trying to throw away the experience I built up. I want to learn more on top of it. And I hope I can accept that ideas I have long believed to be right may turn out to be wrong.
There is a long way to go, and I do not know how the vision I have now will change.
One thing is clear, though.
I wanted to learn again, and now I have started.
Comments
Loading comments...