Week 24· English level: A2 · 3 challenges solved
A senior backend developer documenting the climb toward architect roles — and the English journey from A2 to professional, written entirely in English.
Deep in system design and Domain-Driven Design — solving one challenge a day and writing it all in English.
More on the /now page →I’m a senior backend developer learning English while going deeper into AI. In this post, I share my current English level, my challenges, my goals, and how I plan to measure my progress.
Free text is great for humans but terrible for code. In this post I show how I get reliable JSON from LLMs with schemas and validation, and why I treat prompts like code: versioned, reviewed and tested.
Calling an LLM API is easy. Running it in production is not. These are the backend patterns I use to make AI features reliable, cheap and safe: timeouts, retries, queues, caching and good boundaries.
Your app works on your laptop. But what happens in production at 3 a.m.? Observability helps you answer questions you didn't plan. Here is a simple guide to logs, metrics and traces, with AI features in mind.
A good API is easy to use and hard to use wrong. These are the REST API design rules I follow every day as a backend developer: names, status codes, errors, pagination, versioning and safe retries.
This very site — a Laravel learning journal and portfolio built in public.