Practical insights and guides on PHP/Symfony, React/Next.js, legacy modernization, and software architecture, drawn from 18+ years of building web applications for European businesses.
Symfony Flex writes config files, registers bundles, and edits your .env every time you install a package. Here is how recipes work under the hood, what composer recipes:update actually changes, and how to upgrade without losing your customizations.
Read moreWhat EXIST actually pays, how KfW StartGeld works, whether a SaaS counts as deep tech for the EIC Accelerator, and the state aid ledger every founder should keep from day one.
Read moreToken bucket or sliding window log? How the two rate limiting algorithms differ in practice, the Redis Lua scripts that make them atomic, and the Symfony wiring around them.
Read moreMost founders interview their first senior developer with a process copied from companies a hundred times their size. This guide replaces it with one calibrated to a small SaaS team: a paid take-home, an architecture conversation built on trade-offs, a weighted scorecard, and reference checks that get past rehearsed praise.
Read moreAstro ships almost no JavaScript by default, which makes it a strong fit for SaaS marketing sites. Here is where it beats Next.js, where it does not, and what a migration realistically costs.
Read moreParallel routes and interception routes solve dashboard and modal problems that teams usually hack around with client state. Here are the folder structures that make them work, including the default.tsx gotcha behind most 404 complaints.
Read moreSymfony 5.4 is out of security support, but the road to 7.x does not need a feature freeze. How to clear deprecations with production logs, Rector, and small PRs while the team keeps shipping.
Read morePHP 7.4 stopped getting security fixes in 2022, yet plenty of production apps still run it. A step-by-step upgrade path: the compatibility tooling, the breaking changes Rector cannot fix for you, a CI strategy that finds failures before users do, and honest timelines.
Read moreMost SaaS technical roadmaps are irrelevant by month two. This is the planning discipline that keeps one useful: outcome mapping, honest capacity math, T-shirt sizing, risk buffers, and a 45 minute monthly review.
Read moreA pragmatic git workflow for SaaS teams of 3 to 15 engineers: trunk based development with short-lived branches, feature flags, a weekly release cut, and a hotfix process that does not require heroics.
Read more