<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Martin Makarský</title>
    <description>The latest articles on DEV Community by Martin Makarský (@makma).</description>
    <link>https://dev.to/makma</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F219291%2Ff884b750-5e49-4a81-bf61-c9ffbe8a01cf.jpeg</url>
      <title>DEV Community: Martin Makarský</title>
      <link>https://dev.to/makma</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/makma"/>
    <language>en</language>
    <item>
      <title>Weekly fail (39/2020)</title>
      <dc:creator>Martin Makarský</dc:creator>
      <pubDate>Tue, 22 Sep 2020 12:35:56 +0000</pubDate>
      <link>https://dev.to/kontent_ai/weekly-fail-39-2020-3jnh</link>
      <guid>https://dev.to/kontent_ai/weekly-fail-39-2020-3jnh</guid>
      <description>&lt;p&gt;I spent a good amount of time learning Nuxt.js which caught my attention recently. I walked through the documentation and tutorials and came across some concepts in the framework configuration that seemed unclear and contradictory to me. Also, while browsing StackOverflow, I found out, I wasn't the only one incomprehensive, confused unicorn in this topic. The whole concept of the configuration was hard to grasp for me, so once I mastered it myself, I thought it might be a good idea to share it and write an article about it, just for the sake of simplification for other fellow developers.&lt;/p&gt;

&lt;p&gt;So I wrote a nice article with all the necessary explanations and graphics and I sent it to the framework's Developer Advocate for review and fact-checking (thank you Debbie ;)) only to find out all my findings and pieces of advice originated from the old documentation that's going to be replaced in a little time. So even before publishing, my article had been obsolete 🤦‍♂️.&lt;/p&gt;

&lt;p&gt;After my initial consternation and checking the new docu it turned out the content fitted nicely into my article with just small necessary changes, but I could have made my life easier if I had used the latest documentation.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Lesson learned:&lt;/em&gt; &lt;strong&gt;When learning new programming stuff, make sure to follow the latest documentation.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Clickbait:&lt;/strong&gt; &lt;em&gt;Are you wondering what my article was about? Check &lt;a href="https://kontent.ai/blog/demystify-nuxt-target-mode-and-ssr-properties"&gt;Demystify Nuxtʼs target, mode, and ssr properties!&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>fail</category>
      <category>nuxt</category>
      <category>vue</category>
      <category>content</category>
    </item>
    <item>
      <title>🤦‍♂️ Weekly fail (33/2020)</title>
      <dc:creator>Martin Makarský</dc:creator>
      <pubDate>Tue, 11 Aug 2020 07:58:50 +0000</pubDate>
      <link>https://dev.to/kontent_ai/weekly-fail-33-2020-3eda</link>
      <guid>https://dev.to/kontent_ai/weekly-fail-33-2020-3eda</guid>
      <description>&lt;p&gt;It might be weird, but from time to time, I check for updates manually on my Win 10 computer. Last week, when applying updates on my desktop workstation, right after restarting the PC, my display turned black without any response. Long story short, after waiting 30 minutes and some unsuccessful attempts to hard reset and enter the UEFI settings to revive my screen, I decided to check cables - nothing helped. &lt;/p&gt;

&lt;p&gt;Then, during the constant whining, cursing, and sobbing, I realized I got the second display connected - my TV via the HDMI (love debugging on 55" screen😜). After unplugging this HDMI, I saw the updates were still in progress, at this time, on my default screen. The TV was turned off all the time, however, the operating system somehow changed my default screen selection. I'm pretty sure my PC didn't like all the manual enforced RESETs during the update procedure... 🤦‍♂️ &lt;/p&gt;

&lt;p&gt;&lt;em&gt;Lesson learned:&lt;/em&gt; &lt;strong&gt;If you think your OS is dead or corrupted and you consider reinstalling the system, it's a good idea to check all your connected (even turned off) monitors...&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>fail</category>
      <category>lessonslearned</category>
      <category>windows</category>
      <category>updates</category>
    </item>
  </channel>
</rss>
