My name is Ismael, I'm 21 and I'm a full stack developer. I trained in Multiplatform Application Development, a Spanish higher vocational degree. I didn't come through university, and I don't mind saying so.
I started the degree in 2024 and it hooked me from the start. While studying, I worked the olive harvest in winter and later as a kitchen assistant in a bar. Even so, whenever I had a moment, I was coding. In class I ended up helping classmates with their questions, and explaining things to them was how I finally understood a lot of them. At some point I stopped memorising patterns and started understanding why they exist.
Almost everything I know I learned on my own: trying, breaking things and reading documentation until I understood why they failed, with nobody beside me saying whether it was right. It's slower, but what you learn that way stays with you.
What I've done so far
I've done internships at three companies. At Cojali I was in QA, with testing and an internal survey system. At Savia I did frontend with React: an application that handled more than a thousand records with instant search and filters. And at Entreredes I ended up running one of their projects on my own, a SaaS that generated landing pages with Laravel and Filament, which I took to production with Docker and Gemini integrated through queues.
On my own I've built other projects, such as DevConsole, Kairos and PokeCore, which I cover in the projects section.
Where leo/ comes from
leo/ comes from my surname, León. The slash is the one from the terminal prompt: if you've spent time on a command line, you'll recognise it. It's the signature I publish my work under. There's no company behind it, it's me.
How I work
I've worked with quite a few languages and technologies, and that variety is what has taught me the most. But technology isn't what matters. What matters is understanding the problem well, solving it in a way someone else can maintain, and making sure it still works months later. I own what I build, from how it's put together until it's in production, and if something fails, it's mine.
What I know and what I don't
My experience is measured in months, not years, and I'm not going to pretend otherwise. What I do know is that there's a difference between code that works and code that lasts, and between building loose features and building a complete system. That's where I put the effort.
If you want to talk, write to me. I'm also on LinkedIn.