ITPLEN
← Back to ARCADIA Cafè
Davide Brusadin and Antonio Piana having a coffee
ARCADIA Journal

A coffee with Ricardo Piana

•Davide Brusadin•Ospite: Antonio Ricardo Piana

Welcome to this space, and welcome to our very first guest. Allow me to introduce him. Joining us today is an IT professional, software developer, and consultant specializing in business automation and Artificial Intelligence. Let’s welcome Ricardo Piana.

Hi Davide, thanks for inviting me. Seeing you here again, after so many years and so many galaxies crossed, is a wonderful surprise. Luckily, we no longer have to check whether the fleets have returned.

Can we use informal terms with each other, just like we always do? (I asked him if we could use the informal "you" because Ricardo and I have known each other digitally for many years, ever since I used to play and he was the game master of Wardrome.)

I’d say definitely yes. Starting to address each other formally now would be a worse diplomatic incident than the ones we used to see on Wardrome.

Thank you. Would you like to tell us what Wardrome was and what it meant to manage such a strategic universe back in those days?

I can’t quite put Wardrome in the past tense. It was a game, of course, but also a long chapter of my life. A place with no geography where I met real people, watched friendships form, alliances, grudges, patient diplomacy, and wars declared over a poorly phrased sentence. People joined to build an empire and often stayed for the others. The remarkable thing was this: a universe made of numbers and code managed to have a memory, and that memory was no longer mine alone. It was a persistent strategic browser game, with star systems to explore, economies to govern, fleets to move, treaties to uphold or betray. The complexity was outrageous, and I say that with affection. People used to joke that you needed a PhD just to learn how to play. They weren’t entirely wrong. The rules held hands, or punched each other in the face, and a tiny choice could shift the balance of entire empires weeks later. I wanted a world capable of continuing to live even when I stopped watching it. Fortunately, the players took it upon themselves to prove I wasn't in control. Behind that world lay hundreds of thousands of lines of spaghetti PHP. A sprawling mass that grew over the years through insights, fixes, long nights, and patches that became foundations. Today, a software architect would probably call in civil protection. I lived inside it, and I didn't always know my way around. I spent hours chasing down a bug, days designing a mechanic, years listening to players ask for the world to be fairer—or more unfair when it suited them. I was the game master. That meant being a programmer, referee, economist, judge, and occasionally a provincial deity, without the benefit of omniscience. What stayed with me most is the memory of people seriously debating something I had invented. At a certain point, Wardrome no longer belonged entirely to me. It was theirs too. And that is perhaps the best outcome anyone who builds a game can hope for. I haven't truly left it behind. Recently, I published a three-dimensional version of the classic on wardrome.com, bringing its old strategic mechanics into 3D. And I’m also building a brand-new Wardrome. I started in Unity, then decided to return to the browser, where this story began. It will be three-dimensional, more interactive, closer to the characters and their stories: I want players to feel like they are inside a space opera, like one of those classic sci-fi TV shows where the ship, the crew, and the decisions matter just as much as the battles. Not just commanding a galaxy, but inhabiting it. Maybe I’m still looking for the same thing: a world someone steps into and finds paths I hadn't foreseen. This time without spaghetti PHP.

How did designing a strategic browser game and managing its balance and community influence your approach to software engineering and solving business problems today?

Wardrome taught me to distrust systems that look perfect on paper. As long as a rule remains written down, it’s just a rule. The moment it meets a person, it becomes behavior, and that behavior takes directions no diagram ever predicted. Players found shortcuts, combined mechanics, turned insignificant details into instruments of power. Sometimes it was a flaw to fix. Other times, it was the game showing me something I hadn't seen. That’s where I learned to look at relationships before functions. A minor tweak in trade could spark a war; a change meant to make the system fairer might end up rewarding the exact people who didn't need it. The code executed instructions, but people produced the consequences. And the hardest job was telling a bug apart from an unexpected outcome—letting the world move without abdicating the responsibility of keeping it standing. In businesses, I find that exact same geography. There are official procedures and real procedures—the ones that don't appear in any manual, yet allow the work to get done by the end of the day. There are people working around software because the software failed to understand them, and managers asking for new features when the real problem is a poorly framed question. Before writing code, I try to listen. Who is waiting on whom? Where does information get stuck? What pointless gesture is repeated a hundred times because no one has ever had the time to question it? I don't believe much in micromanagement. I believe in coordination, understandable rules, and tools that give people the space to do their jobs well. Perhaps that is the whole link between a galactic empire and a company: the system works when its parts manage to talk to each other. And fortunately, in an office, it’s much rarer for a change to the price list to trigger the bombardment of a planet.

After the Wardrome experience, your professional path crossed with other complex projects, including Vistagare. What was it about, and what technical and architectural challenges did it put in front of you?

Vistagare was born out of annoyance. Many of my projects start that way: I see something that ought to be simple, discover it has been made nearly impossible to navigate, and feel the urge to take it apart. In this case, it was public procurement tenders. Data that is available, formally open, yet scattered across sources, codes, classifications, and documents that seem to demand a degree in administrative archaeology from the reader. I wanted answers to elementary questions: what is being put out to tender, where, for how much, and with what opportunities for businesses? Why couldn't you see it on a map, search using normal words, understand what’s moving in a given territory? So I started building Vistagare: gathering public information, piecing it back together, connecting the dots, and presenting it in a format that is finally readable. Not just another document repository, but a way to navigate through them. The main difficulty lies before the interface. Real-world data isn't polite: it arrives incomplete, contradicts itself, changes format, hides its meaning inside forty-page PDFs. You have to ingest it, normalize it, classify it, geolocate it, spot duplicates and relationships, figure out what can be stated as fact and what needs verification. Artificial intelligence helps read and interpret, but it cannot become an excuse to give up on reliability. An elegant wrong answer is still a wrong answer. There is a kinship here that amuses me. In Wardrome, I built the world myself and asked players to find their way around. With Vistagare, the world already exists, with all its rules, and I try to make it navigable. In the first case, I invented the complexity. In the second, I try to strip away the complexity that isn't needed. I’m not sure the second job is any easier.

How did that experience contribute to shaping your vision on the value of data and information management for businesses or regional entities?

For a long time, we confused the availability of data with the ability to understand it. Something can be public and remain invisible. All it takes is burying it beneath enough fields, acronyms, formats, and virtual portals. Transparency, when reaching it requires a specialized trade, risks being nothing more than a nicely printed word on a website. This isn't a problem exclusive to public administration. I walk into companies that already own almost all the information they need, yet keep searching for it. It sits in three different ERPs, five Excel spreadsheets, in emails, in messages, and above all in the head of that one person everyone calls when something stalls. The data is there, but it doesn't meet. So people re-type, wait, redo the work. We have learned to digitalize obstacles as well. Vistagare confirmed for me that the right question isn't "what data can we display?", but "what is a person trying to understand?". If a small business owner is looking for opportunities in their local area, they shouldn't have to learn database syntax before being able to find them. They should ask a question, get a clear path to the answer, and be able to trace it back to the source and verify it. Simplicity isn't hiding complexity at all costs; it’s doing the necessary work so the person using the tool doesn't have to carry that burden. Today, AI makes it possible to get closer to this idea even when information is scattered across unstructured documents and texts. But the value doesn't lie in generating more words, more classifications, or more charts. It lies in the moment a piece of data reaches someone and allows them to make a decision. Up until that point, it’s just stored material. Afterward, perhaps, it becomes knowledge. And if we’re lucky, it becomes action too.

And now let’s talk about your latest project, the "little" one that isn't little at all: YOBY.fun. I have to admit that when I saw it, I could immediately sense its scale, from the vastness of the project to the audience it’s aimed at. Can you tell us about it?

YOBY is small only from the perspective of someone looking down from above. There are ponds, burrows, little animals, markets, a sky to reach. It looks like a gentle world. Underneath, however, lies a very serious question: why do we reach adulthood knowing so many things, yet knowing so little about money, trade-offs, and the everyday choices money forces us to make? Financial education is often treated as an extra subject, a lesson to be delivered whenever a spare hour turns up. I wanted it to be an experience. Not a course with a few frogs slapped onto it, because kids immediately spot a disguised lesson. A real game, where spending everything has an effect, waiting creates a possibility, choosing one path means leaving another behind. Saving can be lived before it is ever defined. That way, the word arrives later, when it already carries meaning. The world unfolds across the surface of the ponds, underground, and in the sky; it brings together characters, activities, quizzes, markets, and small goals. It is designed primarily for children aged eight to thirteen, but surrounding them are families and teachers. Schools can create classes, assign activities, and guide the journey; parents can follow along and carry those conversations outside the screen. Because the real proving ground isn't just the game itself. It’s the moment a child, faced with a real-life choice, recognizes something they have already experienced. YOBY launches in seven languages. Not to tack little flags onto a website, but because those questions cross borders, even as economic habits and cultures differ. Building a common language without erasing those differences is part of the challenge. Every now and then, I realize I’m still making Wardrome: a universe of rules, consequences, choices. Only this time, I don't want it to take a PhD to get started. And above all, I don't want to teach a child how to get rich. I want to help them understand that choosing is a skill—and that learning it early can change a great many things.

Behind a project with such broad scope and target audience, there is always a non-trivial technological infrastructure. What were the toughest challenges in designing and scaling a platform like this?

The biggest challenge is making sure the difficulty doesn't show. A child needs to log into YOBY and start playing. They shouldn't know anything about architectures, synchronizations, permissions, or databases. Behind the scenes, however, their journey coexists with their family's, a classroom, a teacher, educational activities, content, quizzes, subscriptions, and seven languages. To the child, it has to be a pond. To the person building it, it’s a city. The delicate part is holding two worlds together without doing violence to either one. The teacher needs tools to guide and observe; the family needs to understand and participate; the child needs to feel free to play. If I turn the pond into an electronic gradebook, I fail, even if every single feature works to perfection. And because we are dealing with minors, security, privacy, and role separation aren't regulatory decorations: they have to sit in the foundations. Seven languages add another layer. Translating isn't replacing words. The rhythm of sentences changes, cultural references shift, UI spacing changes, and sometimes the very meaning of an example transforms. That’s why the international dimension can't arrive at the last minute with an extra button. Artificial intelligence also has to be used with restraint. It can help prepare content, adapt activities, interpret requests. But I wouldn't automatically hand every character over to a language model just because it’s possible today. An educational product for children needs clear boundaries, consistent behavior, and recognizable accountability. Knowing when not to use AI is becoming almost as important as knowing how to use it. As for scalability, there’s the scalability of servers, simultaneous requests, and states to preserve; and then there’s a less flashy kind—the scalability of complexity. How do you add a character without breaking three mini-games? How do you introduce a mechanic without rewriting half the world? After the hundreds of thousands of lines of spaghetti PHP in Wardrome, those questions are particularly dear to me. I’ve already paid my dues there, thank you. I wouldn't describe YOBY's scalability as a victory in front of millions of users who aren't there yet. The platform needs to grow, meet real schools and families, and be refined by what we discover as people use it. For now, my goal is very concrete: behind a frog capable of teaching a child something, there should be all the necessary technology—and neither of them should ever have to notice it.

If you had to give one piece of advice to a business or professional looking to start digitizing and automating their workflows today without getting lost in the sea of new technologies, where would you suggest they start?

I’d say start with whatever annoys you. Not with software, and not even with artificial intelligence, which lately is being pitched as a universal answer before anyone has even formulated the question. I’d ask the business owner to walk me through a normal day. Where does work stall, who is waiting for a piece of information, which data gets copied twice, which procedure survives solely because no one has found the time to challenge it? Digital revolutions often begin with a minor irritation repeated every morning. For years, consulting meant making a binary choice: do we buy an off-the-shelf product and adapt the company to its rules, or do we build something custom and budget for months of work? For many businesses, the second option was out of reach. So massive software moved in, packed with unused features, and everyone patiently learned to take the long way around. Today, that gap has narrowed considerably. Modern tools, and AI applied to development, allow us to go from analyzing a problem to a working product at a speed that would have seemed unlikely just a few years ago. That doesn't mean engineering, security, and maintenance have become optional. It means that, more and more often, the consulting is the product: I talk to people, understand a workflow, build the needed tool, and refine it alongside the people using it. I don't sell complexity hoping it will eventually prove useful. The value of the craft changes too. If writing code takes less time, knowing what deserves to be written becomes even more vital. As does recognizing when a request masks a different underlying issue. Automating a broken process doesn't improve it: it just makes it broken with impeccable punctuality. So I would start with a small, measurable case—perhaps nothing spectacular. Solve it, observe the result, and only then move on to the next. You don't always need a five-year plan, a hundred slides, and three committees just to schedule meetings. Sometimes you need twenty minutes with the person who holds everyone else’s work together every single day. If someone asks me where to start, my question is this: "What is the one thing you can't stand doing anymore?" Often, that’s already a functional specification, finally spoken in human language.

Looking ahead to the coming years: what is the next technological frontier or creative challenge that excites you the most, both personally and professionally?

I started programming back when kilobytes were counted one by one. Every idea came accompanied by a negotiation with memory, with the processor, with available time. I spent decades asking myself not only what I wanted to build, but whether the machine would let me build it. Nowadays, the opposite happens more and more often: the machine can help me make it, and I’m the one who has to decide whether the idea is worth pursuing. For someone who has always had too many ideas, that isn't necessarily good news. I believe the truly interesting future of artificial intelligence will begin when we stop mentioning it in every sentence. Right now, we paste it onto products, slap it onto storefronts, constantly demand that it prove its existence. One day, it will simply be an ordinary part of software, like a database or a network connection. The question will return to being the right one: is this tool useful? Does it do its job well? Does it respect the person using it? I am especially interested in the evolution of interfaces. For years, we taught people to speak the language of machines: fields to fill out, menus, rigid workflows. Now we are beginning to build systems that can understand intent and context, without always demanding that someone translate their problem into the format expected by the programmer. Buttons won't disappear, and perhaps that’s for the best. But we will be able to strip away a lot of unnecessary friction from our relationship with technology. There is one line I wouldn't want to cross: delegating a task does not mean delegating responsibility. A system capable of doing a lot must also allow us to understand what it is doing, correct it, stop it, question its choices. I don't dream of machines that decide everything for us. I prefer machines that help us make better decisions. It’s less flashy, but it strikes me as far more civilized. On a personal level, I’m rediscovering a freedom I knew as a boy. I can move from a game to an educational platform, from an information system to a business tool, and test ideas that once would have sat untouched in a notebook for years. It isn't that the work has vanished. It has shifted. The mechanical toil of writing every single piece matters less and less, while the ability to see the whole system—knowing what to ask for, what to verify, what to leave unfinished—matters more and more. I spent my life learning how to talk to computers. Now computers are starting to talk to us. It feels like a good moment to remember that I didn't program for the sake of filling files with code: I programmed because I wanted to see an idea turn into something another person could use, inhabit, maybe transform. I don't know what the next decisive technology will be. I know I will keep sitting in front of a screen asking myself, "what if we tried it this way?" The difference is that today, the screen occasionally already has an opinion. Not always a good one.

Contacts

LinkedIn: https://www.linkedin.com/in/rpiana/

Personal website: https://ricardopiana.com/

Wardrome: https://wardrome.com/

Vistagare: https://vistagare.it/

YOBY: https://yoby.fun/