<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://blog.teacraft.dev/feed.xml" rel="self" type="application/atom+xml" /><link href="https://blog.teacraft.dev/" rel="alternate" type="text/html" /><updated>2026-06-03T19:46:04+00:00</updated><id>https://blog.teacraft.dev/feed.xml</id><title type="html">Ramblings of a mad scientist</title><subtitle>Software engineer and mad scientist blogging about whatever I find interesting</subtitle><entry><title type="html">The art of mastery</title><link href="https://blog.teacraft.dev/software,/craftsmanship/2026/06/03/art-of-mastery.html" rel="alternate" type="text/html" title="The art of mastery" /><published>2026-06-03T00:00:00+00:00</published><updated>2026-06-03T00:00:00+00:00</updated><id>https://blog.teacraft.dev/software,/craftsmanship/2026/06/03/art-of-mastery</id><content type="html" xml:base="https://blog.teacraft.dev/software,/craftsmanship/2026/06/03/art-of-mastery.html"><![CDATA[<p>Hello everyone. Trying this content creation thing. Thank you for viewing my first post</p>

<p>What do software engineering and making tea have in common? On the surface not much. Software engineering requires building code that is resilent to change and is proven to work all while tracking moving requirements, cross tream dependencies, and the ever shifting software ecosystem.</p>

<!--more-->

<p>Making tea seems simple by comparison. Find some quality leaves, put them in hot water, and wait until done</p>

<p>Surprisingly they have a lot more in common than one would think. Building software well requires learning what good code is and recognizing what is worth fixing and what is likely to change. Making tea requires learning how those leaves respond to different water temperatures, brewing times, and even brewing methods.</p>

<p>Both of these arts require mindful practice and dicipline to master. In fact my favorite brewing method is a form of Chinese tea making called gong-fu cha. Which literally means making tea with skill, or making tea through mindful practice.</p>

<p>Where am I going with this you might ask? There is a quality to great engineers I have noticed. Our hobbies often require this mindful practice. I have seen a surprising overlap in the technology space with how my peers and I all spend our free time.</p>

<ul>
  <li>Tea making</li>
  <li>Music</li>
  <li>Drawing</li>
  <li>Rock climbing</li>
  <li>Bread baking</li>
  <li>Martial arts</li>
  <li>Grand strategy games</li>
</ul>

<p>These are all activities outside of our jobs that require the same kind of practice and dicipline to master. While we love building software, I think it is something more fundamental, we thrive of incremental improvment, and slowly mastering a skill. Whether from a traditional CS degree, bootcamp, or self taught, the best engineers I have had the delight of working with all shared these traits.</p>]]></content><author><name></name></author><category term="software," /><category term="craftsmanship" /><summary type="html"><![CDATA[Hello everyone. Trying this content creation thing. Thank you for viewing my first post What do software engineering and making tea have in common? On the surface not much. Software engineering requires building code that is resilent to change and is proven to work all while tracking moving requirements, cross tream dependencies, and the ever shifting software ecosystem.]]></summary></entry></feed>