About
I work on full-stack software, blockchain systems, and the practical challenges of delivering enterprise projects.
I’m Francesco, a full-stack developer and IT consultant at Blockchain Reply. Over the past six years, I have helped deliver enterprise software, much of it blockchain-based, for clients in finance, energy, insurance, supply chain, and payments. Depending on the project phase, my role may include hands-on development, technical analysis, solution design, client workshops, team coordination, or architecture support.
Day to day, that can mean a Spring Boot backend, a Vue or React frontend, smart contracts in Solidity or PyTeal, or the Kubernetes and Terraform setup underneath them — I’m comfortable owning a feature from the database to the contract to the deploy. The full list of platforms and tools is further down the page.
I’m particularly interested in the operational side of software: keeping systems maintainable while accounting for compliance requirements, production constraints, and the needs of different teams. In consulting, the code is rarely the hard part — making it survive handovers, audits, and shifting requirements is.
Before joining Reply, I completed a master’s thesis on Ethereum state channels and built a mix of freelance blockchain and mobile projects. More recently, I have been experimenting with LLMs, coding agents, and developer tooling.
Experience
6+ years delivering enterprise software in regulated and technically complex environments.
Scope
Backend, frontend, smart contracts, DevOps, and the coordination between teams and clients.
Approach
Practical systems, clear interfaces, and delivery processes that stay maintainable under pressure.
Selected technologies
This is not an exhaustive list, but it covers the platforms and tools I have used most often in recent years.
Languages
Backend
Frontend & Mobile
Blockchain
Infrastructure
Data
LLMs, coding agents, and automation
I’m interested in LLMs as tools inside the delivery process: how tasks are framed, how review is handled, and how to make the output usable by a real team.
I have explored that through small projects and experiments: an app that turned article collections into AI-generated podcast episodes, this website redesign done with coding agents, and small tooling such as opencode-lombok. That has pushed me toward coding agents, spec-driven work, and reusable automations: prompts, scripts, and project-specific setup that save time without hiding ownership or lowering the review bar.
Coding agents
Good for repo navigation, quick implementation spikes, repetitive edits, and documentation passes when review stays clear.
Spec-driven work
Turning requirements, constraints, and acceptance criteria into something precise before implementation starts.
Skills & automations
Building reusable prompts, scripts, and project setup so useful patterns do not have to be rebuilt every time.