IbuiltmyMoodleexpertiseworkingonrealplatforms—notinaclassroom.
chiSiamo.subheadline
Since 2020, a straight line.
In 2020 I was 17 years old and had a client who needed someone to work on Moodle. There was no course to take first, no certification to earn before starting — there was a problem to solve. That's where it began.
The first things were small — theme modifications, configuration adjustments, some CSS customisation. But every problem solved opened the next one. I started reading Moodle's PHP source code to understand how it worked from the inside, not just how to configure it through the UI.
Over the years I stopped making small modifications and started developing complete plugins, rewriting parts of the core, building internal management tools, integrating AI features. Not for a portfolio — to make the platform work for whoever had trusted me with a real problem.
I have no official Moodle certifications. I have something you can't buy with an exam: 5 years of real production work, real mistakes, real solutions.
Euservice: 6 years of ongoing collaboration.
Active users
Ongoing collaboration
In 2020 I began working with Euservice, a professional training company with an active Moodle platform but needs that were growing faster than the available tools could handle.
That collaboration has never closed. We're still working together.
Over those years I built an internal management system that automated administrative operations which previously required manual intervention on every single request. I modified parts of the Moodle core to adapt the platform to business processes that no standard plugin could have covered. I developed advanced reporting scripts that aggregate complex data and make it readable for those who need to make decisions. I integrated AI features that extend the platform's capabilities beyond what Moodle offers out of the box.
The result: that platform now serves 150,000+ active users.
Five operating principles.
I respond within 24 working hours.
Not because it's a policy — because respecting the time of whoever writes to me is the minimum I can do.
Before opening any code, I understand your process.
Ninety per cent of the Moodle problems that reach me are actually process problems poorly mapped onto a tool. If I don't understand what you do and why, I can't genuinely help you.
I work both remotely and on-site.
I'm based in Latina, Italy, and available for travel when the project calls for it. The working mode doesn't change the quality.
I don't take on projects I can't do well.
If your case isn't a good fit for my skills or my current workload, I'll tell you straight away. A clear no is better than a yes that disappoints.
I don't disappear after go-live.
Delivery isn't the end — it's the beginning of the interesting part. A Moodle platform in production always has room to improve.
Skills.
PHP
The language Moodle is written in. I know it out of necessity, not academic choice.
Moodle Core API
Moodle's internal architecture: events, hooks, modules, blocks, themes. I know where to touch and where not to.
Plugin Development
Activity plugins, blocks, reports, authentication, external system integrations. Native development.
Database
Complex queries, optimisation, advanced reporting. MySQL/MariaDB and PostgreSQL in the Moodle context.
AI Integration
I've integrated AI features into a platform with 150,000 users. Production, not experimentation.
Languages
Italian (native), English (fluent), Spanish (fluent). I work with international clients without intermediaries.
Got a project in mind?
Write to me directly. I respond within 24 working hours.