I’m Tamim Ahmed, a 16-year-old student from the UK, although most people online know me as Ahmedallion (pronounced Ah-med-Al-ee-uhn).
While I’ve completed GCSE Computer Science and am preparing to move into college, most of my understanding of programming has come from self-teaching. I didn’t follow a strict or structured path. Instead, I learned by building projects, breaking them, and figuring out how to improve them over time.
Discovering Programming
My first steps into building anything online actually came before I understood programming at all.
At the time, I was experimenting with simple website builders like Google Sites. I would put together basic pages, adjust layouts, and try to create small projects just to understand how websites were structured. I didn’t think of it as “learning development” back then; it was just curiosity about how things on the internet were made.
Around the same time, I became interested in Discord bots. They were everywhere in the communities I joined, handling moderation, games, and utilities. Eventually, I stopped just using them and started trying to build my own.
Those early projects were very simple. Basic bots, simple commands, and small utilities that didn’t do anything particularly advanced. I also continued experimenting with websites in parallel, slowly moving from drag-and-drop builders into more structured development.
Most of those early attempts weren’t successful in the long term. Many were abandoned or completely rewritten. At the time, that felt like starting over again and again, but in reality, each version taught me something new. I learned how to debug problems, how to structure logic, and how to think more clearly about how software should behave.
Over time, I started noticing a shift in how I approached things. Instead of just trying to make something work, I started thinking about why it should exist and who would actually use it.
That change in mindset made a big difference.
Moving From Builders to Real Development
At some point, I moved beyond website builders and started building websites properly.
Instead of relying on tools like Google Sites, I began learning how websites actually work underneath. That transition made development feel more real. I wasn’t just arranging elements anymore; I was creating them.
The website you’re reading this on is part of that progression. It represents the point where I started building full projects myself rather than relying on simplified tools.
Alongside websites, I also started writing small scripts to make my own workflow easier. These weren’t large or complex systems, but they helped me understand something important: software is most powerful when it solves real problems, even small ones. Automating repetitive tasks or simplifying something I did often made development feel immediately useful.
That’s when programming started to feel less like a hobby and more like a tool I could actually use.
Becoming “Ahmedallion”
Around 2022, while experimenting with domains and online identities, I created the name “Ahmedallion.”
The name comes from combining my surname, Ahmed, with the word medallion. It wasn’t created with a deep meaning behind it. I simply wanted something unique that I could use consistently across different platforms.
At first, it was just a username I tested across a few projects. I registered domains, tried different branding ideas, and used them occasionally while exploring what I wanted my online presence to look like.
Over time, it slowly became my main identity. As I moved away from older usernames, I wanted something stable that I could use across everything I built. Eventually, I settled on ahmedallion.dev as the central hub for my work.
Today, it represents more than just a name. It represents the projects I’ve built, the things I’ve learned, and the direction I’m heading in as a developer.
Building Questo
One of the most important projects I’ve worked on is Questo.
The idea came from something I kept noticing in Discord communities. Most servers rely on multiple bots at once, each handling a specific function. One for moderation, one for games, one for utilities, and so on.
While this setup works, it often feels fragmented. Users have to interact with different bots for different things, and administrators have to manage multiple systems at once.
Questo was created to simplify that.
It is a Discord bot that brings multiple interactive games together in one place. Instead of switching between bots, users can play games like Guess the Number, Truth or Dare, Would You Rather, Never Have I Ever, and others through a single system.
What makes Questo meaningful to me is not just what it does, but why it exists. It wasn’t built as a portfolio project or something artificial to showcase skills. It came directly from a real frustration I experienced while being part of and managing Discord communities.
That idea, building things that solve real problems, is something that continues to influence how I approach development today.
How I Learn and Build
My approach to learning programming has always been practical.
I don’t usually follow structured courses from start to finish. Instead, I start with an idea and learn whatever I need along the way to make it work. Python is still my main language, but I also use different technologies depending on the project.
Most of my learning comes from actually building things rather than studying theory in isolation. That means I spend a lot of time debugging, experimenting, and improving projects as I go.
Right now, a lot of my focus is on building websites and writing scripts that improve my workflow. These scripts are usually small tools that automate repetitive tasks or make certain parts of development faster and easier. They’re not always complex, but they are practical, and that’s what makes them valuable to me.
Community Experience
Alongside development, I’ve also managed Discord communities ranging from around 100 to 350 members.
Although I’m not focused on community management anymore, that experience gave me a better understanding of how people behave in online systems. I learned what keeps users engaged, what causes frustration, and how design decisions can impact the way people interact with software.
Those lessons still influence how I build today, especially when working on user-facing projects like Questo or web-based tools.
Interests and Direction
Outside of development, I’m interested in cybersecurity and ethical hacking. What draws me to that area is the same curiosity that first got me into programming: understanding how systems work at a deeper level, how they can be tested, and how they can be improved or secured.
Looking forward, I’m aiming toward a future in either software engineering or cybersecurity. Both paths align with how I already approach development: building systems, understanding how they work, and improving them through iteration and real experience.
Closing Thoughts
My journey so far has been shaped by curiosity and continuous experimentation.
From early experiments with website builders to Discord bots to building full websites and tools, every stage has contributed to how I understand software development today.
I’m still early in my journey, but I continue to learn by building real projects, improving my skills, and exploring new ideas one step at a time.