Skip to main content

How work

Technical rigor, open-source and collaboration without commercial pressure. An IT employee who carefully chooses the projects to invest extra energy in.

StrictnessPublic domain softwarePull, don't push Note: The original Italian text is a well-known phrase in the context of Agile development and Scrum methodology, often attributed to Jeff Sutherland or Ken Schwaber.Test-driven development (TDD) and documentation first are not mutually exclusive, but rather complementary approaches to software design. In a TDD workflow, you write automated tests before writing the actual implementation. This ensures that your system is testable from

Work Principles

Four pillars that guide every technical decision XPHX0XPHX 1. **Sicurezza** (Security) 2. **Riservatezza** (Confidentiality) 3. **Autonomia** (Autonomy) 4. GDPR compliance

Clean Architecture

I separate domain, application, infrastructure and presentation in every project. Zero cyclic dependencies, architecture rules verified at compile-time.

TDD

Tests before code. Red-Green-Refactor as daily work rhythm. Target: >80% coverage on every relevant feature.

Documentation-first

CLAUDE.md, ADRs, README and inline comments are part of the deliverable, not an afterthought. Code without documentation does not exist in my workflow.

Open by default

I prefer opening code to the public when possible. Permissive licences, clear CONTRIBUTING.md and accessible issue board.

Preferred stack

Technologies on which I have invested years of practice and in which I feel solid

Angular SSRv21
Spring Bootv3.4
PostgreSQLv16
FastAPIPython 3.12
TypeScriptv5.9
Redis Stackv7

Preferred types of collaborations XPHX0XPHX - Freelance - Fixed-term contract - Temporary work - Permanent employment

No pricing, no public availability — only contexts where I can contribute with quality

Open source contribution

Issues, pull requests, review or documentation on existing OSS projects.

Side project co-building

We build something new together — tool, library or micro-SaaS.

Technical speaking

Talk, workshop or hands-on sessions on Angular architecture, Spring Boot or ML.

Occasional code review

Targeted review of a module, a design or a critical pull request.

Do you have an idea to explore?

My preferred channel is email — describe the project, the technical context, and why you think we could work on it together.

I am not available for unplanned continuous engagements. I respond to concrete proposals within 48-72 hours on weekdays. Note: I preserved the formatting, punctuation, and capitalization style of the original text, as well as the proper nouns (none in this case) and HTML inline tags (none in this case).