Log driven programming (2013)
antirez.com
Log driven programming (2013)
1–10 of 69 posts
Re: Log driven programming (2013)
#2This is my workflow and has been for the past 10 years or so.
Whenever you think of something else that needs doing, write it down so you stop feeling the need to keep it in mind.
Re: Log driven programming (2013)
#3Ostensibly, this is what TODO comments have always been for.
Realistically, I guess it's probably better that these types of comments remain out of the code itself unless you and your team can practice proper rigor around them, e.g. using prehooks to enforce that no TODOs are left around before committing or merging.
Re: Log driven programming (2013)
#4I use postits for this.
I used to use TODOs, but then if I wasn't looking at the code I forgot about it, and a lot of the stuff didn't have a spot it needed to go. It was just stuff I thought about while I was doing something else.
Daily (or twice daily) I reorder and prioritize. Every week or two there's a postit cleanup party where old postits get trashed or logged. A lot of the stuff that I trash isn't bad....it's just not in scope for the stuff I'm currently doing.
ADD: One of the beauties of postits on my monitors is that when my mind wanders -- as it tends to do -- I'm naturally looking at other stuff I should be thinking about. So when I postit stuff and put it somewhere in my field of vision, I'm telling my subconscious to start working on what I want to do with this stuff.
Re: Log driven programming (2013)
#5https://orgmode.org/manual/Capture-_002d-Refile-_002d-Archiv...
> An important part of any organization system is the ability to quickly capture new ideas and tasks, and to associate reference material with them. Org does this using a process called capture.
Re: Log driven programming (2013)
#6Ostensibly, this is what TODO comments have always been for. Realistically, I guess it's probably better that these types of comments remain out of the code itself unless you and your team can practice proper rigor around them, e.g. using prehooks to enforce that no TODOs are left around before committing or merging.
>I guess it's probably better that these types of comments remain out of the code itself unless you and your team can practice proper rigor around them, e.g. using prehooks to enforce that no TODOs are left around before committing or merging.
Why? If they're "out of the code" they still can be ignored before committing or merging just as well...
Re: Log driven programming (2013)
#7How is something as frivolous as taking notes while programming, which many people do, worth a blog post and a mention here on HN? Let alone turning it into some dogmatic principle to work by, by calling it 'log driven' programming. What is next? Keyboard driven programming? 3-monitor-driven programming?
I do this:
While programming it pays off to stop and think about the code. I call this, thought driven programming.
Re: Log driven programming (2013)
#8How is something as frivolous as taking notes while programming, which many people do, worth a blog post and a mention here on HN? Let alone turning it into some dogmatic principle to work by, by calling it 'log driven' programming. What is next? Keyboard driven programming? 3-monitor-driven programming? I do this: While programming it pays off to stop and think about the code. I call this, thought driven programming…
"Common sense is not so common." - Voltaire
Re: Log driven programming (2013)
#9[deleted]
Re: Log driven programming (2013)
#10Yep, a notepad with a direct step by step 1 liners is very effective to get a ton done in one day.
Have it between you and the keyboard so it can't be ignored, presumably not ruining your typing experience.
Straight up notepad or sublime works too.