My turn to write things down

The honest reason this blog exists: I want to be more present in the dev world than my commit history makes me. The first kick came this week at Affiliate World Budapest. Two days surrounded by affiliates, agencies, hard-working people who treat being visible as part of the work, none of them waiting for anything to be perfect before talking about it. I left wanting some of that.

The deeper reason is older. I'm a self-taught developer, which means everything I know traces back to something a stranger bothered to publish. A French coding PDF from Site du Zéro, back in 2013. Grafikart videos. A PHP and MySQL course on a CD I bought as a teenager. People wrote things down, and I built a career out of reading them. More than a decade in, it feels like my turn.

There's a selfish angle too. Writing forces me to finish my thoughts. An opinion I can't put into plain sentences is usually not an opinion, it's a mood. A standing deadline is a forcing function: pick a take, check the facts, publish it somewhere people who know better can tell me I'm wrong.

So here's the deal I'm making with myself:

• Once or twice a month. Short and opinionated, published when it's actually worth reading.
• Concrete. The stack I touch every day, TypeScript, Next.js, NestJS, databases, servers, plus the occasional story about something breaking in production.
• No filler. No release-notes roundups, no takes on tools I haven't actually used.

That's the experiment. Let's see if the version of me a year from now kept the schedule.