Calling a notebook the “most important tool” for a dev is pure romanticism. Useful for some, sure, but let's not pretend it outweighs a debugger, version control, or CI. This isn't craftsmanship cosplay, it's software engineering.
In a few years of my career now I never had to use a debugger or CI. Console debugging is good enough usually. On version control I agree.
As a developer, my most important tools are a pen and a notebook
31–40 of 302 posts
Re: As a developer, my most important tools are a pen and a notebook
#32Re: As a developer, my most important tools are a pen and a notebook
#33Re: As a developer, my most important tools are a pen and a notebook
#34I don't understand the pen/physical notebook thing. It's slow to write, insanely slow to search what you've written, almost impossible to copy or share.
To me, none of the qualities you listed matter when it comes to sketching ideas, thinking about problems, staying on track while problem solving. When I'm done with the task, I read through my notes once and throw it out.
Re: As a developer, my most important tools are a pen and a notebook
#35Calling a notebook the “most important tool” for a dev is pure romanticism. Useful for some, sure, but let's not pretend it outweighs a debugger, version control, or CI. This isn't craftsmanship cosplay, it's software engineering.
Thanks for pointing this out. In the same vein there are so many posts about productivity systems where people put endless amount of time into crafting their gtd notebooks with tabs and lists, etc. All that time spent to be productive instead of actually being productive. Or people describing their ideal Obsidian work flows instead of actually noting anything useful down in it. People writing about how they built the…
Re: As a developer, my most important tools are a pen and a notebook
#36Earlier quoted context omitted.
In the context of this post it's not about preserving or sharing the thoughts. Writing, in this case, is a "thinking tool". Forcing yourself to materialise the thoughts as actual, written, text helps form clear ideas.
that’s so alien to me. for me, writing by hand is frustrating to the point of distraction. if I want to think clearly, my best bet is to do it silently, in my head.
To me, if the problem is too complex, or more likely, if I expect to be distracted by family and chores, "building in my head" is not the best option as it all falls apart and need to build it up from scratch (though admittedly faster than last time).
Re: As a developer, my most important tools are a pen and a notebook
#37I don't understand the pen/physical notebook thing. It's slow to write, insanely slow to search what you've written, almost impossible to copy or share.
It's remarkable how much of the lecture you'll remember. And when you read your handwritten notes, you'll remember the lecture that went with it.
Re: As a developer, my most important tools are a pen and a notebook
#38I don't understand the pen/physical notebook thing. It's slow to write, insanely slow to search what you've written, almost impossible to copy or share.
Funny. I was tolling the virtues of my spiral notebook which is always on my desk to a coworker, whom I was trying to get out of some trouble and i got... silence. That notebook is the difference between said coworker and I. She didn't get it. That notebook is the fastest most accessible tool to capture my thoughts. I can state concisely what was discussed in a team meeting last october before any notetaking tool boo…
Re: As a developer, my most important tools are a pen and a notebook
#39Calling a notebook the “most important tool” for a dev is pure romanticism. Useful for some, sure, but let's not pretend it outweighs a debugger, version control, or CI. This isn't craftsmanship cosplay, it's software engineering.
In a few years of my career now I never had to use a debugger or CI. Console debugging is good enough usually. On version control I agree.
Re: As a developer, my most important tools are a pen and a notebook
#40Calling a notebook the “most important tool” for a dev is pure romanticism. Useful for some, sure, but let's not pretend it outweighs a debugger, version control, or CI. This isn't craftsmanship cosplay, it's software engineering.
In a few years of my career now I never had to use a debugger or CI. Console debugging is good enough usually. On version control I agree.