This blog was not built to work as a showcase. It exists as a record of a technical path built more on real systems than on ready-made narratives.

I am Yuri Martins. I hold a degree in Mechatronics from IFSP Catanduva, I am currently pursuing a Computer Engineering degree at Univesp, and I have 4 years of professional experience in the field. My career was shaped in environments where software never appears alone: it comes together with operations, communication, telemetry, field devices, integration, physical constraints, and problems that do not respect clean boundaries between layers.

Over these years I have taken on responsibilities across different fronts that nonetheless connect. I have worked on core application teams, participated in internal automation, handled maintenance and evolution of production systems, and approached problems that demand a complete read of what is happening — not just familiarity with a tool. A significant part of that experience came from working on a vehicle tracking and telemetry platform, dealing with continuous IoT data processing, communication with field devices, system behaviour under load, and architectural decisions needed to keep the operation stable.

That kind of context shaped my way of thinking. I have less interest in technology as a surface repertoire and more interest in understanding mechanism, limitation, and real-world behaviour. I like looking at a system as a system: application, database, network, protocol, device, latency, intermittent failure, inconsistent data, observability, operation, and maintenance. In general, the most interesting problems appear precisely at the boundary between layers.

My mechatronics background heavily influenced this way of seeing engineering. I have always leaned towards the point where software meets the physical world: embedded hardware, communication, signal, electrical limitations, poor network connectivity, remote devices, telemetry, and systems that must keep running outside the lab and far from ideal conditions. Today, the Computer Engineering degree extends that path and helps deepen the theoretical foundation for something that was already being built in practice.

I also had exposure to a front I consider important in my trajectory: security and technical investigation. I participated in the TPS — the Public Security Test — as a registered pre-researcher, investigating questions related to the Brazilian electronic voting machine. It was an experience that reinforced my interest in experimental method, careful analysis, critical reading, and rigorous engineering.

At another point, I shared part of this knowledge in a talk at IFSP Catanduva, particularly on topics related to IoT and applied engineering. Teaching and technically organising what one learns in practice is also a way of consolidating knowledge, and this blog relates directly to that.

Today I am deepening my studies in areas that connect directly with the kind of engineering I want to keep developing: microelectronics, computer architecture with a focus on RISC-V, the Linux kernel, DRM/Xe, telecommunications, mobile networks, embedded computing, and systems built with real constraints in mind. I do not see these areas as a loose collection of interests. For me, they are part of the same axis: understanding how computing works from the inside, from the lowest level up to the system operating in the world.

This space exists to organise that journey. Here I write about software, hardware, systems, protocols, security, architecture, and technical investigation from the perspective of someone who prefers to take the problem apart before repeating jargon. Less showcase. More structure. Less pose. More engineering.