Hardware selection strategy and Explainable Architecture design for MVP.

Vendor's code is legacy. WIT driver need to be modern

Code that compiles isn't enough. We tackle runtime reconfiguration, the Zero-Copy trap, and USB hot-plug recovery to build a driver that refuses to die.

Abstraction is beautiful until you plug in the USB cable. How to design a unified driver architecture for fragmented hardware lineups (A1, S3, C1) using Factory Patterns and Finite State Machines.

Why I kept the legacy SDK but rewrote the driver. An analysis of anti-patterns like the 'God Object' and 'Thread Starvation', and a blueprint for a self-healing architecture.

Why I decided to refactor the official RPLidar SDK. A deep dive into issues with vendor-provided robotics software and the plan to modernize it.

Hello World! This is the beginning of my journey to become a specialized Robotics Engineer. I will share my studies on ROS2, C++, and Embedded Systems.