<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nikita Chernykh on Medium]]></title>
        <description><![CDATA[Stories by Nikita Chernykh on Medium]]></description>
        <link>https://medium.com/@n_chernykh?source=rss-822d6c5b2908------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Te-CKMjNzCUEtSVBXZe6MQ@2x.jpeg</url>
            <title>Stories by Nikita Chernykh on Medium</title>
            <link>https://medium.com/@n_chernykh?source=rss-822d6c5b2908------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 17:04:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@n_chernykh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How this drawing changed me as a developer]]></title>
            <link>https://medium.com/hackernoon/how-this-drawing-changed-me-as-a-developer-a0ff79457f20?source=rss-822d6c5b2908------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0ff79457f20</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Nikita Chernykh]]></dc:creator>
            <pubDate>Fri, 15 Jun 2018 11:06:34 GMT</pubDate>
            <atom:updated>2023-01-14T21:57:16.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gltd7dthVH3YD_aOryHJQA.jpeg" /><figcaption>First drawing and version of Internet Junkie</figcaption></figure><p>Today I want to share with you how this small drawing became a functional chrome extension and how it changed me as a developer. One day while browsing the internet I noticed that I completely lost track of time. I thought it would be a great idea if I could track how much time I wasted surfing the web. To solve this problem I decided to make what eventually became the <a href="https://chrome.google.com/webstore/detail/internet-junkie/dnofoicangnkgdijdikmnkfjokjlfigj">Internet Junkie</a> chrome extension.</p><h3>How it started</h3><p>I started with jQuery. I wish I could use <a href="https://reactjs.org/">React</a> or other popular frameworks but I had to work with what I knew at that time to make it happen. I was motivated to learn other libraries and frameworks but had no project to apply them to. I’m the type of learner who always tries to get the value out of what I do. Whenever I set out to learn something, I like to apply it to a real-world problem I’m encountering. I don’t like to learn things simply because “everyone” thinks it’s great to know — I want to learn by figuring out the best approach that can help me to solve the problem.</p><p>At a certain point the jQuery became messy, and I started thinking about switching to AngualrJS. The conversion was challenging, but more importantly, it introduced me to a scaling problem. Now I had way too much more code to work with. I had unnecessary logic in angular controllers, my code was repetitive, and it felt unorganized.</p><p>So I decided to clean it up a bit.</p><h3>Small steps</h3><p>I separated Internet Junkie in different features and put everything related to that feature in the same folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/289/1*Sh8rCi0_Dfk5q5EYxOaNcg.png" /><figcaption>Feature Staructure</figcaption></figure><p>For app logic I have everything in background.js (in background folder) that I converted into a module that I’m planing ot split in smaller modules in the future. <a href="http://browserify.org/">Browserfy</a> helped me to bundle everything and I added <a href="https://facebook.github.io/jest/">Jest</a> for testing.</p><h3>Learning to test — my “Aha!” moment</h3><p>Before tackling this project, I was always afraid of testing and I couldn’t see the value in it. “Why would I write the code twice”, I thought. Now I know why it didn’t make sense to me. I couldn’t see the values because many of my early projects were small and short-lived.</p><p>While working on Internet Junkie day after day I noticed I was becoming afraid of making changes to parts of the project simply because they were already working. That fear I had, because I didn’t trust my code anymore! This is when it became clear why testing is a “must”! After writing and covering 70% of my code with tests, the fear of code refactoring disappeared. I became more confident and could focus on new features.</p><h3>How this project changed me</h3><p>I’m no more the same developer I was before. Now, when starting a project I try to keep these important learnings in mind:</p><p>1. Early decisions can have both positive and negative effects down the road. Think carefully about what languages and frameworks you decide to use. What is the problem you are trying to solve and are you using the right tools?</p><p>2. Write reusable code. If possible, break up your code into smaller features and reuse the common pieces to keep code <a href="https://en.wikipedia.org/wiki/Don%27t_repeat_yourself">DRY</a>(Don’t repeat yourself) and readable.</p><p>3. Test! Writing tests will not only help you better understand your code, but will also give you the confidence to make changes without worrying about accidentally introducing bugs.</p><p>4. Don’t be afraid to make mistakes! I use this quote as my guide to coding “Move fast and break things.”. The idea is that if you never break anything, you’re probably not moving fast enough.</p><p>5. Find someone to give you feedback. Event if you have 5–10 users that can motivate you to make the best app just for them!</p><h3>What Internet Junkie taught me</h3><p>The biggest takeaway for me, was the importance of planning. When building something new in code you often get stuck. Sometimes so much that it’s easy to get discouraged. I realized that I was getting stuck because my tasks were too big to get started on them. I learned to spend more time on planning and breaking thing up into smaller parts. This approach helped me many times while working on Internet Junkie, and without it I never would have finished it.</p><p>Finally, I learned how important it is to find the reason behind why I’m doing the project. For me, without a goal, I lose motivation, and without motivation it’s no more fun. Who likes to work on something they don’t like? Sometimes you have to but better when you have a choice. I am motivated by making something that helps or saves time for people.</p><p>When I figured this out everything cleared up in my head and I knew what I have to do next.</p><h3>How it looks today</h3><p>I released a stable working version but there is much more to come.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*tZA4V9SOmsCGzOrEnFWRqg.png" /><figcaption>Internet Junkie today!</figcaption></figure><p>I think everyone has their own way of learning and this is mine. I hope this inspires someone who is stuck or about to start a project.</p><p>Thanks for reading! If you enjoyed, drop me a few claps below. 👏</p><p><a href="https://chrome.google.com/webstore/detail/internet-junkie/dnofoicangnkgdijdikmnkfjokjlfigj">Internet Junkie</a>, your best internet time tracker. Track how much time you spend on the browser and analyze how productive you are online. Internet Junkie shows statistics on your top 10 visited websites for a full week!</p><p><em>Thanks to </em><a href="https://medium.com/@jen_n_taylor"><em>Jen Nicole Taylor</em></a><em> for helping me edit this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0ff79457f20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-this-drawing-changed-me-as-a-developer-a0ff79457f20">How this drawing changed me as a developer</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to add linting or react-app-start for dummies]]></title>
            <link>https://medium.com/@n_chernykh/how-to-add-linting-or-react-app-start-for-dummies-979b3cfc5bce?source=rss-822d6c5b2908------2</link>
            <guid isPermaLink="false">https://medium.com/p/979b3cfc5bce</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Nikita Chernykh]]></dc:creator>
            <pubDate>Wed, 13 Jun 2018 12:00:01 GMT</pubDate>
            <atom:updated>2018-06-13T12:00:01.803Z</atom:updated>
            <content:encoded><![CDATA[<p>You decided to create a <a href="https://reactjs.org/">react</a> app. First, you go to a clean example from official react <a href="https://github.com/facebook/create-react-app">github repo</a>.</p><p>Hmm, let’s follow the steps and hope for the easy peasy start.</p><pre>npx create-react-app my-app<br>cd my-app<br>npm start</pre><p>It’s suggested to check you <a href="https://nodejs.org/en/">node</a> version to be <strong>&gt;=</strong> 6. Let’s check that in out terminal.</p><pre>$node -v<br>v6.10.1</pre><p>Bam! We good. Go back to previous commands.</p><pre>npx create-react-app my-app<br>npx: <strong>command not found</strong></pre><p>Oh we need npx. As a beginner who knows what is it but lets google.</p><p>Ok after first search we know that we can install it with npm “ok if that’s what you want”</p><pre>npm i -g npx </pre><p>Finally we can run the commands!</p><p>1,2,3. Yay, the app is working!</p><p>But STOP! What is the first thing you see when you open<strong> App.js </strong>to play around with react?</p><p>If you have linter on your editor probably you see…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/749/1*tx0AclBupiXkv0nM3lHdqg.png" /><figcaption>eh red squiggly line</figcaption></figure><p>How annoying is that error line? Probably this can be fixed as easy as we started the react app.</p><p>Not so much.</p><p>You can start googling how to lint react projects now…</p><h3>How to solve this for Atom editor</h3><p>In plugins, I found out that you need to install this two: <strong>linter, linter-eslint</strong></p><p>Done!</p><p>Let’s reopen the file and see if the line is gone.</p><p>Nope, still there.</p><p>Google more!</p><p>Ok, we need to have a config file for eslint.</p><p>In the root of your project create <strong>.eslintrc</strong></p><p>Now search for the best configuration begins and of course, there is so many version online. Some are outdated, some are overkill but after trying a bunch of them you start noticing a common pattern in them.</p><p>Let’s go with simple one that I found thanks to <a href="http://www.zsoltnagy.eu/use-eslint-like-a-pro-with-es6-and-react/">this article</a>.</p><pre>{<br>    &quot;plugins&quot;: [<br>        &quot;react&quot;<br>    ],<br>    &quot;parserOptions&quot;: {<br>        &quot;ecmaVersion&quot;: 6,<br>        <strong>&quot;sourceType&quot;: &quot;module&quot;,</strong><br>        &quot;ecmaFeatures&quot;: {<br>            &quot;jsx&quot;: true<br>        }<br>    },<br>    &quot;env&quot;: {<br>        &quot;es6&quot;:     true,<br>        &quot;browser&quot;: true,<br>        &quot;node&quot;:    true,<br>        &quot;mocha&quot;:   true<br>    },<br>    &quot;extends&quot;: [<br>        &quot;eslint:recommended&quot;,<br>        &quot;plugin:react/recommended&quot;<br>    ],<br>    &quot;rules&quot;: {<br>    }<br>}</pre><p>Many example that I found online was missing this:</p><p><strong>“sourceType”: “module”</strong></p><p>Which is very important for us to fix the squiggly line. ¯\_(ツ)_/¯</p><p>Wooh. OK, can the red line go away now!</p><p>WHAT!? Still there? Whyyyy?</p><p>Again thanks to <a href="http://www.zsoltnagy.eu/use-eslint-like-a-pro-with-es6-and-react/">this article</a>. We need to install few dependencies.</p><p>In you terminal run this:</p><pre>npm install eslint eslint-plugin-react eslint-watch --save-dev</pre><p>That is what every tutorial for adding es-lint to react project should start with but we are ending with it. So you read until the end ;)</p><p>After the installing dependencies go reopen the <strong>App.js.</strong></p><p>Yes, yes, yes the line is GONE.</p><p>This took a while and I didn’t even start writing my first line of code. Let’s hope in the future things go smoother. Good luck with your react app and happy coding!</p><p>Let me know if this helped anyone or made you smile. Thanks for reading! If you enjoyed, drop me a few claps below. 👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=979b3cfc5bce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>