Introduction to the Apollo Protocol: What You Need to Know

Apoll0_11Apoll0_11
3 min read

This is the beginning of something I’ve been thinking about for a while. This dev log is where I’ll be documenting my work, thoughts, experiments, and failures as I dig deeper into programming — from building apps to hacking away at lower levels of the system. I named it Apollo Protocol because I like the idea of structure and exploration working together — this isn’t just about making code work; it’s about understanding how and why it works from the ground up.

For context:
I'm Tiago, a developer based in Cabo Verde. You can check out my GitHub at github.com/Apoll011 — that's where most of my projects live. I am passionate about open source because it empowers collaboration and drives innovation. I mostly write in Python, but I also build apps in Swift. Recently, I've been getting into kernel development and lower-level systems programming. It's been intense, but it’s teaching me how computers really work — not just how to use them.

Why I’m Starting This Now

I’ve been working on a few bigger ideas lately — some real, some still floating around in my head — and I needed a space to break them down. Not for likes, not for clout. Just to track the process, reflect on the work, and maybe even help someone else who’s building their own tools.

I believe in learning by doing, failing, and doing it better. That mindset is what drives me to keep pushing through frustrating bugs or late-night refactors that probably don’t matter to anyone else but me. I care about clean architecture, performance, and building things that feel right to use. That includes everything from system utilities to full-blown apps.

One of my favorite quotes is:

"Clean code always looks like it was written by someone who cares."
Robert C. Martin

That’s how I try to write mine 😂😂. Doesn’t mean it’s perfect, but it means I respect the work and the people who might read or use it someday.

What I’m Working On

Here’s a glimpse into some of the projects you’ll probably see show up in this log:

  • Avi – A full-featured voice assistant system I’m building in Rust, with a focus on privacy, modularity, and flexibility. It's inspired by projects like Mycroft, but I'm designing it with my own ecosystem in mind. There’s an internal scripting language called AviScript, a GUI, and even a custom skill editor like a blueprint system. Think Unreal Engine meets assistant dev tools.

  • Together – A suite of apps centered around personal growth and community building. It includes Together We Support, a platform focused on mental health and substance abuse support. I’m building this one using React and Appwrite, with more tools plugged in as I go.

Each of these projects is teaching me something different — from state management in front-end apps to threading models in system-level code. I’m not claiming to be an expert, but I’m not afraid to dig in and learn the hard stuff.

What to Expect Here

I’ll be using Apollo Protocol to:

  • Document what I’m learning

  • Share system designs and architectural breakdowns

  • Post updates on in-progress projects

  • Reflect on decisions — technical and personal

  • Drop notes on tools, languages, and new ideas I’m experimenting with

You won’t find hype here. Just me building stuff and writing about it.

If you’re curious about any of the things I mentioned, feel free to follow me on GitHub or drop a message. I’m always down to learn something new or trade ideas.

I really need to stay motivated to keep going, so or I'm going all in or this will be a great month.

That’s all for Today

Thanks for stopping by and reading the first post. Whether you’re here to follow the tech, the process, or just curious about how things evolve, I appreciate it. There’s a lot more to come.

Until next time — keep building, keep breaking, keep learning.
— Tiago

0
Subscribe to my newsletter

Read articles from Apoll0_11 directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Apoll0_11
Apoll0_11