### Linear Noting and Sequencial Work We all [[Notes management|took notes]] at some point, especially in school, but we wrote them in a very linear way, divided into isolated subjects. During lessons, topics were taught one after another, in what I call a siloed manner. Each area of [[Knowledge]] we learned was entirely separate from the others. For example, while learning math, there was no context from history or [[physics]] to connect it to. Everything was isolated. Similarly, taking notes and studying often happened in this linear, disconnected fashion. The same principle applies to our work. Even though we have tools like task boards that give the impression of a lot happening at once, the reality for an individual worker is still very linear. Tasks are completed one after another. Sure, there’s room for exceptions, but the ideal workflow is often simplified: focus on one task, finish it, and then move to the next. This approach works because it avoids the cost of [[Context Switch|context switching]]. ### The Mind-Killer And it’s true—switching between tasks isn’t always costly when done occasionally, and working sequentially is relatively straightforward. But sooner or later, you encounter a specific kind of frustration, especially familiar to programmers. ![[Context Switch#^is-the-mind-killer]] Imagine being deep in focus, with abstract ideas flying around in your head, headphones on, immersed in your “flow.” Suddenly, someone interrupts you to address something urgent. Or maybe a client writes to report a fire that needs immediate attention. It’s as if your focus bursts like a bubble, and you’re thrown into a void. ^before-void This void - the result of context switching - can become a serious issue if you don’t have strategies to manage it. It disrupts your workflow and makes it hard to return to where you left off. ^in-void ### Too Many Threads, Too Much Noise > [!warning] Too many parallel threads > At certain point of time even [[Pomodoro]] won't help. ^too-many-parallel-threads [[Pomodoro]] works well for task-focused workflows, but when you have to juggle multiple threads simultaneously, it gets increasingly difficult. You might be wondering, `Wait, wasn’t this supposed to be about Obsidian and methodologies?` It is, but here’s the thing: my main motivation for adopting any system to manage my [[Knowledge]], tasks, and projects came directly from the problem of context switching. I found myself taking on too many things at once, constantly switching between them, and quickly losing the context of where I was. At some point, I realized something wasn’t working. Sure, I could blame it on taking on too much or being overcommitted, but the truth was I simply lacked the tools and processes to return to tasks effectively. That’s where the problem became clear. And that’s where the idea of building a second brain really began to make sense. ### Common Problems I Encountered I’ll briefly outline a few typical problems I’ve come across, which I’ll later address in detail. ![[Notes management#^problem-storage]] The first problem is the simplest one: quickly jotting something down. You need a tool where you can effortlessly save a note, forget about it for now, and still find it easily later—whether tomorrow or a year from now. It might sound trivial, but it’s not as easy as it seems. For example, take Notion. If you want to save something quickly, you often get stuck deciding where to put it: Should it be a new page? A new section? A board? This simple act of saving becomes unnecessarily complicated. And then there’s the issue of finding that information later. Everyone who’s used Notion knows how frustrating its search functionality can be. This makes tools like Notion inadequate for solving even this basic problem—at least for now. ![[Notes management#^problem-traction]] The second problem, while slightly different, is still related to note-taking: I want a system to manage what I need to do and what I’m currently working on—something with a clear status. Ideally, I’d like to open an app and immediately see tasks I need to complete today or deadlines I’ve missed that I should prioritize. ^problem-traction ![[Notes management#^problem-projects]] The third problem ties closely to tasks. I want to achieve goals within their deadlines. For example, if I have a project to deliver, how do I keep track of it effectively? This includes managing all related tasks and information in one cohesive way. ![[Notes management#^problem-growth]] The fourth problem builds on the previous ones. Ultimately, I want to grow. I’d like to access everything I’ve noted, reflect on how I’ve worked, and draw insights to improve my productivity in the future. ^problem-growth These problems, while seemingly simple, are the foundation of why I sought a better system. ## Productivity Tools ### The Overwhelming World of Productivity Apps There are countless apps in the productivity category—that’s the first fundamental problem. Earlier, I mentioned tools like Notion, but I’ve also tried others, like Google Keep, and even entire Google ecosystems with Calendar, Tasks, Keep, and a bunch of other tools I don’t even remember now. In the past, I also used tools from the Microsoft ecosystem, like notes stored in Outlook or something similar—I can’t even recall exactly what I was using. Then there are dedicated task management systems, like Jira or Trello, and documentation tools like Confluence. The list is endless. > [!fail] All-in-one tool doesn't exist? > Few solved even one problem completely; > **None solved them all.** Despite trying so many tools, I realized something: few apps solve even one of the problems I outlined earlier effectively, and none of them solve all of them. This became a huge frustration for me. I’m someone who prefers to work within a single app or system. If I need to switch between multiple apps to address different problems, it becomes cumbersome. The issue is that these problems—tasks, projects, and information—are often deeply interconnected. For example, tasks are tied to information, and projects are tied to tasks. If I store these in separate systems, I start losing traction between them. Take Google Keep, for instance. I could store information there, but I’d have to use Google Tasks for task management. There wasn’t a way to connect the two, and I constantly found myself searching for things independently in each app. ### The DIY Approach At one point, I had what I like to call my "Middle Ages of Note-Taking." Like a classic programmer, I thought, “I’ll just write my own app.” That was a terrible idea. I ended up stuck in this phase for nearly a year. Interestingly, I did arrive at some useful insights. I started noticing that the problem lay in how information was structured. Most apps store information, tasks, and projects in a linear or hierarchical format—often like trees. But I realized that information connects in a much more freeform way, more like a graph. So, I built a quick graph-based solution using Neo4j and GraphQL to extract the data. But then I hit another wall—I didn’t know how to design the interface or how I wanted to interact with this system. I lacked a clear vision for the UI or how I wanted to manage everything. In the end, this experiment taught me a lot, but it also showed me how challenging it is to create a system that truly works. ### Productivity at scale I realized something crucial: ![[The scale problem]] - I had a clear understanding of the problems I wanted to address. I wanted an easier way to store information, learn from it, and manage tasks and projects. - I was aware of the tools on the market—apps like Notion, Trello, Google Keep, and others. And here’s the catch—none of the tutorials or documentation I came across explained how to use these tools effectively for large-scale problems. Think about it: most guides and examples show how to handle a small amount of data. Task management tutorials, for instance, might demonstrate with 10 tasks and two groups. That’s fine—but what happens when you have 1,000 tasks, grouped into 20 projects, each with deadlines and overlapping dependencies? No app explains how to handle that complexity. They don’t teach you how to organize or structure it. So, I have to learn [[Method]]s and [[Methodology]] ### Learning Methods and Methodologies I realized I needed to learn two things: ![[Method#^definition]] ![[Methodology#^definition]] This was a turning point for me. I understood that solving my problems wasn’t just about finding the right app; it was about learning _how_ to use these tools effectively, especially at scale. Today, what I’m presenting is more about methodologies than about specific apps. And this is something I’d urge others to consider as well. When people ask, “Do you recommend this app?” or “Will this app solve my problems?” my response is: **Maybe.** But it depends heavily on how you work, what your expectations are, and how you plan to manage your data. Learning the right methodologies is key to making these tools work for you.