Welcome to Kaleb Notes

Hi, I’m Kaleb.

This blog is where I share what I am building, what I am learning, and the lessons I pick up along the way. It is part working notebook, part technical journal, and part personal record of the path that brought me here.

What I do

I build full-stack applications and work on AI-powered systems that solve practical problems. I enjoy taking ideas from the early concept stage all the way to a product people can actually use. That includes thinking through the interface, designing APIs, building the backend, and adapting the system as requirements change.

What keeps me interested in software is that it is always moving. New frameworks, better workflows, different architectures, and more capable tools show up constantly. I like that pace. It pushes me to stay curious, keep learning, and become more flexible as a builder.

My path into tech

My path into technology was not a straight line.

I studied pharmacy, and for a time that was the academic and professional direction I was following. That experience gave me discipline, patience, and a structured way of thinking. It taught me how to pay attention to detail, how to take responsibility seriously, and how to keep learning even when the material is demanding.

But over time, I found myself increasingly drawn to technology. I was interested in how digital tools are built, how products solve real problems, and how software can create opportunities across industries and borders. That interest became more than curiosity. It became a real shift in direction.

So I moved into tech.

That transition was not about abandoning one field casually. It was about recognizing where my energy, focus, and long-term growth were leading me. I started learning by doing, building, experimenting, reading, fixing mistakes, and gradually becoming more confident in how I approached software development.

Learning through adaptation

One of the most important things I have learned is that growth in tech depends heavily on adaptation.

You rarely get to stay comfortable for long. Tools change. Stacks change. Client expectations change. The way you stay relevant is by learning quickly and applying what you learn in real work.

That ability to adapt has helped me work with both local and international clients. Different clients bring different expectations, communication styles, timelines, and technical needs. Being able to understand the problem, choose the right tools, and adjust to new technologies has been one of the most valuable parts of my journey so far.

I do not see learning as a separate phase that ends once the work begins. For me, learning is part of the work. Every project introduces something new, whether that is a better engineering practice, a different product mindset, or a tool that changes how the whole system should be built.

Why this blog exists

I created this blog to document that journey in public.

I want this space to hold ideas, technical discoveries, project notes, lessons from client work, and reflections on building with modern tools. Some posts will be practical. Some will be exploratory. Some will simply capture what I am thinking about at a given point in time.

If you are building, learning, switching paths, or trying to grow in tech, I hope some of what I share here is useful to you.

Looking ahead

I am still learning. I am still building. And I am still evolving in the kind of work I want to do.

Right now, I am especially interested in full-stack product development, AI agents, and systems that turn powerful ideas into useful tools. This blog is one way I want to make that journey visible.

Thanks for reading. More to come.