Code review, debugging, pair programming and code rescue for developers and agencies. On-demand sessions or a monthly retainer. Zero red tape, maximum efficiency.
From € 60/hour · On-demand or retainer
// In short
Developer support for developers and agencies: code review, debugging, pair programming and rescuing projects in trouble, as single sessions or with a monthly retainer. Sessions start at €60/hour, the retainer at €400/month and a code audit at €350.
Dev Support isn't business consulting. It's a technical service between developers — no red tape, no formal presentations, no explaining the problem to someone who doesn't understand code.
You work alone and run into problems you'd normally ask a colleague about. You don't have colleagues. That's what I'm for — no annual subscriptions or formalities.
You have a project whose technical complexity exceeds in-house skills, or your lead dev is away and you need someone to unblock things. I'm available on demand.
You're learning and want someone to talk things through with, to review your code and explain the why — not just the what. Technical mentoring accelerates growth more than any course.
The bug is there, you can reproduce it, you've checked Stack Overflow ten times and the code looks right. This is exactly when a fresh pair of eyes solves in 20 minutes what stole three days from you. Share the code before the session, we get on a call and isolate it together.
The previous developer vanished. The code is there — no comments, no documentation, an architecture as intuitive as a dark maze. I have experience with code rescue: we analyse the codebase together, map the existing architecture, identify the critical points and decide what's salvageable and what needs rewriting.
You're about to make a technical decision — which database, monolith or microservices, REST or GraphQL, server- or client-side rendering — and want a second opinion from someone with no commercial interest in the answer. I lay out the real trade-offs of each option in your specific context, without dogma.
You're an agency or freelancer with more work than you can handle alone. Instead of turning the client down or doing things badly, you can lean on me for specific modules of a project — frontend, backend, API integration, performance optimisation. White label if you prefer: nobody will know I'm there.
Not a rigid service catalogue — flexible technical availability that adapts to the problem you have right now.
A call with screen sharing — or via a shared repository. A systematic approach: reproduce the bug in isolation, analyse stack traces, test hypotheses, fix and verify. 90% of bugs are solved in 30–60 minutes with another developer watching.
Reviewing code before it goes to production: logical correctness, performance, security, readability, patterns to avoid. With written feedback commented directly in the repository (GitHub/GitLab PR) or a shared document. Unreviewed code before deploy is tomorrow's technical debt.
We work on the code together in real time — you drive, I watch and suggest, or vice versa. Useful for tackling complex features, exploring new patterns or simply not losing the thread on a long refactor. Via screen share or VS Code LiveShare.
Analysis of inherited, abandoned or hard-to-understand codebases. A map of the existing architecture, identification of structural problems, assessment of what's salvageable vs. what to rewrite, and an action plan to get it back into production safely. A speciality for half-dead projects.
Assessment of a proposed or existing architecture: scalability, bottlenecks, single points of failure, accidental complexity. A neutral second opinion before a significant investment — changing it after you've built on top of it is expensive.
Profiling slow applications, identifying the real bottlenecks (not the ones that look like it), query optimisation, lazy loading, code splitting, caching strategy. With before/after benchmarks to measure the real impact of each change.
Analysis of common vulnerabilities: SQL injection, XSS, CSRF, exposure of sensitive data, weak authentication, missing rate limiting. Not a formal penetration test — a practical review aimed at finding the most frequent issues before someone else does.
Regular sessions for junior or self-taught developers: code review with explanations, introduction to patterns and best practices, answers to questions without judgement. Not a course — a technical reference available when you get stuck on something real.
If you're an agency or freelancer with overflow, I can work as an external developer on parts of the project — website, web app, API integration — without appearing to the end client. Total discretion, code delivered as agreed, no interference with your client relationship.
I'm not a jack of all trades — I'm competent in a specific area of web development. If your problem is outside this scope, I'll tell you right away.
Advanced DevOps, Kubernetes, native mobile (iOS/Android), ML/AI, embedded systems. If you need these areas, I'll point you to people who really know them.
Write by email or the contact form: what you're trying to do, where you're stuck, which stack you use. No formal brief needed — just enough to see whether I can help and estimate the time needed. I reply within 24 hours, usually much sooner.
The more context before the session, the less time spent understanding the setup. GitHub/GitLab repository, offending snippets, error messages, expected vs. actual behaviour. With 15 minutes of prep, a 2-hour session is worth double.
Screen share, VS Code LiveShare or whatever tool you prefer. No slides, no theory — real code, real problem. If it's a code review, I leave comments directly in the PR. If it's a bug, I isolate it and explain it as we fix it. If it's architecture, we draw it together.
After each session I send a written summary of what we discussed, the decisions made and the recommended next steps. You can write to me with follow-up questions in the following days — sometimes the real insight comes when you think it over in the shower.
Anonymous names, real problems. The kind of situations that happen to everyone — and get solved much faster with a second pair of eyes.
A freelancer with a Node.js e-commerce ready to launch. Pre-production code review: 8 critical vulnerabilities found (including SQL injection and XSS), 9 medium, 6 suggestions. Launch postponed by 4 days, data breach avoided.
A junior developer with a React app stuck in an infinite re-render loop. Blocked for 4 days. A 90-minute session: found the circular dependency in a useEffect, explained the correct pattern, fix applied and verified. App working and concept understood.
A technical founder convinced he needed microservices for his first SaaS MVP. Two architecture review sessions: showed why microservices were a trap for an MVP and chose a simpler monolithic stack. An estimated 3 months of development saved.
No mandatory annual subscription. You can start with a single session, move to a retainer if it's useful, or request a one-off audit.
On demand, no commitment. 1-hour minimum. Ideal for bug hunting, pair programming or specific questions.
8 hours/month of technical support. The plan chosen by those who need ongoing support.
In-depth review of an entire codebase or module with a detailed written report.
It depends on the problem. Most bugs get solved in the session — and if not completely, we'll come out with a clear plan and the hypotheses narrowed to one or two. If the problem is more complex than expected and needs more time, I'll tell you honestly how many extra hours I estimate — no surprises on the invoice. In the very rare cases where the problem is outside my skills, I tell you right away and suggest who to turn to.
No, share only what's strictly necessary to solve the problem — a file, a function, an isolated module. If you have NDA constraints, we can sign a confidentiality agreement before the session — it's normal practice between professionals. Alternatively, you can anonymise sensitive parts (variable names, real data) before sharing — it usually changes nothing for debugging or review.
Yes — white-label subcontracting is included. If you're an agency or freelancer with overflow, I can develop specific modules or features by agreement. The difference from classic Dev Support is that we don't work in a shared session; I deliver working code on the agreed timeline. For this kind of project we agree a per-project quote or a package of hours, not the single-session hourly rate.
Usually 24–48 hours is enough for standard sessions. For clients with an active monthly retainer, replies are prioritised and sessions can be booked with 12 hours' notice. If you have a real emergency (a production bug blocking everything), write to me directly — I assess immediate availability case by case. I don't promise 24/7 availability, but I try to be flexible when the situation calls for it.
Yes, and it works especially well. Mentoring for junior or self-taught developers is one of the most frequent uses. No minimum skill level is required — only a real problem you're working on. The difference from Stack Overflow or ChatGPT is that you can ask follow-up questions, understand the reasoning behind the solution (not just the solution), and have someone who adapts the explanation to your level and specific context.
For single sessions: payment in advance by bank transfer or Stripe before the call (I've had too many no-shows in the past). For the monthly retainer: a monthly invoice payable within 15 days. For Code Audits: 50% upfront, 50% on delivery of the report. All prices exclude VAT for companies and VAT-registered professionals. You always receive an electronic invoice.
I'm based in Perugia but offer dev support to developers and companies across Umbria: Perugia, Terni, Foligno, Spoleto, Assisi, Gubbio, Città di Castello, Umbertide, Orvieto, Narni, Amelia, Bastia Umbra, Corciano, Marsciano, Deruta, Castiglione del Lago, Norcia and every other town in the region.
90% of the work happens remotely — which means I work with clients all over Italy with no geographical limits. Sessions happen on calls with screen sharing: the code is in front of both of us and location is simply irrelevant.
Site status
No onboarding, no endless contracts. Describe the problem, we set a call, we tackle it.
Your data stays between us. No newsletter, no spam.
I'll reply personally within 24h. In the meantime… I'll start making the coffee.
