Who I am

Juanjo Payá

I’ve been building software since 2003. I’ve been a CTO and Co-Founder for most of my career, leading technical teams and architecting high-concurrency, performance-critical systems.

Currently I’m Co-Founder & CTO at Zeronet IT, where we work on improving the energy efficiency of IT networks, and where we’ve integrated AI as a core part of both our workflow and the final product.

What I do

ZeroNet helps reduce the energy consumption of IT networks. It’s a real problem: network infrastructures consume far more than they need to, and most don’t even realize it. We combine intelligent monitoring to improve network efficiency. We cover data centers, end devices, shadow AI agent detection, and cyber threat alerting (based especially on energy consumption patterns). More info: zeronetit.com.

I’ve incorporated AI as a central part of my workflow. Not as code autocomplete, but as AI-Augmented Development — AI agents that operate as real collaborators: creating branches, writing code, opening pull requests, and responding to code review.

I’ve decided to share this approach and contribute to the community through this blog, and with open source tools that I keep adding to my GitHub account, some directly related to AI, others simply built with its help. I don’t have grand aspirations — if just one developer benefits from these experiences, I’ll be more than satisfied :-).

Jarvis: my AI collaborator

Jarvis

Jarvis is an AI developer agent with its own GitHub identity. It creates branches, writes code, opens pull requests, manages Jira tickets, and responds to code review — all under human supervision.

Why a separate identity instead of just using my account? Security and real separation of responsibilities. Jarvis has its own credentials on GitHub and Jira, with limited permissions: it can create branches, make commits, and open pull requests, but it cannot commit to master or merge PRs — branch protection rules prevent it. It has no access to my passwords or tokens. If something goes wrong, the damage is contained. It might look like a toy, but it’s an engineering and security decision.

Jarvis is not fine-tuning or a custom model. It’s prompt engineering with structured context: policies, skills, protocols, and tools (MCP servers) that define its behavior. The result is an agent that works like another developer on the team — autonomous inside its branch, but always waiting for peer review before merging.

All my work shows the collaboration (visible in public repositories): Jarvis implements, I design and review. The git log tells the real story.

The result

The productivity impact is enormous. Tasks that used to take hours now take minutes, and those that took days now take hours, while maintaining the same quality and rigor. It’s not about writing code faster, but about having more time for what truly matters: designing well, thinking through the architecture, and reviewing with good judgment.

On top of that, this workflow has broadened my reach across stacks. Programming is programming — good practices, SOLID, separation of concerns, layered architecture… are universal and independent of the chosen programming language. I bring my experience in those principles, and Jarvis masters the syntactic details of each language. The result is that I can work confidently with stacks that would have previously required weeks or months of learning curve.

Contact