notes

i still remember my first day at the Atal Tinkering Lab. i didn't know much about robotics or electronics back then, but i was curious about how things worked. there were components, wires, tools, and machines everywhere, and i wanted to understand all of them.

what excited me most was the thought that i could actually build something instead of just reading about it in a textbook.

i started exploring the equipment and learning about electronics. of course, i didn't understand everything immediately, but that didn't really matter. every new thing i learned made me want to try something else.

looking back, i think that day was the beginning of something important. ATL wasn't just a room full of equipment for me; it was a place where my ideas could finally become experiments.

i didn't know what i would build in the future. i only knew that i wanted to keep making things.

sometimes, a big journey begins with nothing more than curiosity.

lately, i've been thinking about how technology could help teachers understand what's happening in their classrooms. teachers have so many things to focus on at once, and i wondered whether a small system could help with some of that work.

that's how EduSense One started taking shape.

the idea was to combine a Raspberry Pi, a camera, and sensors to explore features such as attendance assistance, classroom sound monitoring, and engagement analysis.

building it hasn't been as easy as i imagined. i've had to troubleshoot the camera, deal with software dependencies, and figure out how the different parts should communicate with one another.

there were moments when something that seemed simple on paper turned into an entire afternoon of debugging.

but i think that's what makes building real things interesting. you don't always get the result you expect, and sometimes you learn more from fixing a problem than you would have from getting everything right the first time.

i want to present EduSense One as a project that explores how robotics and automation could support education.

there's still room to improve it, and i'm excited to see how far i can take the idea.

an idea becomes real when you're willing to work through the difficult parts.

one thing i've always wanted to do is create software that other people can actually use — not just projects that run on my own computer.

that ambition led me to MAILIX.

MAILIX is a developer-focused email platform that helps applications send and manage emails through APIs. i've worked on ideas such as email templates, API keys, domain verification, delivery logs, analytics, and integrations with email providers.

as the project grew, i realised that making the interface look good was only one part of the job. there was also authentication, error handling, project isolation, and the challenge of making everything work together properly.

eventually, MAILIX became a publicly released product. that felt different from finishing an ordinary coding project — because releasing software means thinking about the people who might use it.

i've also been thinking about how to make installation easier, especially for Windows users.

there is always something else to improve, but i'm learning that a project doesn't have to be perfect before you share it. it needs to be useful, thoughtfully built, and open to improvement.

writing code is one thing. putting your work out into the world is another.

i was thinking about colours one day and realised how much information can be hidden behind a simple hexadecimal code.

a colour might look beautiful on a screen, but its code doesn't really tell you a story about it. i started wondering whether i could build a more organised collection where every shade had its own name and identity.

that idea became Huefy.

my plan is to create a library of 10,000 shades divided into nine colour families. each shade would have a unique identifier, a hexadecimal value, and a custom name.

i also want to build a website where people can explore the collection and eventually experiment with colours using interactive tools.

the interesting part is that this project combines two things i enjoy: programming and creativity. i get to think about data structures and file organisation while also exploring names, shades, and the way colours work together.

i know that creating a colour library is only the first step. making it consistent, useful, and easy for other people to explore will take much more work.

still, i like the idea of building something that gives every shade a place of its own.

sometimes, the smallest details are what make a bigger idea memorable.