I practice “walking driven development” — every day I take a 2-3 mile walk in the afternoon. Takes 45mins to an hour. I get a lot of problem solving done on those walks.
One of my favorite talks on software development and problem solving in general. Closely related to Peter Naur’s Programming as Theory Building”. And reminiscent of Leslie Lamport’s famous observation:
I believe the best way to get better programs is to teach programmers how to think better. Thinking is not the ability to manipulate language; it’s the ability to manipulate concepts.”
Lastly, but importantly, code is required. You need to take your great ideas and make sure that they solve the problems you think they solve.
I think this is a super important point that seems a little glossed over in the article. In my experience, much of the time, you don’t see certain unknowns when you’re planning a solution for a problem. In some cases, it may even be worth it to write some exploratory code first to explore the problem space before codifying possible solutions.
I practice “walking driven development” — every day I take a 2-3 mile walk in the afternoon. Takes 45mins to an hour. I get a lot of problem solving done on those walks.
One of my favorite talks on software development and problem solving in general. Closely related to Peter Naur’s Programming as Theory Building”. And reminiscent of Leslie Lamport’s famous observation:
I think this is a super important point that seems a little glossed over in the article. In my experience, much of the time, you don’t see certain unknowns when you’re planning a solution for a problem. In some cases, it may even be worth it to write some exploratory code first to explore the problem space before codifying possible solutions.