Publish Hugo-generated contents.

Author: Publisher

index.xml

@@ -83,8 +83,7 @@ <h2 id="kapt-anger"><code>kapt</code>: anger</h2>
 especially if you are running tests more often than the project executable itself.
 I’ve asked myself a million dollar question.</p>
 <blockquote>
-<p>Do you even need <code>kapt</code>?</p>
-</blockquote>
+<p>Do you even need <code>kapt</code>?</p></blockquote>
 <p>Turns out there was only a single annotation-processing dependency in the project.
 I think you already know which one. Yep, it was <a href="https://google.github.io/dagger/">Dagger</a>.
 Down the rabbit hole we go.</p>
@@ -106,8 +105,7 @@ <h2 id="do-you-even-need-kapt-dagger">Do You Even Need <del><code>kapt</code></d
 <a href="https://golang.org/pkg/context/">Go</a> and
 <a href="https://spring.io/understanding/application-context">Spring</a>.
 You can associate it with Google Dagger <code>@Component</code> or
-a Square Dagger <code>ObjectGraph</code>.</p>
-</blockquote>
+a Square Dagger <code>ObjectGraph</code>.</p></blockquote>
 <p>There is a downside though. The Square version had a small but extensive API.
 In my opinion, it covered almost everything you need from a dependency injection.
 The Google version has grown up big and sometimes not in a good way.
@@ -181,16 +179,14 @@ <h2 id="do-you-even-need-kapt-dagger">Do You Even Need <del><code>kapt</code></d
 <h2 id="decisions-decisions">Decisions, Decisions</h2>
 <p>All of the above got me thinking.</p>
 <blockquote>
-<p>Do you need complex tools to solve simple problems?</p>
-</blockquote>
+<p>Do you need complex tools to solve simple problems?</p></blockquote>
 <p>As you can see, the setup is pretty simple.
 Yes, <em>potentially</em> Dagger could give some benefits,
 but is it worth it increasing build time for every developer on the team
 dozens of times per day? And taking into an account the fact
 that this setup worked for years without any change at all?</p>
 <blockquote>
-<p>Do you need to keep using tools designed for different conditions?</p>
-</blockquote>
+<p>Do you need to keep using tools designed for different conditions?</p></blockquote>
 <p>Let’s face it — the annotation processing is a nice idea but meant
 for special environments.
 It is too verbose to declare everything by hand using Java, so here we go,
@@ -199,8 +195,7 @@ <h2 id="decisions-decisions">Decisions, Decisions</h2>
 I have no idea, it is your codebase and your call. I did mine.</p>
 <h2 id="back-to-the-roots">Back to the Roots</h2>
 <blockquote>
-<p>Having a library isn’t cool. You know what’s cool? Not having a library.</p>
-</blockquote>
+<p>Having a library isn’t cool. You know what’s cool? Not having a library.</p></blockquote>
 <p>Let’s go crazy and use Kotlin to make our own
 <a href="https://en.wikipedia.org/wiki/Inversion_of_control">inversion of control</a> implementation.
 Not <a href="https://github.com/Ekito/koin">Koin</a>,
@@ -211,8 +206,7 @@ <h2 id="back-to-the-roots">Back to the Roots</h2>
 <p>I highly suggest reading
 <a href="https://martinfowler.com/articles/injection.html">a Martin Fowler article</a>
 about inversion of control (IoC) containers.
-It contains almost everything you need to know about IoC, so I’m going to talk about practice only.</p>
-</blockquote>
+It contains almost everything you need to know about IoC, so I’m going to talk about practice only.</p></blockquote>
 <h3 id="modules">Modules</h3>
 <p>What is a module? It is a registry of dependencies.
 What properties a module has? Dependencies on other modules.
@@ -426,7 +420,7 @@ <h1 id="fin">Fin</h1>
 pick it based on your needs and do not adapt your needs to a tool.
 We develop things to solve issues, not to create them.</p>
 <hr>
-<p>PS Bonus points to everyone who got <a href="https://en.wikipedia.org/wiki/A_Flight_to_Remember">the Futurama reference</a> 😉</p>
+<p>PS Bonus points to everyone who got <a href="https://en.wikipedia.org/wiki/A_Flight_to_Remember">the Futurama reference</a> &#x1f609;</p>
 <hr>
 <p>Thanks to <a href="https://twitter.com/artem_zin">Artem Zinnatullin</a> and
 <a href="https://twitter.com/PreusslerBerlin">Danny Preussler</a> for the review!</p>

posts/a-dagger-to-remember/index.html

@@ -72,9 +72,8 @@ <h1 id="nope">Nope</h1>
 Imagine a weird code issue which takes hour after hour and multiply
 it by a factor of uncontrolled external tools and environments.</p>
 <blockquote>
-<p>⚠️ I have to note this explicitly — I’m describing a situation related to small teams.
-Big companies have dedicated units to manage all of this and not a single person.</p>
-</blockquote>
+<p>&#x26a0;&#xfe0f; I have to note this explicitly — I’m describing a situation related to small teams.
+Big companies have dedicated units to manage all of this and not a single person.</p></blockquote>
 <p>Some people might think it is cool to be that person — the only one who knows
 how the toolchain works. Well, it is really not.</p>
 <ul>
@@ -127,8 +126,7 @@ <h1 id="delegate">Delegate</h1>
 <blockquote>
 <p>Human beings are generally not capable of managing more than six to ten people,
 particularly when things go sideways and inevitable contingencies arise.</p>
-<p>— <em><a href="https://www.amazon.com/dp/B00VE4Y0Z2">Extreme Ownership</a></em></p>
-</blockquote>
+<p>— <em><a href="https://www.amazon.com/dp/B00VE4Y0Z2">Extreme Ownership</a></em></p></blockquote>
 <p>The same can be applied to the tools we use. There is a limit on how many
 things a small development team can manage on its own without losing
 the primary goal — to improve the business value of a product.</p>