Skip to content

Comment on Using a logbook to improve your programming

Comments

Based on a some of the comments so far I think people are glossing over the key elements of the logbook. This isn't simply an activity log.

The first step is to describe the nature of the problem as well your planned solution before beginning. I think this can be a pretty powerful practice in being mindful.

All to often I find myself jumping into a half-baked solution while at the same time having only half-understood the problem.

All to often I find myself jumping into a half-baked solution while at the same time having only half-understood the problem.

This is what kills me in tech interviews. Unfortunately its hard to calm down and think quietly when you are being hounded by the interviewer to "think out loud".

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.