<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Philosophy on Joey Gennari | Blog</title><link>http://gennari.industries/tags/philosophy/</link><description>Recent content in Philosophy on Joey Gennari | Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Aug 2024 18:57:38 -0400</lastBuildDate><atom:link href="http://gennari.industries/tags/philosophy/index.xml" rel="self" type="application/rss+xml"/><item><title>On Troubleshooting</title><link>http://gennari.industries/posts/on-troubleshooting/</link><pubDate>Fri, 23 Aug 2024 18:57:38 -0400</pubDate><guid>http://gennari.industries/posts/on-troubleshooting/</guid><description>&lt;p&gt;As a long time contributor to StackOverflow, the quality of posts are wide ranging. In the hay-day, a contributor could rack up tons of points by pointing low-effort posters in the right direction with a single line of code. Now I&amp;rsquo;m sure the majority of those questions could be (and are) answered by AI, which was trained on my answers. But I think troubleshooting is the &lt;a href="https://www.etymonline.com/word/hallmark"&gt;hallmark&lt;/a&gt; of a great engineer. Over time, you learn to hone troubleshooting skills and you can often tell a lot about an engineering by the tooling they surround themselves with.&lt;/p&gt;</description></item></channel></rss>