Orlando B.
Curious by nature.
Exploring what AI can become.
Using AI to explore ideas—then building what holds up.
Using AI to explore ideas—then building what holds up.
I'm Orlando B. I've been working with technology for a long time, and it still feels new every day. I enjoy understanding how things work, then building something to see if the idea holds.
Right now, I'm exploring AI—not just what it promises, but where it breaks down and what happens when you apply careful engineering to the uncertain parts. I like working through the full cycle: from early experiments to deployed systems, observing what survives contact with reality.
I'm always learning. My English continues to improve. My understanding of AI keeps evolving. This work is ongoing—never a finished state, just the next iteration.
This is an ongoing experiment in how far lightweight infrastructure can go when you accept real constraints. I run small services on a minimal VPS and make conscious trade-offs around performance, reliability, and simplicity. Owning the full loop—setup, deployment, monitoring, and iteration—has taught me what actually holds up when resources are tight.
I build APIs to test ideas in real conditions, not as demos. The work is less about adding endpoints and more about what happens after deployment: logging, iteration, and small decisions that reduce operational surprise. Over time, the systems become clearer and calmer to operate because they're shaped by what I observe in production.
This is a collection of small builds meant to understand where AI works, where it breaks, and how it behaves in real use. Many of the prototypes were intentionally constrained so the failure modes show up early. Not every experiment was finished or kept, but each one left a clearer sense of what to trust and what to verify.
I build small tools to remove friction from everyday workflows. Most of them are personal utilities: simple scripts that make the next step easier and more consistent. The focus is clarity and usefulness, and the learning comes from refining small pieces until they feel stable.
I share technical notes as a way to reflect on what I learn while building. One FastAPI-related post reached a large audience, which reminded me that clear, honest details are often more helpful than big conclusions. I try to write from experience, not from authority.
If you want to reach out about something I've built, or just to talk about AI and systems, feel free to send an email.