<?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: Mindaugas Jacionis</title>
    <description>The latest articles on DEV Community by Mindaugas Jacionis (@mindaugasjacionis).</description>
    <link>https://dev.to/mindaugasjacionis</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%2F92188%2Fe0a90977-500e-4c42-8ea1-68eb9ba56207.jpg</url>
      <title>DEV Community: Mindaugas Jacionis</title>
      <link>https://dev.to/mindaugasjacionis</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mindaugasjacionis"/>
    <language>en</language>
    <item>
      <title>I should read instead of scrolling 📄</title>
      <dc:creator>Mindaugas Jacionis</dc:creator>
      <pubDate>Thu, 20 Feb 2020 21:39:52 +0000</pubDate>
      <link>https://dev.to/mindaugasjacionis/i-should-read-instead-of-scrolling-4ei5</link>
      <guid>https://dev.to/mindaugasjacionis/i-should-read-instead-of-scrolling-4ei5</guid>
      <description>&lt;p&gt;I have this habit of hoarding digital material. Either it is browser tabs that &lt;em&gt;"I'll use later"&lt;/em&gt;, or, in this case, &lt;code&gt;dev.to&lt;/code&gt; newsletters that &lt;em&gt;"I will read later".&lt;/em&gt; ⌛️&lt;/p&gt;

&lt;p&gt;Today is the day I went through my inbox, replied all emails I intended to reply, rescheduled any that needed to be postponed. Basically went for &lt;strong&gt;#zero-inbox&lt;/strong&gt;. By the end, I was left with 4 newsletters from &lt;code&gt;dev.to&lt;/code&gt; that I was postponing, because they contain content that got my curiosity. &lt;br&gt;
So, what to do? It is almost &lt;em&gt;11:00 PM&lt;/em&gt;, but I wanted to get my inbox empty and also get to bed at a decent time. &lt;br&gt;
Email! I will email myself the list of what to read! For quite some time I wanted to read during my breaks at work, but end up searching for the article that would be not too long, not too short, and something of interest to me. &lt;br&gt;
So two birds with one stone!🐦🐦&lt;/p&gt;

&lt;p&gt;What I did:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;went through those newsletters and collected links with articles that &lt;em&gt;spark interest&lt;/em&gt; for me 📄&lt;/li&gt;
&lt;li&gt;added small note by the links so I wouldn't need to mentally-parse the link (makes the list more accessible to me + fun) 📝&lt;/li&gt;
&lt;li&gt;scheduled the email to drop in my work inbox about the time I'll get to the office 📧&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now I was raised(by my peers and mentors in the dev world) that &lt;strong&gt;sharing is caring&lt;/strong&gt;. Therefore, I'm sharing my upcoming read list:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;a href="https://dev.to/integerman/how-to-contribute-to-open-source-software-4pbl"&gt;how to contribute to OSS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/coderbyte/how-to-build-a-side-project-that-will-impress-future-employers-nl2"&gt;might help with that pet-project motivation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/arcanis/introducing-yarn-2-4eh1"&gt;you should check out what's all the fuss about yarn 2&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/ibrahima92/how-to-build-a-pwa-from-scratch-with-html-css-and-javascript-4bg5"&gt;Yes yes, you know all the what's and how's of PWA. Now build one in vanilla JS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/zaklaughton/the-only-3-steps-you-need-to-mock-an-api-call-in-jest-39mb"&gt;you don't like mocks, so read some more about them&lt;/a&gt; &lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/liaowow/take-this-quiz-understand-how-this-works-in-javascript-44dj"&gt;this is annoying. And by this I mean JavaScripts this&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/pluralsight/analyzing-the-attacks-on-my-website-30jf"&gt;digital security matters!&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/davinc/graphql-for-beginners-3f1a"&gt;it's about time to brush-up on GraphQL&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://dev.to/atsmith813/how-do-you-get-familiar-with-a-new-codebase-4106"&gt;new codebase is always overwhelming. Maybe this will help&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/nprimak/work-culture-toxicity-in-tech-2jn2"&gt;don't deny, you love to read-up on company culture&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Happy reading! 🤗 And feel free to share your tips and tricks on how to read more, or improve one's days in other ways! 🙇‍♂️&lt;/p&gt;

&lt;p&gt;&lt;em&gt;P.s. I don't expect to go through the list in one sitting. No need to make a burden out of the fun! I'll definitely read a few of the articles. By the time for the next email to myself, I'll probably be done with the list&lt;/em&gt;&lt;/p&gt;

</description>
      <category>learning</category>
      <category>read</category>
      <category>web</category>
      <category>newsletters</category>
    </item>
  </channel>
</rss>
