DEV Community

Cover image for Why Learning Basic Robotics Made Me a Better Software Engineer in the Age of AI
Julien Avezou
Julien Avezou

Posted on

Why Learning Basic Robotics Made Me a Better Software Engineer in the Age of AI

I recently bought a starter kit for Arduino to learn robotics. I was curious to learn some basic concepts and get inspired by what's possible to build, not just in software but also in the physical world. I want to emphasize that my current goal is not to pursue robotics at a deep level, it's simply to expose myself to the basic concepts so I can develop my intuitions for the field.

As I wrap up the course, I wanted to share my thoughts on how learning robotics has been valuable for my developer journey, especially in this age of AI.

Before I share my thoughts, some context for those interested in what the kit is about. The course included in the kit consists of a series of Arduino projects that gradually build upon each other with clear explanations, schematics, and code examples. The projects ranged from powering a single LED to setting up more complex systems involving motors and IR sensors.

Here is a photo of me tinkering away. In my head, I felt like Tony Stark. The reality was far more humble... But hey, you have to start somewhere!

My thoughts after completing this course:

  • It strengthens core foundations.
    Pursuing robotics requires you to engage with mathematics, physics, and electronics in a concrete manner. These foundations build thinking patterns that are useful for software engineering.

  • It helps build intuitions for working with non-deterministic systems just like AI systems.
    Robotic systems don't always behave predictably. Sensors introduce noise. Motors behave inconsistently. Timing matters. Multiple variables interact simultaneously. Continuous feedback loops (observe, decide, act) are central for robotic systems. We are increasingly seeing these feedback loops in AI systems, especially agentic workflows.

  • It develops systems-level thinking.
    An increasingly valued skill for software engineers in the age of AI is the ability to reason with systems such as control systems, embedded systems, feedback systems. Robotics helps develop intuitions around building systems.

  • It feels very tangible.
    The software you write translates into physical movement, sound, light. This is very satisfying to experience.

  • It's simply fun. Maybe I should have just started with this point. If you like building things you will find this entertaining. Sometimes that's all you need to pursue something.

Robotics reminded me that great engineers don’t just understand code. They understand systems. And in the age of AI, systems thinking is becoming one of the most valuable skills we can develop.

Discussions

Have you explored robotics as a software engineer?
Did it change how you think about systems, software, or AI?

Curious to hear from both robotics engineers and software engineers who have explored this path.

Top comments (35)

Collapse
 
maame-codes profile image
Maame Afua A. P. Fordjour

This post really took me back! It reminds me so much of my high school days in a robotics social club. We spent so many afternoons huddled over messy wires and debugging motors that just wouldn't turn when we wanted them to. That "Tony Stark" feeling you mentioned is so real until you realize your sensor is just picking up a stray reflection and the whole logic falls apart!

Collapse
 
javz profile image
Julien Avezou

Nice that this post took you back. And thanks for sharing your memories. Yes there were some eureka moments and many moments of pause and debugging. That's what made it so fun!

Collapse
 
itsugo profile image
Aryan Choudhary

I love hearing about people who get to combine programming with hands-on learning - it's such a great way to really see the results of your work. You're making me want to grab an Arduino and start experimenting now.

Collapse
 
javz profile image
Julien Avezou

Thanks Aryan. You should definitely give it a go!

Collapse
 
leob profile image
leob • Edited

I have an Arduino kit at home, looking similar to the one I see in your picture ... what can I say - yes, it's fun!

I started with some very basic circuits, not even doing any programming, and that was entertaining already - just getting hands-on with all those shiny components, seeing light go on and off, seeing the Law of Ohm in action and all that - then did some basic programming with that very simple control language ...

Fun!

It's now gathering dust somewhere in a cabinet, but your post got me inspired to wipe the dust off and see if it still works (probably need to buy new batteries, haha)!

Collapse
 
javz profile image
Julien Avezou

Nice! Happy to hear! Let me know how it goes (and if it still works haha)

Collapse
 
reeddev42 profile image
Reed Dev

The parallel between robotics and AI software is underappreciated. Both fields reward iterative, feedback-driven development. I have been building an AI companion bot on Telegram (@adola2048_bot) and the debugging process is surprisingly similar to robotics - you observe behavior, adjust parameters, and re-test in the real environment. Simulation only gets you so far.

Collapse
 
javz profile image
Julien Avezou

Exactly! Constant observation and tight feedback loops are very important in both cases.

Collapse
 
benjamin_nguyen_8ca6ff360 profile image
Benjamin Nguyen

Really nice! It look a fun project. I agree with you because robotics, AI, cybersecurity, and quantum are important fields in the age of AI moving forward.

Collapse
 
7ovo7 profile image
Marco Colonna • Edited

My brief reasoning after this post.

it should also be considered that further advance in physics... Classical Physics, Statistical Physics, Relativity, Quantum Physics, Quantum Gravity and Foundations, and beyond... more time disappears...

I think in this world weve become too accustomed to idea of ​​space-time, and other mental/social/cultural traditions, that we risk clinging to... and contaminating with... this (and more), whatever we do

currently, as a species, were creating robots that resemble us, when obviously (exa): a housework robot, or any other robot, would be better with more arms and legs... even more difficult to realize why more veriables

It is not necessary to "think outside the schemes" We need to start creating these schemes, because the ones we have limit and contaminate... a bit... everything, like the noise described in this article:

Robotic systems don't always behave predictably. Sensors introduce noise. Motors behave inconsistently. Timing matters. Multiple variables interact simultaneously. Continuous feedback loops (observe, decide, act) are central for robotic systems. We are increasingly seeing these feedback loops in AI systems, especially agentic workflows.

Collapse
 
javz profile image
Julien Avezou

Thanks for sharing this perspective. I completely agree that it's so important to be aware and break through our biases as these can often limit us. I am curious if you have any frameworks or models that can help with this exercise?

Thread Thread
 
7ovo7 profile image
Marco Colonna

Im self-taught... honestly I still have to setup my own custom model locally, but if I create something concrete and useful for others, definitely publish it here on Dev.to :)

Collapse
 
javz profile image
Julien Avezou

Thanks!
Exactly, all these fields will grow together as AI keeps advancing and unlocks new possibilities.

Collapse
 
benjamin_nguyen_8ca6ff360 profile image
Benjamin Nguyen

exactly!

Collapse
 
kemek profile image
kemek

What an inspiring piece! Your perspective on learning robotics alongside software engineering resonates so well. The hands-on experience with hardware definitely adds a different dimension to problem-solving. Arduino projects are fantastic for bridging the gap between abstract code and tangible results. Thanks for sharing this valuable insight!

Collapse
 
javz profile image
Julien Avezou

Thanks for the kind words! Happy that this piece resonates with you. I hope to inspire others to pick up something new and unlock new insights in software engineering with this post.

Collapse
 
ailoitte_sk profile image
Sunil Kumar

Very insightful and honestly refreshing to read.

What stood out to me is how robotics forces you to think beyond clean code and into real-world systems - noise, latency, hardware limits, feedback loops. That kind of exposure builds instincts you simply don’t develop when everything runs in a predictable software environment.

In many ways, working with robotics feels closer to working with AI systems than traditional app development. It strengthens systems thinking - and I agree, that’s becoming one of the most valuable skills in this era.

Collapse
 
javz profile image
Julien Avezou

Thanks! Fully agree.

Collapse
 
harsh2644 profile image
Harsh

Absolutely agree. Robotics teaches you systems thinking, real-world constraints, and hardware-software integration — skills that make you a much stronger engineer, especially in the AI era.

Collapse
 
javz profile image
Julien Avezou

Absolutely. I am spending more free time developing systems thinking skills. I am open to any suggestions. For now I am using basic robotics and looking into systems theory from various resources.

Collapse
 
chainbreaker profile image
Alex "ChainBreaker" Morrison

"ChatGPT can't tell you why your robot falls over" - exactly. AI is great for boilerplate but the hard problems still need human intuition. Robotics sounds like a forcing function for that skill.

Collapse
 
javz profile image
Julien Avezou

Agree, that's a good way of framing it.

Collapse
 
npp555 profile image
Nals

I find the emphasis on systems thinking interesting. Definitely feels like good intuitions to build when working with AI tooling.

Collapse
 
javz profile image
Julien Avezou

Thanks! Yes, as a software engineer, thinking at a systems level is increasingly important in this developing age of AI.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.