<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>learning · Alex Moreno</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/tags/learning/</link><description>Alex Moreno writes about developer tools, calm software and the occasional home-lab adventure.</description><generator>Hugo</generator><language>en-US</language><managingEditor>hello@example.org (Alex Moreno)</managingEditor><lastBuildDate>Sat, 15 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/tags/learning/index.xml" rel="self" type="application/rss+xml"/><item><title>What a year of journaling taught me about debugging</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/journaling-and-debugging/</link><pubDate>Sat, 15 Jul 2023 00:00:00 +0000</pubDate><guid>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/journaling-and-debugging/</guid><description>&lt;p&gt;For a year I kept a plain-text work journal. The most useful entries were not the summaries at the end of the day. They were the predictions.&lt;/p&gt;&#10;&lt;p&gt;Before running a command I wasn&amp;rsquo;t sure about, I wrote one line: &lt;em&gt;what I expect to happen&lt;/em&gt;. When reality disagreed, the gap between the two lines was almost always the bug.&lt;/p&gt;&#10;&lt;p&gt;It feels slow. It is faster.&lt;/p&gt;</description></item></channel></rss>