From Business Analyst to CPO
What carried over from ten years of banking and insurance analysis into running engineering at a startup — and the habits I had to unlearn.
Information
Engineering notes, product thinking and career lessons from building software for banks, insurers and startups.
6 articles in this category and its sub-categories.
What carried over from ten years of banking and insurance analysis into running engineering at a startup — and the habits I had to unlearn.
Where a language model genuinely helps a business analyst — drafting acceptance criteria, spotting gaps in workshop notes — and where it quietly makes things worse.
A short template for acceptance criteria that reads like a test, avoids ambiguity and stops the “that is not what we meant” conversation at UAT.
A boring, reliable deploy pipeline for a Laravel site on one VPS: atomic releases, health checks, cached config and a rollback that takes ten seconds.
How this blog models a three-level category tree with an adjacency list, cached depth/path columns and a single scope that returns every post under a branch.
Why Filament replaced a hand-rolled admin in a week: resources, relation managers, media uploads and a tree-aware category select — with the trade-offs I hit along the way.