<?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>Advice on TheJavaGuy Blog 🚀</title>
    <link>/tags/advice/</link>
    <description>Recent content in Advice on TheJavaGuy Blog 🚀</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2016-2026 Ivan Milosavljević. All Rights Reserved.
</copyright>
    <lastBuildDate>Thu, 23 Jun 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/advice/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The right tool for the job is a lie</title>
      <link>/posts/012-the-right-tool-for-the-job-is-a-lie/</link>
      <pubDate>Thu, 23 Jun 2022 00:00:00 +0000</pubDate>
      <guid>/posts/012-the-right-tool-for-the-job-is-a-lie/</guid>
      <description><![CDATA[<p>We&rsquo;ve heard it a thousand times already. &ldquo;Use the right tool for the job&rdquo;. It&rsquo;s a very popular phrase between developers. Just look at the number of times it has been mentioned on <a href="https://hn.algolia.com/?dateRange=all&amp;page=0&amp;prefix=true&amp;query=right&#43;tool&#43;for&#43;the&#43;job&amp;sort=byPopularity&amp;type=story" target="_blank" rel="noopener noreferrer">HackerNews<i class="fas fa-external-link-square-alt ms-1"></i></a>. Or search the internet and see enormous number of articles that <a href="https://duckduckgo.com/?q=right&#43;tool&#43;for&#43;the&#43;job&amp;t=h_&amp;ia=web" target="_blank" rel="noopener noreferrer">DuckDuckGo<i class="fas fa-external-link-square-alt ms-1"></i></a> or <a href="https://www.ecosia.org/search?method=index&amp;q=right&#43;tool&#43;for&#43;the&#43;job" target="_blank" rel="noopener noreferrer">Ecosia<i class="fas fa-external-link-square-alt ms-1"></i></a> or any other search engine have on the topic. While it sounds nice and useful, let&rsquo;s first see some issues with this saying, and also what I recommend you to do when feeling paralyzed by the multitude of tools that people preach are <em>the</em> right ones.</p>]]></description><enclosure url="/posts/012-the-right-tool-for-the-job-is-a-lie/cover.png" length="95671" type="image/png" />
    </item>
    
    <item>
      <title>Don&#39;t prefix JUnit tests with the word test</title>
      <link>/posts/011-dont-prefix-junit-tests-with-the-word-test/</link>
      <pubDate>Thu, 02 Jun 2022 00:00:00 +0000</pubDate>
      <guid>/posts/011-dont-prefix-junit-tests-with-the-word-test/</guid>
      <description><![CDATA[<p>I admit publicly that I like doing code reviews. Code that is submitted for review often contains a lot of implicit information and assumptions of a fellow developer that authored it. Going into their thought process sometimes reveals what we&rsquo;ll see more and more often in software development - a forgotten knowledge about some topic and a way of working that is driven by inertia. &ldquo;Now wait a second Ivan,&rdquo; I hear you say, &ldquo;what in the world does that have to do with prefixing names of my tests with… test?&rdquo;</p>]]></description><enclosure url="/posts/011-dont-prefix-junit-tests-with-the-word-test/cover.png" length="88659" type="image/png" />
    </item>
    
  </channel>
</rss>

