This can be personal, about the domain or code related on a project. This is where notes go in about things I've learned. I've also gotten into the habit of creating a "TIL" document for each day. writing code, without losing the context, because you can always pick up the task again when reading what you have written. Writing is also helpful when you take a break from a task, e.g. also in the direction of investors, hiring etc. When you write, thoughts arise that are not only related to the features. If you write down the features, you know on the one hand the scope and on the other hand you recognize whether this is a USP, commodity or nice to have.
You work away and never come to a defined end, because without a concept you often overlook and forget important things. Indicators are unclear commit messages, no releasable artifacts, and so on.
You quickly produce a ball of mud and have no clear structure. This leads neither to structured code nor to well thought-out features. When working and developing alone, it's easy to fall into the trap of immediately starting to write code. This, in turn, creates capacity for more thoughts and gets you into flow faster because you can immediately "dump" the brain again with each new thought since you already have all the tools at your disposal (pen and paper or a note-taking app). This relieves the brain and reduces the cognitive load and avoids multitasking with thoughts. It gives you the opportunity to talk to yourself and reflect on thoughts without having to keep them in your head. I wrote concepts, ideas and strategies for in my opinion, is even more important when you are a founder on your own. This weekend I did nothing but read and write, with writing predominating. This resonates very much with my experience and I want to share it here. Writing is thinking.- Tiago Forte May 29, 2022
0 kommentar(er)
