A software engineer reviewing system architecture, website monitoring, crypto analysis, and meal-management ideas across several screens and wall sketches in a home office.

Completed

Learning to Build Software

A four-part account of how I went from curious hobbyist to shipping engineer — the mentorship, systems, and mistakes that shaped how I build software today.

A desk with programming books, a notebook sketching an idea-build-learn loop, a laptop showing code, and a small robotics kit, with a hand-drawn diagram on the wall showing the path from graphic design to software engineering.

Part 1

Learning to Build

How curiosity led me from graphic design and freelancing to web development, robotics, and my first software engineering job.

3D-rendered illustration of a gray-haired engineer sitting on a desk in thought, in front of a whiteboard system-architecture diagram, with a shipping yard visible through the window

Part 2

I Started as a Senior Engineer by Accident

How I began with a senior title, junior knowledge, and enough responsibility to discover why I needed real mentorship.

3D-rendered illustration of a dark-haired engineer pointing at a whiteboard system-architecture diagram with a cityscape visible through the window

Part 3

Learning to Design Maintainable Software

How better teams, shared frameworks, and difficult systems taught me to design software that could keep changing.

A young software engineer planning several unfinished projects at a desk, surrounded by website monitoring dashboards, crypto charts, a meal-count display, and system architecture sketches.

Part 4

When Good Engineering Stops You From Shipping

How thinking too far ahead helped me at work but kept several personal projects from reaching real users.