I’m starting this blog because I need a place to think out loud.
I work as a software engineer, but I spend a lot of time thinking about how technology shapes our world beyond just lines of code. The name “Debugging Culture” seemed fitting – not because I think culture is broken and needs fixing, but because I’m trying to understand the systems at play.
This isn’t meant to be another tech blog with hot takes on the latest frameworks or tools (though I might talk about those sometimes). It’s more about exploring questions that stick with me:
- How do we encode human moral decisions into autonomous systems? (My Master’s thesis focused on this problem for self-driving cars)
- Why do cooperative systems break down despite being in everyone’s best interest? (Game theory has some fascinating answers)
- At what point does “we built it because we could” become “we really should have asked if we should”?
Along the way, I'll try to break down complex technical concepts without the usual jargon overload. I've always thought that if you can't explain something clearly, you probably don't understand it well enough. So consider this a challenge to myself – taking ideas like distributed systems or algorithm design and finding their intuitive core. Not dumbing them down, just clearing away the unnecessary complexity.
I write code for a living and spend a lot of time listening to podcasts and audiobooks. No special expertise beyond curiosity and some technical background. I’m sharing thoughts here because writing helps me think more clearly, not because I have all the answers.
No schedule, no grand promises. Just thoughts on technology and society when I have something worth saying.
Let’s see where this goes.
