Full-stack dev,backend-first
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.
| PID | CPU% | MEM | Command |
|---|---|---|---|
| 4141 | 34.0 | 0.4% | php artisan queue:work --queue=imports |
| 4278 | 35.1 | 3.5% | claude --review PR#482 --spec orders.md |
| 4415 | 36.2 | 2.6% | pest --parallel --coverage |
| 4552 | 27.8 | 1.7% | next build && next start |
| 4689 | 28.9 | 0.8% | opencode spec:write orders-export |
| 4826 | 20.5 | 3.9% | traefik --providers.docker |
| 4963 | 21.6 | 3.0% | mysqld --innodb-buffer-pool=2G |
| 4201 | 22.7 | 2.1% | hermes-agent --skills ./skills |
| 4338 | 14.3 | 1.2% | astro build idea-scout |
| 4475 | 15.4 | 4.3% | seoflux crawl --site appuntidalgiappone.it |
→ Queue workers powering a legacy B2B platform migration to Laravel.
→ Agent code review against the spec — AI across the whole workflow.
→ Pest test suite, run in parallel.
→ A Next.js frontend on top of a Laravel API.
→ Spec-driven development: the spec comes first, then the code.
→ Docker + Traefik for self-hosted side projects.
→ MySQL / PostgreSQL, schemas designed for heavy operations.
→ HermesAgent: self-hosted agent with custom skills.
→ IdeaScout: AI-scouted product ideas archive, built with Astro.
→ SEOFlux crawling appuntidalgiappone.it.
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.
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.
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.
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.
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.
Hey! I'm Andrea's assistant. Ask me about his skills, experience or projects.It answers using a knowledge base served by this site's API — not a trained model.
Hey! I'm Andrea's assistant. Ask me about his skills, experience or projects.
Conversations are stored to improve the assistant.
available for hire · open to remote & relocation