Backend-first developer with 9+ years shipping PHP & Laravel systems, RESTful APIs and Next.js frontends. I use AI agents across the whole workflow — from specs to code, tests and code reviews.
Led the migration of a legacy B2B platform to Laravel, redesigning the database schema and optimizing heavy operations with job queues and schedulers. I architect backend systems and RESTful APIs across production projects in different industries, and I've woven AI agents into the daily workflow — from code generation to peer reviews and test coverage. I also ship features end-to-end with Docker and CI/CD.
Built back-end systems and APIs across client projects, expanding into AngularJS and a Node.js/MongoDB pipeline for large-scale Excel data imports. I owned the full lifecycle of dozens of websites — from gathering requirements with clients to deployment and maintenance — wearing both the backend and the frontend hat. I also introduced version control and more structured deployment practices inside the web department.
Started as a university intern building sites from PSD files with HTML/CSS/jQuery, later connecting the front-end to a PHP/MySQL back-end. I learned the craft of pixel-perfect markup, progressive enhancement and cross-browser compatibility, and got my first real taste of shipping work that lives on the public web. It's where the habit of caring about the details — from spacing to load times — really started.
Caregiver-client marketplace
Open-source, ATS-optimized CV builder
Japan travel journal
LLMs rarely make syntactic mistakes anymore — when something breaks, it's architectural. Two things changed how I review: asking the agent what could break elsewhere before merging, and keeping a running spec of past decisions it checks against new requests.
read on linkedin →Cloudflare's numbers show agentic traffic growing faster than any other automated category. If a site isn't readable by agents (markdown content, llms.txt, a proper sitemap), it risks being invisible to both agents and the humans using them.
read on linkedin →An agent now reads my Japan travel blog's RSS feed, tracks what's been covered, and drafts new posts in Markdown pushed straight to a GitHub repo. The real bottleneck was never the writing — it was picking the topic and deciding to start.
read on linkedin →A few habits that actually moved the needle: a new chat per phase of work, compacting context before it fills up, cheap models for binary checks, and trimming long logs to just the last 20-30 lines.
read on linkedin →// powered by mistral — answers from andrea's knowledge base