Introducing Weekly Commit

A few weeks ago, I caught myself googling something I had clearly solved before. Same error, same fix, zero memory of it. That small moment of déjà vu made something click: I was learning a lot, but retaining surprisingly little.

So I'm starting something to fix that — and I'm calling it Weekly Commit.

What is Weekly Commit?

A weekly post about something I learned, broke, fixed, or finally understood. It can be:

• A technical insight from my work as a developer
• A debugging story with a lesson at the end
• A concept I struggled with until something clicked
• Or simply a tool, pattern, or idea worth sharing

Think of it as a git commit -m "learned something".

Why am I doing this?

Honestly? Mostly for myself. Writing forces understanding in a way that reading does not. But if any of these posts help someone else avoid a rabbit hole I fell into, that would be a great bonus.

What to expect

• One post per week, short and focused
• A mix of technical deep-dives and lessons learned the hard way
• Mostly around Cloud, Distributed Systems, AI and Software Engineering — but right now focused more on the Microsoft .NET stack, which is what I'm using professionally
• Occasionally, broader reflections on being a developer / engineering student

Commit #001 drops next week.

See you next week.