{
  "id": 1500674,
  "title": "The Day I Realized I Wasn't Building Apps",
  "url": "https://urgent.news/2026/08/17/the-day-i-realized-i-wasnt-building-apps",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-17T15:00:04.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ashb4/the-day-i-realized-i-wasnt-building-apps-14fm"
  },
  "original_language": "en",
  "account": "For years, I believed I was constructing apps. That was the term I associated with my endeavors. I developed a scheduler, a job bot, a healthcare platform, an AI project, a content tool, and a browser automation system. Upon examining my GitHub, it became evident that these projects were utterly disparate. I've always been apprehensive about this. A single glance at over a hundred repositories could lead others to conclude: \"Wow. This individual is all over the place.\" Intriguingly, I eventually comprehended the opposite. My GitHub can be accessed at https://github.com/ashb4.\n\nOne of my initial projects commenced as a straightforward scheduler. The intention was clear. I detested manually posting content. The process was repetitive, tedious, and seemed best suited for a computer rather than a human. Thus, I devised a scheduler. Or so I thought. As the project progressed, additional elements emerged. Content creation became necessary. Analytics were required. Identifying successful content became essential. Tracking winners was imperative. Reusing content needed to be managed. Strategizing for different platforms became necessary. Eventually, I recognized that I was no longer constructing a scheduler. Instead, I was developing a comprehensive system. This system encompassed discovering, creating, publishing, measuring, and improving content. The scheduler merely constituted one component.\n\nSubsequently, I began scrutinizing other aspects of my projects. I noticed the same phenomenon recurring in nearly every endeavor I had undertaken. My job application tools were not conventional job application tools. They were systems engineered to minimize repetitive effort. My automation initiatives were not genuine automation projects. Rather, they aimed to reduce repetitive effort. Even my AI undertakings were not primarily focused on AI. They sought to diminish repetitive effort. Different technologies, different domains, the same underlying obsession. The pattern eluded me for quite some time. Initially, I thought I suffered from a lack of focus. An abundance of ideas, projects, and directions. However, upon examining the core problems I aimed to address, they all shared a common thread: \"This is tedious. There must be a superior method.\" Job applications, content posting, data entry, decision-making, workflow management - the technology varied, but the frustration remained constant. I concluded that I am a systems builder. This epiphany transformed my perspective on my work. When individuals inquire about my creations, I typically understate them. \"It's a scheduler,\" I might respond. Or: \"It's a content tool.\" Or: \"It's an automation project.\" Technically, these descriptions are accurate. Yet, they are incomplete. Because what I am fundamentally constructing is a system. A compilation of tools, workflows, feedback mechanisms, and automation integrated to resolve a problem. The application is merely the visible facet. The lesson I learned was that for a long time, I perceived my projects as arbitrary. Now, I view them as cohesive. Not because they employ the same technology. Rather, because they all endeavor to resolve the same issue. To mitigate repetitive human effort. To assist individuals in making decisions. To create systems that persist despite waning motivation. Upon recognizing this pattern, numerous aspects became clear. The final thought is that I still construct apps. At least that is the narrative I convey to others. However, I eventually grasped that the apps were never the captivating element. The intriguing aspect was invariably the system concealed within. Once I comprehended this, I began to better understand my own projects and perhaps even myself.",
  "summary": "The Day I Realized I Wasn't Building Apps For years, I thought I was building apps. That's what I called them anyway. A scheduler. A job bot. A healthcare platform. An AI project. A content tool. A browser automation system. Looking at my GitHub, they seem completely unrelated. Honestly, that's something I've worried about before. I have over a hundred repositories. If someone spends thirty…",
  "key_points": [
    "Ash Bhatti realized his projects were systems, not just apps.",
    "He identified a common thread: reducing repetitive effort.",
    "His work focuses on building systems to solve problems."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}