The Developer’s Box For too long, we’ve confined ourselves to a title: “developer.” We write code, we fix bugs, we build features. We are the architects and construction workers of the digital world. And while that is a noble and essential craft, the label itself can become a box. It can narrow our focus to the how – the languages, the frameworks, the systems – and make us lose sight of the why. ...
Software development is often seen as a discipline of pure logic and rigid structures. We talk about architecture, frameworks, and design patterns – the building blocks of a rational and predictable process. But what if there’s another side to it? A more intuitive, artistic, and dare I say, philosophical approach to building things? This is the story of my journey with “vibecoding” while building a personal project called Dhanika. What is Vibecoding? The term “vibecoding,” recently popularized by Andrej Karpathy, describes a software development approach that is less about rigid plans and more about the “vibe” of the project. It’s about letting your intuition and the feel of the product guide the development process. Instead of detailed specs and roadmaps, you work with a general idea, a vision, and you let the project evolve organically. ...
In the world of software development, abstraction is one of the most powerful tools at our disposal. Yet, it is often taken for granted—seen merely as a technical concept or a convenience. In truth, abstraction is much more than that; I agree it’s a confusing topic for some, but it represents a currency of trust and a gateway to creative problem-solving. Abstraction as Trust At its core, every abstraction is built on trust. When we build or use a library, framework, API, or even a programming language, we trust the people or systems who designed it. We trust that these abstractors have already handled the intricate details—the “hows”—so that we don’t have to. ...