<?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 Yasha Gootkin on Medium]]></title>
        <description><![CDATA[Stories by Yasha Gootkin on Medium]]></description>
        <link>https://medium.com/@yashagoonki?source=rss-d67138a60cd2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*u8YPbPCRhQ7EmEPhKP6KQg.jpeg</url>
            <title>Stories by Yasha Gootkin on Medium</title>
            <link>https://medium.com/@yashagoonki?source=rss-d67138a60cd2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:03:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yashagoonki/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[Zooming in on video interviews]]></title>
            <link>https://medium.com/@yashagoonki/zooming-in-on-video-interviews-5ac03ef9d1da?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ac03ef9d1da</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Thu, 09 Apr 2020 20:26:40 GMT</pubDate>
            <atom:updated>2020-04-09T20:26:40.029Z</atom:updated>
            <content:encoded><![CDATA[<p>The good, the bad, the ugly. Here are some tips for conducting better video interviews in these tough times, from a candidate software engineer’s point of view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*_jHwvDXI96okmTnnrXOT3w.jpeg" /></figure><blockquote><em>I think it is safe to assume large enterprises/corporations won’t be reading my tips, but if by any chance you have stumbled upon this article and felt the urge to apply any of my recommendations, then, by all means, I hope they help you and your candidates feel better with the entire process.</em></blockquote><p>So hi there, I am Yasha. I am a software engineer who has recently left WeWork Technologies in search of new opportunities, not expecting the Coronavirus to run over all of my dreams and ambitions. I have started my “job hunt” about a month ago and like everyone else, I have seen most of my processes being halted or frozen. Obviously it didn’t help the anxiety stemming from being out of a job and having to navigate through a looming economic crisis.</p><p>The good news is that as software engineers, we have to consider ourselves lucky. While being fired, having to take a pay cut or having tougher competition for the same career opportunity is probably not at the top of our wishlists, there are still a lot of companies out there functioning the same as before this crazy pandemic has started. Some are even doing better. And since other industries are completely paralyzed (or in some cases even crumble) by the “stay at home” orders, we have to make the most out of our situation.</p><p>I have been extremely lucky to start several processes with some amazing companies even at these tough times. Not everything went according to plan, but that’s okay because I believe you should always adapt and seize the best opportunity out there (it might end up being for the better). So after going through several interviews, I wanted to share my conclusions with you. Hopefully, it will help you avoid mistakes and improve your overall process of candidacy filtering at this new age of remote connections.</p><blockquote>We are all in this together, and so we have to make our best effort despite the circumstances. Here are a couple of takeaways you could implement at your organization (starting from the most trivial ones)</blockquote><h3>Provide instructions to your video platform of choice</h3><p>I can’t believe I have to say this, but please let your candidates know, which video platform you have chosen for the interview. And also attach a short explanation as to how to download it and how to start the conversation. By this point, most of us probably know how <a href="https://zoom.us/">Zoom </a>works, but <strong>you should not assume everyone is well versed in it</strong>. For some people, it may be the first time.</p><p>And if you are not using Zoom, then please, for lord’s sake, provide a detailed explanation as to what and how. <a href="https://products.office.com/en/microsoft-teams/group-chat-software">Microsoft Teams</a> or <a href="https://www.codility.com/">Codility</a> are also great options. But when one company just sent me a Codility link expecting me to realize it is not only a sharable coding platform but also a video platform, let’s just say it was less than ideal. Also, why would I have to guess that pressing the WhatsApp icon button at the top right would start a video conversation (I assume it uses the WhatsApp API behind the scenes, but this is not something you should just guess out of the blue)? <strong>It has to be explicitly stated in the interview invitation</strong>.</p><p><em>Side note: During my Codility video interview, the interviewer’s video box has duplicated, which made it very hard to concentrate. You might want to consider it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*0vHG1NbGr7EVAvVpiv8A-g.jpeg" /></figure><h3>Consider circumstances</h3><p>Look, this predicament is nerve-racking and frightening as it is. People are afraid for their health and the health of their loved ones. They might be afraid of managing their debt without a job, homeschooling and taking care of their children 24/7, having trouble with their landlord or getting their hands on necessary supplies.</p><p>Whatever the case may be, people are under <strong>a lot</strong> of stress these days and as an interviewer, there really is no need in adding to that. We all suffer from bad internet as a result of overused bandwidth. It doesn’t mean you should start talking to a technician, while your candidate is trying to solve an algorithm problem. <strong>Consider switching to a hotspot, talking over the phone instead or rescheduling.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*XpykGqlX0yP6krn7xuESzA.jpeg" /></figure><p>If you have children at home and they are constantly breaking lamps and setting the house on fire, so every 5 minutes you have to go and check what that sound was, it is slightly distracting but obviously very understandable. What is not understandable is claiming a candidate <strong>didn’t take control of the interview</strong>. I mean, what if he was trying to but it was too hard to focus on thinking and explaining when all he hears are weird sounds in the background and the interviewer constantly excusing himself.</p><p>I am not searching for excuses myself, I have had my fair share of bad interviews which I failed due to <strong>my own fault</strong>. And that’s ok, not everything goes according to plan. I try to do my best and learn from it. But when you solve a question despite hearing construction work in the background and your interviewer is pausing every couple of seconds, I really believe the company <strong>should give you another chance</strong> if the only thing troubling them was your “inability to take control of the interview and finish explaining your solution”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*gr8gO_2AVhipoXqIPE9BYQ.jpeg" /><figcaption>Focus level over 9000</figcaption></figure><h3>Back to the drawing board</h3><p>Oh, right there is no drawing board. There is Zoom’s convenient whiteboard feature, as well as <a href="https://awwapp.com/">AWW</a>, which I assume, are not the only options out there. But it is not the same as having a face to face meeting with a whiteboard and a marker to scribble down your thoughts and ideas.</p><p>Online drawing boards are handy enough to let you demonstrate a system architecture but it takes longer and more effort to draw your ideas the way you imagined them. And they definitely <strong>don’t give you a good solution</strong> for demonstrating data structures quickly enough for your interviewers to follow your train of thought.</p><p>If your candidate has Zoom’s whiteboard and Codility open at the same time but still has no means to draw a 9 level binary search tree in 5 minutes, then maybe he shouldn’t be expected to solve the question in 3. Mind-boggling I know, but this is the time for readjustment and reevaluation. <strong>Giving fair chances to your candidates is super important</strong>, now more than ever before, so either provide them with the right tools to answer your questions from the get-go or adjust your questions to fit the current situation and constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*rSy2eBkXSErPVig_tLYIDQ.jpeg" /><figcaption>Trust me, it’s a tree</figcaption></figure><h3>Make the best out of the internet</h3><p>Ah, the internet. What a wonderful creation. Without it, all of this wouldn’t be possible. But since it exists, why not leverage it and convince the best candidates to join you?</p><p>One of the major pain points in the current climate is the <strong>inability of candidates to experience and assess your company from within</strong>. They can’t visit your offices, feel the vibe and see more clearly what they are getting into. But it doesn’t mean the situation is hopeless and there are no ways of improving it. Here are some suggestions/solutions:</p><ul><li>Utilize Zoom’s virtual background feature to <strong>add a photo of your offices </strong>and showcase the daily routine on a normal day. If you have a video taken in your offices, then even better.</li><li>Find out what is most important to a candidate you want to convince to come. If it is people, you might want to organize a Zoom meeting with more employees from your company so they <strong>get to see who they are going to work with</strong> and if there is chemistry, or lack thereof present (Personally, for me this is the most important aspect). Remember that if one of your tests is a home assignment, it means one less person your candidate has met. And if you don’t compensate for that, they might just choose a company where they had good conversations with more people as it could seem like a better fit.</li><li><strong>Describe a normal day at your offices</strong>, activities, and benefits available to your employees and what is expected of them if they chose to join you. This may help your candidates grasp their future day to day better.</li></ul><p>The main key point here is you should invest in giving your candidates the best first impressions, be it face to face or over a video conversation. All of these gestures may prove to be the difference-makers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*7WjFMP4XdwS6uegMUMeeEw.jpeg" /><figcaption>Office vibes are critical</figcaption></figure><h3>To new beginnings</h3><p>Before I bid you adieu, I would like to take the opportunity and remind you that as all billion-dollar celebrities say nowadays, <strong>we are all in this together!</strong> Changing your interview format and adjusting it to the current reality doesn’t necessarily mean you have to compromise. It just means you are doing <strong>your </strong>best to give candidates fair chances as they are doing <strong>their </strong>best to find a suitable workplace under major stress and surrounded by other problems. A lot of companies have already implemented this approach and I have nothing but admiration and gratitude towards them. Just make sure you follow lead :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*omPc0wg1llzjaxGMZoYG-Q.jpeg" /><figcaption>Baby zoomer</figcaption></figure><blockquote><em>Hi, I am a full-fledged software engineer, a part-time entrepreneur and a part-time artist (making my schedule a living hell, but I enjoy every second of it). If you like my content, please be sure to 👏 clap, 📱 share and 👣 </em><a href="https://medium.com/@yashagoonki"><em>follow me</em></a><em>. Feel free to connect with me on </em><a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/"><em>LinkedIn</em></a><em>!</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ac03ef9d1da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Footsteps 1.0.0: The Better Way to Create a New Project From the Ground Up]]></title>
            <link>https://medium.com/better-programming/footsteps-1-0-0-the-better-way-to-create-a-new-project-from-the-ground-up-1e01b4dec15b?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e01b4dec15b</guid>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Sat, 07 Mar 2020 14:54:29 GMT</pubDate>
            <atom:updated>2020-03-09T18:26:42.354Z</atom:updated>
            <content:encoded><![CDATA[<h4>The story of the Electron, Node.js, React, and TypeScript chimera app and how to choose (or cross out) technologies and frameworks</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vO-sQ9ZY5Be5Jlw1LfglA.jpeg" /></figure><p>In the past year, I had my focus shift from Node.js and React to less Node.js and less React. They were still a part of my development stack, but I found myself developing Ruby on Rails microservices and deploying services on Kubernetes way more often. At a certain point, the closest I came to a front end was a Grafana dashboard, and last time I checked, I didn’t develop that one.</p><p>But such is a software engineer’s life: You cycle through a lot of different tasks, depending on what is of the highest priority. So when I was transitioning from my “WeWorker” position to my new “Ex-WeWorker” position, I decided I was going to catch up on everything I missed.</p><p>This is where Footsteps comes in.</p><p><a href="https://github.com/yashag/footsteps">yashag/footsteps</a></p><p>I had envisioned a cool new product I could develop while sharpening my skills and learning new technologies in the process. It would be this amazing desktop application for other developers who are constantly struggling with creating a new project according to best practices. It will guide them through the process, generate most of the boilerplate for them, and everyone is going use it since Mark Zuckerberg is Jewish and we have that in common.</p><p>I guess that is why the following phrase exists: “Keep your standards low and your expectations even lower.”</p><p>Apparently, learning a lot of new technologies is no easy feat. In the timeframe I had, making all my dreams come true would have been impossible. Instead, I built a very solid basis and learned a lot from it. And most importantly, I did not build another to-do list.</p><p>So let’s go over what I have done. Maybe you will like it and want to try and build a similar project yourself. Or maybe you would like to continue mine. Whatever the case may be, I promise to deliver key inputs and conclusions.</p><h3>Follow the Footsteps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w80ggrTXlN798nVQXrmMtw.gif" /><figcaption>Recommended to watch at x0.25 speed.</figcaption></figure><p>Through my experience, I have learned that seed projects and project generators oftentimes create more problems than solutions. More specifically, they create a false notion of lesser work and maintenance being needed, only for you to discover later that synchronizing your forked project with the seed or upgrading your generated code is a huge hassle and way more work than you had bargained for. However, there are two better ways:</p><ol><li>An example repository showcasing a suggested<strong> </strong>setup.</li><li>A guide explaining and comparing different choices with recommendations<strong> </strong>as to what is a better choice in each specific case.</li></ol><p>Enter Footsteps.</p><p>Currently, Footsteps contains the following:</p><ul><li>Welcome step — You are welcome.</li><li>Project selection step — Where you can choose between a Node.js project button and another disabled button.</li><li>Basic information step — Here you input your project’s name, code name (the way it would be referred to in your code), and a short description. My intention was to use this information later on to generate the appropriate boilerplate.</li><li>Repository step — Here I encourage users to open a repository on one of the more common vendors while providing the necessary information on creating and cloning the project.</li><li>Readme step — This is the heaviest step so far. It contains all the available data on how to write README.md files since the invention of the internet.</li></ul><p>Ideally, I would have gotten the chance to implement the following as well:</p><ul><li>License step</li><li>Contributing step</li><li>Dependencies management step</li><li>Directories structure step</li><li>Automatic file creation</li><li>Steps completion checks</li></ul><p>These additions would obviously take Footsteps to the next level, making it an attractive choice for developers who would rather have a helping hand than a script taking over their development process. I am looking at you, create-react-app and Yeoman generators<em>.</em></p><p>But as it stands, the most important takeaways from this project are on the technical side and not the content side. So let’s dive deeper into those and see how this idea can replace your relatively run-of-the-mill to-do lists, blogs, and chats.</p><h3>High-Tech</h3><h4>Electron</h4><p>When it comes to Node.js desktop applications, the first framework that comes to mind is <a href="https://www.electronjs.org/">Electron</a>. This Chromium-based open-source library was initially created by GitHub<strong> </strong>for the Atom<strong> </strong>editor but has since served as the backbone of other giants, such as VS Code, Slack, Discord,<strong> </strong>and more. While other initiatives like <a href="https://nwjs.io/">NW.js</a> and <a href="https://github.com/nodegui/nodegui">NodeGUI</a>/<a href="https://github.com/nodegui/react-nodegui">React NodeGUI</a> (powered by Qt5 instead of Chromium) make headways, Electron ended up being my choice since it has a larger community/support and I was also already familiar with it from previous experience. I was going to tackle a lot of other new technologies/frameworks, so Electron felt like the smarter choice at the time.</p><h4>Electron-Forge</h4><p>Lo and behold, I made the right choice. Ironically, the hardest part of creating a project for creating projects is creating the project itself. What I mean by that is I was searching for a good template with best practices combining:</p><ul><li>Electron</li><li>create-react-app</li><li>TypeScript (more on that later)</li></ul><p>And as trivial as it may seem, I couldn’t find any satisfying explanation or example of how to set up such a monstrosity with good practices in mind. At a certain point, I gave up on this “holy trinity” and decided to focus on my main goals instead: an Electron app written in TypeScript and serving any client-side code (figuring I would simply add React later on).</p><p>This is where <a href="https://www.electronforge.io/">Electron-Forge</a> comes in. As their website states:</p><blockquote>“Electron Forge is a complete tool for creating, publishing, and installing modern Electron applications.”</blockquote><p>Sounds promising, right? Well, I’m happy to report it worked like a charm. I used their TypeScript+Webpack template and ended up having an Electron app with a main<strong> </strong>and a renderer<strong> </strong>process. The idea was for the main process to take care of basic desktop app configurations, while the renderer process will serve my React application (pretty common for Electron setups).</p><p>I also followed this great guide to make sure I was headed in the right direction and that my Webpack was set up correctly:</p><p><a href="https://itnext.io/develop-a-cross-platform-desktop-application-with-electron-forge-react-webpack-typescript-ac2c7452b71f">Develop a Cross-Platform Desktop Application with Electron Forge, React, Webpack &amp; TypeScript</a></p><h4>Webpack</h4><p>Oh, Webpack, why in the blue hell are you so popular? Seriously, how does a module bundler that prides itself on having a ton of unclear configurations and solving its issues by copy-pasting a question mark with jibberish text gain 53,000 stars on GitHub?</p><p>Look, I am not trying to hate on it for fun. All I am saying is I miss the days when Gulp dominated over Grunt, as Grunt was a bunch of copy-pasted configurations, while Gulp required you to write your own tasks and understand the logic behind the piped steps. I guess history repeats itself.</p><p>At this point, though, I would like to acknowledge two things:</p><ol><li><a href="https://parceljs.org/">Parcel</a> and <a href="https://rollupjs.org/guide/en/">rollup</a> are pushing module bundling in the right direction in my opinion, and I highly encourage you to check them out. Everything is out of the box and works seamlessly.</li><li>Once you overcome your fear of Webpack’s configuration, I can see a certain appeal in such a community-favorite bundler handling your project.</li></ol><p>I had overcome my fear of Webpack about two years ago, so this time around, it definitely wasn’t as traumatic as before. But I do have to credit the article I have attached above and <a href="https://itnext.io/@lewispfairweather?source=post_page-----ac2c7452b71f----------------------">Lewis Fairweather</a> for instilling order into my Webpack setup. I ended up having the following Webpack files:</p><ul><li>webpack.main.config.js — Where my Webpack configuration for the main process lies.</li><li>webpack.renderer.config.js — Where my Webpack configuration for the renderer process lies. Didn’t see that one coming, huh?</li><li>webpack.rules.js — Which contains my bundling rules. They are shared between the two config files above.</li><li>webpack.plugins.js — For my Webpack plugins, though admittedly I only have <a href="https://www.npmjs.com/package/fork-ts-checker-webpack-plugin">fork-ts-checker-webpack-plugin</a> here for TypeScript checks.</li></ul><p>I also want to give credit to my awesome friend <a href="https://medium.com/@giladbar">Gilad Bar</a> and his great article:</p><p><a href="https://medium.com/better-programming/how-i-got-over-my-fear-of-webpack-2f66218bb18b">How I Got Over My Fear of webpack</a></p><p>It really inspired me and helped me get through error screens like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/908/1*Vhy_5_CI-OmkfKJMXlpIjg.png" /><figcaption>There were quite a few of them.</figcaption></figure><h4>TypeScript</h4><p>So at this point, I have a useless desktop app that I pretty much copied and generated from other sources. I am starting to wonder if it was all worth it and why I didn’t just create a Svelte to-do list if I wanted to brag about learning something new.</p><p>That makes this section even more intriguing. Remember my Webpack rant from a minute ago? Well, this is not my first rodeo with TypeScript, and I used to have the same reaction towards it. The main reason is that TypeScript was originally developed by Microsoft<strong> </strong>and more specifically by none other than Anders Hejlsberg. Mr. Hejlsberg is the lead architect of C# and was a core developer and designer of TypeScript. Now I have nothing against him. Quite the contrary, I respect him and his many accolades a lot. But I felt like JavaScript was being “stolen” from right under our noses by a heavily opinionated party wanting to transform it into another C#.</p><p>And it shows. Even though TypeScript went open-source and Google had a heavy influence on it, being a C#-type superset of JavaScript caused quite a few issues in my opinion. The best example is probably the private fields/functions. They were developed “the C# way” only for the rug to be pulled out from under it by an ECMAScript proposal (replacing the private<strong> </strong>keyword with a hash symbol). Also, a lot of TypeScript projects I have encountered heavily abused the any<strong> </strong>keyword and contained a black hole directory for interfaces that nobody wanted to organize.</p><p>I realize I have used quite polarizing phrasing, but I always liked JavaScript for what it was: a dynamic functional programming language. And the fact that it is supported by the ECMAScript<strong> </strong>language specification and opinions of multiple experts from different backgrounds reinforced my belief that it was moving in the right direction and soon enough wouldn’t need TypeScript’s features at all (even if I disagree with several ECMAScript proposals myself). Obviously, I was aware of JavaScript’s shortcomings, but I believed it all came down to skill and knowledge. If you know your JavaScript, you shouldn’t struggle too much with its quirks.</p><p>So what has changed?</p><p>I’m not sure. I guess my experience and outlook on software engineering as a whole. Maybe the fact that I had to write code in Ruby for a whole year sucked out the joy of dynamically typed languages for me. I don’t know. What I do know for certain is I now view TypeScript as an essential part of a JavaScript-based development stack.</p><p>Because thinking about it, if you pour your JavaScript project management skills into TypeScript, you shouldn’t end up with a random interface directory. And if you are professional enough, you will disallow the usage of the any keyword through your tsconfig file and type everything in a consistent manner. Only in the most severe and justified cases would you use the unknown<strong> </strong>keyword (kudos, by the way, for introducing this one).</p><p>So, essentially, all my complaints could be answered. Even the private keyword collision was solved pretty quickly with the TypeScript team adding support for the ECMAScript way. And now that I am calm and collected, I can enjoy the benefits of adding TypeScript:</p><ul><li>An amazing IntelliSense (which is worth the TypeScript inclusion by itself).</li><li>A lot more OOP concepts support (like abstractions, polymorphism, and such).</li><li>Support for features that can organize and help my code readability, like enumerable types, namespaces, and decorators.</li><li>Auto-generate support for specifications such as OpenAPI 3.0.</li><li>Easier debugging and error prevention ahead of runtime.</li></ul><p>There are several more, but having considered all of the above, I have to admit I was wrong about TypeScript and that it’s quite beneficial and even necessary to a professional project. Looking ahead at initiatives like <a href="https://deno.land/">Deno</a>, that belief within me becomes even stronger. Now I am kind of its No. 1 fan.</p><p>So yeah, Footsteps is covered with TypeScript from top to bottom.</p><h4>React</h4><p>This is not a new technology for me by any chance, but I would be the first to admit I haven’t gotten much practice with hooks<strong> </strong>and the not-so-new-anymore ContextAPI. To remedy that, I made sure that Footsteps uses both, following their best practices (which in this case means contexts would not be abused and instead would be used for “global” data only).</p><p>Case in point, I have created a context to store the project data the user inputs on the Basic Information step and then used it in the Repository step by utilizing the appropriate hook (I have way more hooks in my code, though). Overall, I am very happy with those additions to React (especially if they help retire Redux).</p><p>I would like to note that I have also considered using MobX for my state management but haven’t found the suitable use case as well as a good enough tutorial showcasing a good integration with an existing React TypeScript codebase. I will keep looking for one, though, and hopefully get the chance to implement a MobX solution within Footsteps in the future (I might use it for the steps movement).</p><h4>UI Framework — Evergreen UI</h4><p>Choosing a UI framework for your React project is pretty simple actually. Just choose Material-UI and move on. Now let me explain it in a non-cynical fashion.</p><p>I have used <a href="https://material-ui.com/">Material-UI</a> for many projects before. It is kind of the go-to framework. And with it having 55,000 stars on GitHub, there is probably no delusion as to why that is. But its greatest pro is also its greatest con: Being so popular means almost every website you see is written with Material-UI. At a certain point, you start wondering if all websites should look the same and be united into one giant website.</p><p>Coincidentally, I have also worked with <a href="https://semantic-ui.com/">Semantic UI</a> for over a year. Now I know, it only has 47,000 stars on GitHub, so how can it even compare? Joking aside, it had a nice presentation, good RTL support (which is what I mainly needed then), and a variety of components.</p><p>So what is the problem? Well, I remember three off the top of my head:</p><ol><li>It might look good on their website, but when you bring over those components onto yours and try to customize them to fit your general design, you sometimes find it impossible to pull off. Some of the components simply looked unnatural — like they were embedded with an iframe or something.</li><li>The support was very limited. I would use a dropdown and try to implement an efficient search or a dropdown within a dropdown, only for me to realize after two hours it is impossible. Why? Because under their example of it working properly, there was a small label saying it is currently unsupported and would only be developed if the demand arises.</li><li>It would update very scarcely. I had literally no hope for dropdowns to be fixed in time for my deadlines. And it really bummed me out.</li></ol><p>A year has passed since I last touched Semantic UI, and I noticed they have made some progress. It is probably a case of too little, too late for me at this point, but they might have remedied most issues.</p><p>Since I ruled out Material-UI and Semantic UI, it was time to try something new. As I have stated before, my goal was to try a lot of new technologies and frameworks. Therefore, I have opted for <a href="https://ant.design/">Ant Design</a>. So is it a viable competitor to the other frameworks with only 57,000 stars on GitHub?</p><p>The answer is probably yes, but I am not sure. The thing is it looks very nice on their website, they have a lot of useful and beautiful components, a huge community, and they even recently released their 4.0 version introducing redesigns, RTL support, and more. But why do all good things come at a steep price? Ant Design is written with the Less CSS extension, meaning it is almost impossible to customize it with your own theme unless you use Less (all puns intended). They do have an instructions page on their website that explains how it can be done without it, but even after following their instructions, it simply didn’t work. I had no intention of introducing Less to Footsteps or letting my UI framework dictate my choices, so I left Ant Design behind. Hopefully, this issue can be fixed soon.</p><p>We have arrived at <a href="https://evergreen.segment.com/">Evergreen UI</a>. I know it seems hopeless at this point since it was not my first choice, but I was actually pretty enthusiastic about Evergreen. I have been following this framework for quite a while. I really liked some component designs they have created and wanted to give this a shot. I was wary of the 9,000 stars on GitHub, as it doesn’t really compare to other frameworks, but I didn’t have much to lose and really wanted to try it out.</p><p>As you can see, it gave Footsteps a pretty unique look, but boy oh boy did I struggle with it. First and foremost, it is very CSS in JS-driven. I started with scss files only for me to acknowledge later on that I can’t handle the design both in Sass and in JS. So I had to move to styled-components instead. That is ironic based on my Ant Design criticism, but it was actually a blessing in disguise. More on that later. But apparently, Evergreen doesn’t work well with styled-components (and according to their GitHub, they are aware). The best example of it was the side tabs, which lost their entire design upon introducing styled-components.</p><p>Also, a lot of their component APIs were very limited, the icon support is tied to Blueprint JS and that’s it, the table resizing is very hard to handle, the theming docs are still unclear and lack explanations, and that’s kind of the tip of the iceberg. I really wanted it to be a huge success, but unfortunately, this was not the case.</p><p>Maybe future versions can salvage this framework and make it stand out in a positive way, but as of right now, I want to move to Material-UI and put my efforts in theming and customizing it in my own unique way. In this case, the proven solution wins by a long shot.</p><h4>CSS in JS — styled-components</h4><p>We’ve arrived at <a href="https://styled-components.com/">styled-components</a>. Don’t worry, this will be short. I have used styled-components before, but I was not a fan of CSS in JS, as I believed it introduced extra clutter. As with TypeScript, I had changed my mind about it.</p><p>My hand with styled-components was forced, as Evergreen UI’s API kind of left me with no choice but to move my entire design to JS. But after gradually transitioning from Sass and making my stylings function the same way, I found out it can be done in a beautiful manner. Here is the gist of it:</p><ul><li>As with Sass, your syles are still separated and kept in a different file ending in<em> </em>.styles.ts<em> </em>or .styles.tsx.</li><li>You can reuse constant JavaScript values for your styled-components and your UI framework (like color palettes, spacings, etc…).</li><li>styled-components can accept default props or handle prop-based design logic. I can’t stress enough how extremely useful and elegant those features can be.</li><li>Hierarchy isn’t handled both in your JS and CSS files anymore. You only customize the specific components you want to alter and leave behind the Sass way of managing hierarchy.</li></ul><p>So in general, once I went over the styled-components docs and gave it another shot (only this time with the best practices in mind), I had a blast. In my opinion, it is really the way to go about styling in this day and age.</p><p>I have also considered <a href="https://emotion.sh/docs/introduction">Emotion</a> but ended up choosing styled-components over it, as it seemed to have a bigger following and I was more familiar with it.</p><h3>The Next Steps</h3><p>I wanted to show you my perspective on the technologies/frameworks I have chosen to work with and give you an idea for a to-do list alternative you can try developing of your own volition. I also wanted to show you the potential of a project like Footsteps and how it can become very useful to developers in the future. Hopefully, it helped you in one way or another.</p><p>Personally, I would have to say that overall I enjoyed working on Footsteps very much. It was an interesting and challenging idea to implement and I learned a lot from it. But since I have done it mostly for educational purposes, I might not continue it for the foreseeable future. So if you want to step in and push Footsteps forward, you are more than welcome!</p><p>Check out Footsteps below:</p><p><a href="https://github.com/yashag/footsteps">yashag/footsteps</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e01b4dec15b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/footsteps-1-0-0-the-better-way-to-create-a-new-project-from-the-ground-up-1e01b4dec15b">Introducing Footsteps 1.0.0: The Better Way to Create a New Project From the Ground Up</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The full stack list of all lists: Overview]]></title>
            <link>https://medium.com/jay-son/the-full-stack-list-of-all-lists-overview-6a356fd0802f?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a356fd0802f</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Mon, 12 Feb 2018 10:41:36 GMT</pubDate>
            <atom:updated>2018-02-13T09:42:41.702Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVShg2LmvZMBtt1j4CWmmw.png" /></figure><p>The list of all lists, the guide of all guides, the roadmap of all roadmaps. Many have tried and many have… well, done a good job for the most part. Yet something is always missing.</p><p>Ironically web development <strong>trends/tools/libraries</strong> and more are scattered all over the web. Top<strong> 10/50/100</strong> lists are everywhere, yet you never seem to know, what is the best approach and the best choice for your current predicament. <strong>Technologies/tools/solutions</strong> keep popping up like mosquitoes in the summer, taking residence mainly in the bounds of the GitHub “trending” section. So what are you, a full-stack web developer living in 2018, supposed to do?</p><p>Facing the same question at my new workplace, we decided to revise our development stack. Taking an additional step towards our goal, I decided to research an enormous amount of articles (in part, the infinite bookmark pool everyone has 😉) , videos and other resources in order to compile the <em>List of all Lists</em>!</p><blockquote>Disclaimer: By no means does that mean, this list is absolute! Au contraire, I would gladly welcome any assistance in expanding this list as you will see down below</blockquote><h3>So what exactly is this “List of all Lists”?</h3><p>Well, first and foremost my <em>List of all Lists</em> is going to revolve around the stack I’m going to work with, which is <strong>React</strong> + <strong>React Native</strong> apps, backed by <strong>Node.js</strong> micro-services. This is important, because it means I am not going to cover Angular, Vue, PHP, etc…</p><p>As for the list itself, it is going to be a collaborative effort to survey the entire web development stack in a wide, professional and helpful manner, so that anybody would be able to choose the right solution based on our research. Basically it should be a fair representation of the current state of affairs.</p><h3>How is it going to work?</h3><p>I decided to split the stack into different categories. Each will require additional research in order to portray it more precisely, but I still managed to characterize them well enough for an overview perspective. The categories (and subcategories) are as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mjdp_dqCexRv518TFfR7EQ.png" /></figure><p><em>Edit: I replaced the textual format with this descriptive infographic</em></p><p>If the tone of the article didn’t give it away already, each category will receive its own article at some point in the future. The <em>List of all List</em> is a series I intend on up-keeping an extending as time goes on.</p><blockquote>Another disclaimer: As previously stated, the prioritization is based on my work agenda, so the categories covered will be ordered accordingly.</blockquote><h3>How do you decide which technology to include?</h3><p>I have based my research on several key principles, technologies should abide by to qualify for my list (partially, not all are required):</p><ul><li><strong>Popularity</strong> — How wide is their usage right now?</li><li><strong>Relevancy </strong>— How many modern stacks apply them?</li><li><strong>Features </strong>— Do they have many useful features? Do they have any additional value?</li><li><strong>Availability </strong>— Do they support our stack choices? Are they free? If not are they worth it? Are they easy enough to use?</li><li><strong>Hype </strong>— Yes I admit to being guilty with this one</li></ul><p>Consequently, many technologies have not found themselves on the <em>List of all Lists</em>. Not, because they don’t deserve it, but because at the time of writing I haven’t deemed them essential enough. Maybe I was wrong, so I wholeheartedly encourage you to correct me!</p><h3>So what do you have so far?</h3><p>I have a full-stack map of all the categories mentioned above. Here it is (feel free to comment and help me improve the <em>List of all Lists</em> in any way you can):</p><p><a href="https://docs.google.com/spreadsheets/d/14DOQggJ1UDxtjZfWfQ4MILVlvh0-Lfnh7PZPEz36HTE/edit?usp=sharing">Modern Full-Stack (Node.js + React)</a></p><h3>What can I do while I wait for the next article in the series?</h3><p>It will take some time until your comments are processed and evaluated as the next article in the series (see what I did there?). In the meantime, why don’t you read about the upcoming changes in ES2018?</p><p><a href="https://medium.com/jay-son/happy-new-es2018-b7bc37d8c1a3">Happy New ES2018!</a></p><p>You can also read the highly popular “Web Developer Roadmap — 2018” by Kamran Ahmed:</p><p><a href="https://github.com/kamranahmedse/developer-roadmap">GitHub - nilbuild/developer-roadmap: Interactive roadmaps, guides and other educational content to help developers grow in their careers.</a></p><p>Your cooperation is very appreciated. I can’t stress it enough! I am just one man in the infinite bowels of accumulated research, so the only way to create a collaborative full-stack <em>List of all Lists</em> is to collaborate on it. Thanks in advance! 😄</p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time artist. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a356fd0802f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/the-full-stack-list-of-all-lists-overview-6a356fd0802f">The full stack list of all lists: Overview</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Happy New ES2018!]]></title>
            <link>https://medium.com/jay-son/happy-new-es2018-b7bc37d8c1a3?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7bc37d8c1a3</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Sat, 03 Feb 2018 08:25:58 GMT</pubDate>
            <atom:updated>2018-02-13T11:17:43.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZgYg0pkAcHG8Pu7yFUESA.jpeg" /></figure><p>About a week ago, TC39 (ECMA International’s technical committee, responsible for standardizing the ECMAScript language specification) finalized the list of features, which will officially enter ECMAScript 2018. Exciting right? Well, it’s hard to say, since we have no idea what to be excited about yet. So let’s find out, what do they have in store for us!</p><h3>Rest/Spread Properties</h3><p>Let’s open with a bang! Arrays are no longer the cool kid in the block, objects are! That’s right, the feature everyone thought was already a part of ES6, since it is supported practically out of the box by everything, including Webpack, TypeScript, Chrome 60 and more, is finally becoming a built-in capability within ES2018. Intuitive as it is, for some reason it wasn’t included in ES6 (or any following edition of the spec for that matter). Okay, enough mumbling let’s see how it works:</p><h4>The rest operator</h4><pre>const eminem = {firstName: &quot;Marshall&quot;, lastName: &quot;Mathers&quot;, albums: 9, rapGod: true};<br>const {firstName, lastName, ...rest} = eminem;</pre><p>let’s log <em>firstName</em>, <em>lastName </em>and <em>rest </em>now:</p><pre>console.log(firstName); // Marshall<br>console.log(lastName); // Mathers<br>console.log(rest); // {albums: 9, rapGod: true}</pre><p>Easy, right?</p><h4>The spread operator</h4><p>This one is a handy one. I feel bad for <strong>Object.assign</strong> (just kidding, I don’t) as the spread operator allows you to assign object properties to another object very easily:</p><pre>const insect = {ugly: true, annoying: true};<br>const mosquito = {name: &quot;mosquito&quot;, ...insect, friends: Infinity};</pre><pre>console.log(mosquito); // {name: &quot;mosquito&quot;, ugly: true, annoying: true, friends: Infinity}</pre><blockquote>Note: All of you <strong>JSON.stringify</strong> and <strong>JSON.parse</strong> people beware, the spread operator can be used as a cloning mechanism for <strong>shallow clones</strong> <strong>only</strong>. Deep clones as well as true clones (including prototype) <strong>cannot </strong>be created using the spread operator!</blockquote><h3>Asynchronous iteration</h3><p>This is another big one. Asynchronous iterables and iterators are now a thing. Meaning your “<em>next”</em> calls will now return promises, eventually holding an object with the following structure:</p><pre>{value: &#39;next iterable value&#39;, done: false} // done is true when your iterator finishes cycling through the iterable and doesn&#39;t point to anything anymore, i.e: value is undefined</pre><p>This is not very easy to understand, so stick with me and I’ll try my best to explain it as clearly as possible using an example.</p><p>Let’s say you are a big shot developer with a tight schedule and for some reason you decided to create your own calendar, so you can mark your appointments. Now let’s assume you have an async iterable holding your appointments dates, how would you extract them? Here is a suggestion using ES2018:</p><pre>const appointmentsIterator = appointments[Symbol.asyncIterator]();<br>appointmentsIterator.next().then(appointment1 =&gt; {<br>    console.log(appointment1); // { value: &#39;11/02/18 11:00:00&#39;, done: false }<br>    return appointmentsIterator.next();<br>})<br>.then(appointment2 =&gt; {<br>    console.log(appointment2); // { value: &#39;12/02/18 15:00:00&#39;, done: false }<br>    return appointmentsIterator.next();<br>})<br>.then(appointment3 =&gt; {<br>    console.log(appointment3); // { value: undefined, done: true }<br>});</pre><p>Cool cool cool… a million lines of code and promises to get some appointments. Just COOL!</p><p>Well you can stay chill, since your next “<em>next</em>”<em> </em>calls (I’m sorry) will be much simpler if you make them inside an async function. Behold:</p><pre>async function printCalendar(appointments) {<br>    const appointmentsIterator = appointments[Symbol.asyncIterator]();<br>    console.log(await asyncIterator.next()); // { value: &#39;11/02/18 11:00:00&#39;, done: false }<br>    console.log(await asyncIterator.next()); // { value: &#39;12/02/18 15:00:00&#39;, done: false }<br>    console.log(await asyncIterator.next()); // { value: undefined, done: true }<br>}</pre><p>If you weren’t mesmerized yet, check out the following:</p><pre>async function printCalendar(appointments) {<br>    for await (const appointment of appointments) {<br>        console.log(appointment);<br>    }<br>}<br>// Prints:<br>// 11/02/18 11:00:00<br>// 12/02/18 15:00:00</pre><p>David Copperfield has got nothing on that magic ✨</p><h3>Promise.prototype.finally()</h3><p>Finally, The Rock has come back to… sorry wrong finally. But finally promises will have the <em>finally </em>function, which means that whether they succeed or fail, they will always enter the finally call and execute the provided callback.</p><p>Let’s see it in action:</p><pre>logOut()<br>    .then(() =&gt; { // promise fulfilled<br>        console.log(&quot;Logged out successfully&quot;);<br>    }).catch(err =&gt; { // promise rejected<br>        console.error(&quot;Failed to log out. Details: &quot;, err);<br>    }).finally(() =&gt; { // never mind what happened before, this is going to be executed<br>        closeModal();<br>    });</pre><p>I hope we will see even more promise functionality implemented natively in the future (I’m looking at you <strong>Promise.try</strong> and <strong>Promise.allSettled 👀</strong>).</p><h3>Template literal revision</h3><p>In my opinion the major additions to the spec were already covered by now. It’s not to say that the rest isn’t important, just not as game changing as the previous entries of this list. Starting with the “Template Literal Revision”, which is not a feature per say, more like a limitation drop.</p><p>First I need to explain what are <em>tag functions</em>. A <em>tag function</em> is essentially a function name followed by a template literal for an instant application of the function with an object parameter holding the template literal itself. Let’s look at one:</p><pre>function printFunc(str) {<br>    console.log(str);<br>}</pre><pre>printFunc`It is soccer, not football!`<br>// {0: &quot;It is soccer, not football!&quot;, raw: [&quot;It is soccer, not football!&quot;]}</pre><p>Now I hear you asking:</p><blockquote>Why would I need an object wrapper for my template literal?</blockquote><p>I assure you it is a great question. The answer is a bit underwhelming though. So basically this object wrapper is the essence of the tag function. It is comprised of both the <em>cooked </em>and the <em>raw </em>versions of the string. I am smelling the upcoming question in the air so let’s answer it right away.</p><p>A <strong><em>cooked </em></strong>string is a string with the escape sequences within it being interpreted, whilst a <strong><em>raw</em> </strong>string treats them as regular text. Looking back at our <em>printFunc</em> function, we can clearly see and understand its structure now.</p><blockquote>So where is the problem?</blockquote><p>As always it lies with the edge cases. Up until now, if you would have used a tag function with a bad escape sequence, you would receive a nasty syntax error. As it is not yet very clear what is considered bad, let’s try the following:</p><pre>/* GOOD */<br>printFunct`\u{3A}`<br>// {0: &quot;:&quot;, raw: [&quot;\u3a&quot;]}</pre><pre>/* BAD */<br>printFunc`C:\urawesome\somefile`<br>// SyntaxError: malformed Unicode character escape sequence</pre><p>I really think they should have seen it coming, back when template literals were added in ES6. Because now the solution is basically taking a step backwards and removing all syntactic restrictions. In plain english code it means:</p><pre>printFunc`C:\urawesome\somefile`<br>// {0: undefined, raw: &quot;C:\urawesome\somefile&quot;}</pre><p>No more escape wars, no more syntax errors, just plain <em>undefined </em>flying all over the place. It is certainly better, but not perfect imho.</p><h3>Regex Features</h3><p>Regex is not my cup of tea, which is why I don’t want to elaborate too much and confuse you with my misunderstandings. What I can say though, is that 4 regex related features were added to ES2018, so all of you keyboard smashing fanatics who love unreadable regex ABC mashes, may enjoy an easier life very soon.</p><h3>Further read</h3><p>I hope my article was clear enough for you to understand what is coming in the near future. If you would like to learn more about ES2018, I would highly suggest going straight to the source:</p><p><a href="http://2ality.com/2017/02/ecmascript-2018.html">ECMAScript 2018: the final feature set</a></p><p>I have to admit I was a little disappointed with the absence of some highly requested features such as fields, private members and more, but it is easily fixable in future spec editions. As for ES2018, I’m very excited about the first 3 features I covered. Can’t wait to use them. What about you? What are your thoughts on ES2018? Please share them with me in the comments below! 😃</p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time artist. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7bc37d8c1a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/happy-new-es2018-b7bc37d8c1a3">Happy New ES2018!</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[{“bestRookiePublication”: “Jay Son”}]]></title>
            <link>https://medium.com/jay-son/bestrookiepublication-jay-son-ba975b469329?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba975b469329</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[web-devlopment]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Sun, 31 Dec 2017 16:27:44 GMT</pubDate>
            <atom:updated>2017-12-31T16:27:44.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGWUU4XJu_ANKvvw3a0Mag.png" /></figure><p>Yes, 2017 was our debut year! And while our comical puns may arguably still need some work, we tried our best to deliver the utmost value through our development related content.</p><p>So I guess there is no better time for capping off our progress during our debut year, than right around the corner of 2018. Therefore let’s take a look at our content so far and mention some interesting developments (this is most certainly not ant intended word play 😥), that occurred since publishing it. Oh, and I will finish with some requests/resolutions/prophecies for the following year. Call them any way you want, they will happen. Or not…</p><h3><a href="https://medium.com/jay-son/how-to-land-a-job-in-oh-god-not-one-of-those-again-ca95b074408e">How to land a job in… Oh god, not one of those again</a></h3><p>It is a story, or a blog post if you will, which details my recent job hunting quest. And let me tell you something: I have 5 years of experience in the website development scene, but I sure wasn’t expecting this.</p><p>This post may have a practical effect on you or just entertain you. Either way, I really tried to make it a relatable piece and I would like to hear your feedback. Who knows, maybe it will turn into a series: <strong><em>“High-tech and the valley”</em></strong> or something of the sorts.</p><h4>The post</h4><p><a href="https://medium.com/jay-son/how-to-land-a-job-in-oh-god-not-one-of-those-again-ca95b074408e">How to land a job in… Oh god, not one of those again</a></p><h4>Related links</h4><p>Here is my minesweeper (game &amp; code):</p><ul><li><a href="https://yashag.github.io/minesweeper/">Minesweeper</a></li><li><a href="https://github.com/yashag/minesweeper">yashag/minesweeper</a></li></ul><h3><a href="https://medium.com/jay-son/too-mainstream-for-climbing-stairs-i-rather-stairjump-6eb792d975e0">Too mainstream for climbing stairs. I rather StairJump</a></h3><p>2 of my very talented friends released an amazing arcade game, so I decided to give you an exclusive preview of the final product. I’m extremely proud of them and I’m happy that the fruits of their labor are receiving such high praise and traction allover. A week barely passed, yet it has already experienced a few interesting developments:</p><ol><li>The game was released! 🎉</li><li>It reached all parts of the world (Russia, China, France and the list goes on). Seriously, check YouTube, you’ll find various streams and videos of people joining the hype.</li><li>A patch was released with multiple game improvements.</li></ol><p>4. More and more mentions of the game pop out everywhere. Use <strong>#StairJump </strong>to see for yourself!</p><p>Want to here the most absurd part of it all? I recently caught myself stair jumping in real life. Go figure.</p><h4>The post</h4><p><a href="https://medium.com/jay-son/too-mainstream-for-climbing-stairs-i-rather-stairjump-6eb792d975e0">Too mainstream for climbing stairs. I rather StairJump</a></p><h4>Related links</h4><p>Download “StairJump”:</p><ul><li><a href="https://play.google.com/store/apps/details?id=com.Stairjump.StairsJump">StairJump - Android Apps on Google Play</a></li><li><a href="https://itunes.apple.com/us/app/id1302926417">StairJump Game on the App Store</a></li></ul><p>The official “StairJump” website:</p><p><a href="http://stairjump.com/">StairJump Game</a></p><h3><a href="https://medium.com/jay-son/publish-like-there-is-no-tomorrow-e6ee0e136864">Publish like there is no tomorrow!</a></h3><p>Truth be told, at the moment of writing that article, I was publishing like there is no tomorrow. I just had a huge amount of ideas to share with the node.js community. So much so that my hyperactive genes kicked in and channeled all the sugar inside my body into NPM packages. I’m glad they did and I’m glad I took the time to share it with the Medium community as well.</p><p>Eventually it paid off as I got my first GitHub 🌟. Hopefully I’ll have more time in the near future to improve upon my creations so far. So keep the starts raining!</p><h4>The post</h4><p><a href="https://medium.com/jay-son/publish-like-there-is-no-tomorrow-e6ee0e136864">Publish like there is no tomorrow!</a></p><h4>Related links</h4><p>My NPM packages:</p><ul><li><a href="https://www.npmjs.com/package/texting">texting</a></li><li><a href="https://www.npmjs.com/package/constring">constring</a></li><li><a href="https://www.npmjs.com/package/jsdoctor">jsdoctor</a></li><li><a href="https://www.npmjs.com/package/semita">semita</a></li></ul><h3><a href="https://medium.com/jay-son/node-package-master-548169e70171">Node Package Master</a></h3><p>As far as I’m concerned NPM could also stand for “Node Paradise Maze“, or something similar (you can extend this acronym in any way you’d like and it would still make sense for some reason). The node.js packages ecosystem is amazing, yet also amazingly hard to master, so I felt the urge to share my knowledge and and provide helpful tips. It was my first article and my proudest achievement in Medium so far.</p><p>I poured my heart and soul into this one, so I would greatly appreciate your feedback. You can read it here (and yeah, I know that the developing stack is fastly chagning. I tracked some minor changes already and I intend on posting a suitable update later on).</p><h4>The post</h4><p><a href="https://medium.com/jay-son/node-package-master-548169e70171">Node Package Master</a></p><h3>Fun facts</h3><ul><li>The original title of this yearly review was: “Say Jon? Have you heard about Jay Son? No, Jayson what is it? A new publication! You Jon say!”, but the cringe factor was <strong>way </strong>too high.</li><li>As of right now, my StairJump high score is <strong>376</strong>.</li><li>Even though Medium gives me the option to add 140 characters subtitles to my articles, there is no actual place, where they are fully displayed. So I decided to share them here:</li></ul><p>From my <strong><em>{“bestRookiePublication”: “Jay Son”}</em></strong> post (the one you are reading now):</p><blockquote>Too many fitting Confucius quotes to insert here. So let’s just go with mine: “Jay Son in 2017 — great. Jay Son in 2018 — even better!”</blockquote><p>From my <strong><em>How to land a job in… Oh god, not one of those again </em></strong>blog post (I’ll let you figure out the pun here by yourself. For the time being…):</p><blockquote>This is a story of a boy, who went on searching jobs and fill a void, and while he did not expect a thing… Spoiler: he took a swing</blockquote><p>From my <strong><em>Too mainstream for climbing stairs. I rather StairJump </em></strong>article (nothing special here):</p><blockquote>The next big mobile game? Maybe. One thing is certain. It is a lot of fun!</blockquote><p>From my <strong><em>Publish like there is no tomorrow! </em></strong>article:</p><blockquote>It’s your lucky day. Cool npm packages just found you. 50% of the work is done!</blockquote><p>Last but not lease, from my <strong><em>Node Package Master </em></strong>article (this is actually the only one that is fully displayed):</p><blockquote>How to build the ultimate package! I kid you not, it is ultimate!</blockquote><h3>2018</h3><p>2017 was quite a fruitful year for me and for the <a href="https://medium.com/jay-son">Jay Son</a> publication, but this is just the beginning! 2018 is going to be even better! And not because I quote every other person during the holidays. I have actual proof. By the end of the next month, I am leaving my very demanding job (and I mean very demanding. I literally wasn’t at home most of the calendar year. But more on that later). Besides I got the chance to explore my love for Medium and the community in a more active role this time around so my confidence grew accordingly. Which means, you can expect a lot more from us in the future. Starting with:</p><p><strong>Having more writers!</strong> I am dead serious about this one. If you are interested in sharing your expertise in any programming related matter, feel free to contact to me and publish under the <a href="https://medium.com/jay-son">Jay Son</a> brand. I would gladly have you here.</p><p>As promised, I covered resolutions and requests. The only thing left is a prophecy, so here it is (I serve as the <strong>Oracle of Delphi </strong>as my side job. Just don’t quote me, that’s all):</p><blockquote>2018 is the year we finally breakout and go viral!</blockquote><p>Feel free to help us in realizing my spur of enlightenment.</p><p>As always, I appreciate your feedback and support! And I wish you the best year one could possibly have! Happy Jay Son Year guys! (God knows why I couldn’t do it like a normal person).</p><p>Let’s try this again 😉, <strong>Happy New Year! </strong>🎊</p><p><strong>(С новым годом! 🎄 🎁)</strong></p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time artist. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba975b469329" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/bestrookiepublication-jay-son-ba975b469329">{“bestRookiePublication”: “Jay Son”}</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</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 land a job in… Oh god, not one of those again]]></title>
            <link>https://medium.com/jay-son/how-to-land-a-job-in-oh-god-not-one-of-those-again-ca95b074408e?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca95b074408e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 19:23:44 GMT</pubDate>
            <atom:updated>2017-12-31T16:14:19.974Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v_0kyzuV4ZVFhhhOohEc1g.jpeg" /></figure><p>So recently, I have been job searching for the first time (as a full-stack web developer) and I certainly wasn’t expecting reality. It didn’t blow up in my face, but I learned that expectations and eventual outcome have nothing in common, when it comes to the job market. So if you see posts/tutorials/articles that claim to hold all the answers, you can calmly make peace with the fact that it’s a flat lie.</p><p>I decided to do things differently and tell you about my process. No unnecessary exclamations, just a story (with some necessary exclamations 😌). Hopefully, it will be more helpful than an article titled “How to land a 1000000$ job in 3 easy steps!”. Let’s dive in.</p><p><em>Disclaimer: I won’t disclose the names of the companies or the people in question as they are not the primary point of this article (or in our case a blog post would be more accurate. As I told you, it is a story).</em></p><h3>My target job</h3><p>First, I had to define my target job. Sounds easy right? Well it actually was, I don’t know why added the suspension pause there. Guess it was for insuring you will take it seriously, even though it is probably the easiest part of it all.</p><p>In my case, I wanted a senior full-stack node.js and React position within a startup. Defining my goals helped me in filtering unfit positions as well as almost fitting ones. What do I mean by that? Simple, if I saw a job posting for a full-stack Angular developer, I dismissed it momentarily. If I wouldn’t have been picky, I would be attending job interviews until it’s 2020 and I have neither the time nor the will for that.</p><h3>CV</h3><p>So I went a little overboard here. And by little, I mean a lot. Here is how it went down:</p><p>Google Images&gt; Search “CV Templates” &gt; <em>“Wow, cool, can I design something so extravagant myself? Challenge Accepted!”</em> &gt; 2 days later: <em>“Was ctrl+c, ctrl+v that hard to do?”</em> &gt; <em>“Well OK, my CV is too unique not to send it now, so let’s get the party started!”</em></p><p>I should also note that I sent my CV to my more experienced friends first, so I could receive their feedback and correct it. It may seem like a <em>while(true)</em> loop, but it is actually a <em>while(noneOfMyFriendsAreApproving)</em> loop. Eventually it ends and you end up with a great CV you are proud of. I was proud of mine.</p><h3>Headhunters</h3><p>A side note about headhunters. It’s your choice of course to approach them (I know they are approaching you, since LinkedIn is an easy platform to take advantage of in that sense). Most of them are actually great people, who can offer legitimate assistance, <strong>but</strong>:</p><ol><li>A friend told me his company is valuing candidates sent by headhunters lower than their “self-suggested” contemporaries, hence they offer them a lower salary.</li><li>Some headhunters tend to overwhelm and burden you with unreasonable amount of positions you are not really interested in, just because they have an established partnership with the places, which offer them. Remember the goal defining part? Swimming in a sea of jobs is so much worse than it sounds.</li></ol><p>So I am currently headhunting myself, but you are free to be hunted by others 😉.</p><h3>Interviews</h3><p>As I have mentioned above, headhunting was not an option I used. So how did I find potential jobs? Through friends, LinkedIn and Facebook. Surprisingly Facebook turned out to be even better than LinkedIn in my case (more on that later), but it is a very specific case, so feel free to use both platforms 😃</p><h3>Before the interviews</h3><p>Google search “node.js interview questions”, “React interview questions”, “web development interview questions” or whatever fits the position you are looking for. Thank me later.</p><p>On a more serious note, Those searches are extremely helpful, not only because they provide you with potential interview questions, but because they help in strengthening you core theoretical knowledge and even more importantly, your self esteem. Those are super important for any good developer.</p><p>In addition, I recommend collecting information about your potential employers beforehand. I googled mine and learned anything I could find about them. How long do they exist? How much money have they gathered? What stage is their product currently at? And so forth. It helped me show interest and ask more relevant questions during the interview itself, as well as be informed about their financial situation.</p><h3>During the interview</h3><p>Remember I just told you to learn more about the technologies you claim to be an expert in? Well forget that. My first interview was the only one which tackled my knowledge. And it wasn’t even that thorough.</p><p>The reason is startups usually search for candidates with a good algorithm in their brain rather than candidates with a large DB (wow it’s my geekiest analogy so far). Therefore, they prefer logical questions intended on showcasing your thinking process as well as getting to know you personally in order to establish how you fit the team.</p><p>I wasn’t ready for it. I thought I had it all figured out after reading 200 interview questions, but then I found myself reaching into the depths of my brain, trying to solve some tech-logic riddle.</p><p>All in all, it went pretty good. I didn’t let my sense of bafflement get the better of me. But I was caught a little bit off guard during my later interviews as well, because I couldn’t comprehend the fact that every interview is similar. No one was interested in my npm packages. They just wanted me to sort their binary trees. And that is the essence of it.</p><h3>More of the unexpected</h3><p>Expected or not, I have to admit, I enjoyed those interviews very much. I love solving quizzes as well as getting involved in business matters. But then, every company I applied to, added something different to the mix, resulting in me going through 4 very different application processes. Let’s present them chronologically:</p><p>1. The first company asked me to make a React minesweeper game as an examination task. They told me it should take me about 2–3 hours. Needless to say it was way more. More like 2–3 days. So why did I comply, even though there is a general rule of thumb not to agree to long home assignments? Because I wanted to master React in a fun way, so I thought of it as a great opportunity to do so. I also wanted the job, so I guess it also had something to do with it ;)</p><p>I forgot to mention that this was in addition to a technical interview where I met the CEO and the CTO, 2 incredibly talented guys, who I can learn a lot from. So I decided it was my turn to impress them. And I wasn’t disappointed as a few days later the CEO drove all the way to my place, so we could have the most open discussion on my future within the company. I really appreciated the gesture.</p><p>2. The second company invited me to an additional round of interviews. Besides the HR interview, the second round was the same as the first. Just more of those logical questions. By the way, I think this is a good place to mention it:</p><blockquote>Please have hobbies! It’s for your own sake!</blockquote><p>3. I’m very glad I went to this interview, because it was absolutely horrible. A 3 man company with their only developer being an unpleasant CTO. He was taking jabs at me at every opportunity he got and the whole damn thing felt like an overly opinionated trial. So yes, I’m glad I went there and I’m glad it was the first interview I failed. This place didn’t deserve me and it’s not arrogance speaking, it’s realism. I’m not going to be slammed with the statement:</p><blockquote>“A good developer doesn’t create bugs and then fixes them. I search for developers, who never create bugs in the first place”</blockquote><p>and think nothing of it. Especially if it comes as a response for me suggesting “css grids” as a new solution for layout design in web pages (and yes I know they are not supported yet in every browser, but it wasn’t the topic at the time). Of course I exercised patience during the interview, but there was so much I wanted to say. Anyway I’m glad I didn’t and I’m glad it is over.</p><p>4. This one I was definitely not expecting. More precisely, I wasn’t expecting anything coming into this interview. I found this small startup on Facebook and decided to contact them, for job security purposes (as an insurance, if I failed everywhere else). Then I met their CEO and WOW! My mind was blown!</p><p>Just to make it clear, we didn’t even conduct the technical interview. We just set for an hour and a half and analyzed the market and our society. It was a learning experience I will never forget. I received so many explicit and implicit tips, it felt way more like a mentor-ship program than a candidate selection process. Which is why I decided to terminate my process there. I knew I wasn’t ready yet. I had so much to learn and the following years will serve as my stepping stone. Hopefully I’ll get another opportunity along the way to work with this particular individual, but this time, on a more equal footing. Right now, I just thank him with all my heart for illuminating my path for me. Yeah, who could have imagined this could happen in a technical interview.</p><h3>After the interview (a.k.a The contract)</h3><p>If everything went well up to this point, you should be getting a contract. Read it thoroughly, have experienced friends in the industry who got screwed over before and have a lawyer mother. Those are my recommendations. Or just read it carefully and do your best to make sure it doesn’t come to bite you in the future. Either way, you can’t protect yourself from everything, so there is nothing else to do here, other than gain experience with time.</p><h3>Results</h3><p>I have made my choice, but I’ll keep it for future articles. I mean blog posts. As for this one, here is the outcome:</p><ul><li>I have made a minesweeper. Seriously here it is, feel free to play:</li></ul><ul><li><a href="https://yashag.github.io/minesweeper/">Minesweeper</a></li><li><a href="https://github.com/yashag/minesweeper">yashag/minesweeper</a></li></ul><ul><li>I learned a lot of theoretical material and I feel like a more developed developer (come on, I had to make this pun. But I mean it!).</li><li>I exercised my brain a lot through logical quizzes and had a lot of fun, while doing it. I absolutely recommend all of you to attend technical interviews for fun (I know I sound crazy).</li><li>I learned a lot from a business stand point, which is something I’m very intrigued in.</li><li>I met incredible people and I intend on maximizing and capitalizing on my newfound opportunities.</li><li>I greatly boosted my confidence.</li></ul><p>Overall, I call my job hunting process a huge success. Hopefully it will go the same way for you too!</p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time artist. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca95b074408e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/how-to-land-a-job-in-oh-god-not-one-of-those-again-ca95b074408e">How to land a job in… Oh god, not one of those again</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Too mainstream for climbing stairs. I rather StairJump]]></title>
            <link>https://medium.com/jay-son/too-mainstream-for-climbing-stairs-i-rather-stairjump-6eb792d975e0?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6eb792d975e0</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Fri, 22 Dec 2017 15:45:11 GMT</pubDate>
            <atom:updated>2017-12-23T08:24:38.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h7hzcCz19Jj15MBZujLBDQ.jpeg" /><figcaption>StairJump</figcaption></figure><p>Unfortunately, I haven’t had the chance to write for a while now. Fortunately though, I come back bearing some good news and some good content.</p><p><strong>Have you ever heard of <em>StairJump</em>?</strong> It would be quite strange if you had answered “yes”, as it is a rhetorical question. <em>StairJump</em> wasn’t released yet. So what is it? Only one of the best mobile games I have ever played! Don’t believe me? Check it out for yourself:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2yCLsn-gwPA%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2yCLsn-gwPA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2yCLsn-gwPA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/5757d34e20cca3884b83ad05f08fe85d/href">https://medium.com/media/5757d34e20cca3884b83ad05f08fe85d/href</a></iframe><p><strong>Why should you care?</strong> Because it releases tomorrow and you get the chance to play it right away. Just imagine playing “Flappy Bird”, before it was so popular. Or playing “Doodle Jump” before it was cool. Besides you get to experience an amazing game for absolutely free!!!</p><p>You are also welcome to check <a href="http://stairjump.com/">http://stairjump.com/</a> for more details:</p><p><a href="http://stairjump.com/">StairJump Game</a></p><p>⚠️ Now I have to make a disclaimer:</p><blockquote><strong>Rom Haviv</strong> and <strong>Tom Bogin</strong>, the people behind <strong>SunFury</strong> and the development of <strong>StairJump</strong>, are 2 of my best friends.</blockquote><p>Then is me promoting <em>StairJump</em> considered favoritism or some form of nepotism? Hell no. This game is great by any standard and I recommend it purely out of strong belief in it. I am truly addicted to it after playing for hours straight and I can definitely see it blowing up in popularity. I just happen to know the people behind the game and in my honest opinion, it is a huge plus. You can count on them to provide great content and a very fun experience.</p><p>I also have a great explanation as to why this article is published under the <a href="https://medium.com/jay-son">Jay Son</a> publication. It is very simple actually: <strong>it is a great product of development so it most certainly fits a development publication</strong>. As a bonus, I want to hear your thoughts about it. If there will be enough interest, who knows? Maybe <a href="https://medium.com/jay-son">Jay Son</a> will feature a development manifesto of sorts, detailing exactly how <em>SunFury</em> created <em>StairJump</em>.</p><p>So what are you waiting for? 🎊 GET HYPED 🎊 December 23rd, it is going live! Trust me, you will actually fall in love with stair jumping 😍</p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time artist. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6eb792d975e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/too-mainstream-for-climbing-stairs-i-rather-stairjump-6eb792d975e0">Too mainstream for climbing stairs. I rather StairJump</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Publish like there is no tomorrow!]]></title>
            <link>https://medium.com/jay-son/publish-like-there-is-no-tomorrow-e6ee0e136864?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6ee0e136864</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Wed, 11 Oct 2017 07:06:32 GMT</pubDate>
            <atom:updated>2017-12-31T16:16:34.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AjTpuT869H_kNu7rHI25Uw.png" /></figure><p>Did you come here in search of new and cool npm packages, which may change your workflow? If the answer is <strong>yes</strong>, then you came to the right place. If the answer is <strong>no</strong>, then I present to you cool npm packages, which may change your workflow, even though you were not looking for them.</p><h3>Short intro</h3><p>Recently I published my first article under my newly founded publication: <a href="https://medium.com/jay-son">Jay Son</a>. It has the ultimate node.js package guide as well as some backstory to tie everything together. I recommend you to check it out, since it contains some insight on our topic today. In any case, here is a link:</p><p><a href="https://medium.com/jay-son/node-package-master-548169e70171">Node Package Master</a></p><p>Now on to our topic for today. I decided that instead of posting here and there, one line summaries of my public npm career so far, I should use this opportunity to give you a broader review of each package. So here it goes:</p><h3>The review</h3><p>I decided to cover my created packages in a chronological order based on time of creation. Hence, we will start with <em>texting</em>:</p><h4><a href="https://www.npmjs.com/package/texting">texting</a></h4><p>I have to admit that creating <em>texting</em> was a decision made out of pure frustration. I was a actually working on <em>jsdoctor</em> (which I will cover later) and I couldn’t find a decent package for multiple strings manipulation as I needed. The only package I did find that somehow gave me my coveted result, made me jump through a lot of illogical hoops, so I gave up on it pretty fast.</p><p>As for <em>texting</em>, I would describe it in the following manner: it is a package for joining an array of strings with many addition options. For instance, let’s say you want to pretty print the shopping list your wife gave you. You could do it in the following way:</p><pre>texting([&quot;steaks&quot;, &quot;apples&quot;, &quot;rice&quot;], {<br>    blockStart: &#39;My shopping list: &#39;,<br>    lineStart: &#39;&gt; &#39;,<br>    lineEnd: &#39;.&#39;,<br>    blockEnd: &#39;---------&#39;<br>});</pre><p>Here is the result:</p><pre>My shopping list:<br>&gt; steaks.<br>&gt; apples.<br>&gt; rice.<br>---------</pre><p>Pretty handy, right? If you think so, you are welcome to check it out here:</p><p><a href="https://www.npmjs.com/package/texting">texting</a></p><h4><a href="https://www.npmjs.com/package/constring">constring</a></h4><p>This one right here is a tricky one. Either you will be the number one fan of it or its biggest opposition. The reason being the sole idea of this package is to replace one/two character strings with a variable, just to prevent string pollution in your code. Though to be fair, the idea is actually to replace any eligible string constant, regardless of length, purely out of aesthetic reasons.</p><p>Here is one way the package allows you to do so:</p><pre>const { ONE, DOLLAR, EXCLAMATION } <strong>=</strong> require(&#39;constring&#39;);<br>console.log(&#39;It will cost you: &#39;, ONE + DOLLAR + EXCLAMATION);</pre><p>You probably guessed it already, but here is the result:</p><pre>It will cost you: 1$!</pre><p>I truly believe that often, strings stand out and make our code less readable. It is not a huge problem, but a very solvable one , if you are using <em>constring</em> :)</p><p>If you think so too, you are welcome to check it out here:</p><p><a href="https://www.npmjs.com/package/constring">constring</a></p><h4><a href="https://www.npmjs.com/package/jsdoctor">jsdoctor</a></h4><p>This one is my baby, the one which pushed me to create the first two packages. It also pushed me to the limits of sanity as lexical code analysis is a fascinating world, but also a very complex one.</p><p>The idea of creating <em>jsdoctor</em> originated from my co-workers complaining that in JavaScript, you can’t keep track of how certain objects and variables look like. In their words:</p><blockquote>“You don’t know what you get”</blockquote><p>When I suggested jsdoc, they claimed that the upkeep is too much of a hassle. While personally I disagree, I decided that maybe a more cost-effective solution is an order. The direction was clear, a tool for generating jsdoc comments on the fly.</p><p>Unfortunately, it is easier said and done. Type inference is a very difficult task in JavaScript, as it has certain limitations in that department. And rightfully so. JavaScript was not intended to be a strongly typed language.</p><p>The other problem is I can’t read people’s minds, so as far as descriptions go, I can only generate some hard-coded ones from pre-made templates.</p><p>With all that being said, I enjoyed parsing my way through code, “deciphering” it and creating a well deserved solid result. While <em>JSDoctor</em> is still not this mind reading documentation tool, it saves a lot of work already. It creates pretty nice templates based on read code and inferred information and I really recommend using it. See for yourself:</p><pre><em>/**<br>* @param {*} a<br>* @param {number} b<br>* @param {boolean} opposite<br>* @returns {*}<br>* @throws {Error} The first argument wasn&#39;t provided<br>*/</em><br>function diff(a, b <strong>=</strong> 1, opposite <strong>=</strong> false) {<br>    <strong>if</strong> (<strong>!</strong>a) <strong>throw</strong> <strong>new</strong> Error(&quot;The first argument wasn&#39;t provided&quot;);<br>    <strong>if</strong> (opposite) <strong>return</strong> b <strong>-</strong> a;<br>    <strong>return</strong> a <strong>-</strong> b;<br>}</pre><p>It was all auto-generated. If you like what you see and want to try it out or you’d like to learn more about <em>JSDoctor</em>, check it out here:</p><p><a href="https://www.npmjs.com/package/jsdoctor">jsdoctor</a></p><h4><a href="https://www.npmjs.com/package/semita">semita</a></h4><p>Unrelated to the previous packages I developed, I decided to go for visual data representation. The long-term goal was to create some analysis tools for node.js applications. But a diagram to showcase data seemed like a valid starting point. Thus a hierarchical data visualization package called <em>semita</em>, was born.</p><p>Using <em>semita</em> is very easy. All you have to do is provide it a json object with some specific keys. The result however, is something else entirely. Let’s take a look:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rv67k0XLzCxQ0bhzQilPkg.png" /><figcaption>semita</figcaption></figure><p>You can think of it this ways: there is an easy option to beautify hierarchical data now (you would be surprised how rare it is). If it is something you are interested in, check it out in the link below:</p><p><a href="https://www.npmjs.com/package/semita">semita</a></p><h3>In conclusion</h3><p>I had lot’s of fun creating those packages and I am very excited to learn what the future holds, for them and for me both 😃. if you still didn’t have the experience of creating any packages or publishing them on npm, I highly suggest you fix it as soon as possible. I also want to remind you to check my previous article about node.js packages creation, as it may further your knowledge and help you down the line (the link is in the intro). Until next time!</p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time artist. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6ee0e136864" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/publish-like-there-is-no-tomorrow-e6ee0e136864">Publish like there is no tomorrow!</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node Package Master]]></title>
            <link>https://medium.com/jay-son/node-package-master-548169e70171?source=rss-d67138a60cd2------2</link>
            <guid isPermaLink="false">https://medium.com/p/548169e70171</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[nodejs]]></category>
            <dc:creator><![CDATA[Yasha Gootkin]]></dc:creator>
            <pubDate>Sun, 08 Oct 2017 12:39:51 GMT</pubDate>
            <atom:updated>2017-12-31T16:18:50.637Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*ZL0hrfDvxH8ZpmQ1FqI0Jg.jpeg" /></figure><p>After this awful programming pun in the title hopefully caught your eye, I’m happy to explain, what this article is actually going to consist of: an ultimate node.js package development guide (trust me, it is ultimate) and my personal experience in the field. Let’s start with the latter (if you are not a fan of backstories or gathering arguments to convince your boss, you may very well skip ahead).</p><h3><strong>My personal experience</strong></h3><p>I have been working with node.js for the best part of the last 3 years and I have to admit that at the beginning, I had no idea I would end up all over the place. From basic REST API server development to various DB queries, swagger API implementations, WCF communication and a lot more things one could not predict to be working on, when asked to develop a node.js application. And don’t get me wrong, I loved it!</p><p>But all of us have been on this roller coaster ride sometime during our development cycle. When you are done with your feature, you are the happiest person on earth and you tend to forget that a mere two minutes ago, you were smashing the keyboard and wondering if the computer is considering today April’s Fool’s Day and it is just messing with you.</p><p>This is where node.js packages come into play. A much shorter roller coaster ride with the benefits of reusability, sharing and more moments of satisfaction. For instance, let’s say I was asked to implement a button for viewing a shopping cart content and supposedly it would take me 5 days to do so. I would have to create the button, make it send a request to the server upon pressing, query the DB, return the results and present them in a tasteful way. But wouldn’t it be better if I were to work for 8 days, and besides my requested feature, I would also create a DB querying package and a response parsing package for my company? That way, Bob, my colleague would thank me for shortening his feature development cycle and I would get triple the satisfaction for creating 3 products instead of 1.</p><p>I apologize if the last part sounded a little like a sales pitch, I’m sure most of you were already sold on the idea of packages. But I can’t stress enough the importance of insisting on developing them and convincing your boss it is the right thing to do. Investing a little more time now can save you and others much more time later.</p><p>Quickly grasping this concept, I began developing private packages for my workplace and sharing them with everybody. My colleagues did the same and needless to say, it was a huge success, because it saved a lot of dirty work for the whole company. It also improved our professionalism as it served as a stepping stone for introducing new technologies and methods, such as unit testing, linting, coverages and many more. It was the perfect platform for minor improvements. At some point I even had the privilege of developing a yeoman package generator specifically for our needs (which by the way I recommend to every development team to do).</p><p>But after doing so for two years, I have began questioning the idea of creating packages solely for ourselves. We were using so many public packages, from the npm ecosystem, but when we couldn’t find anything that would satisfy our needs, we developed something outside this ecosystem, even though it could help others in our position.</p><p>I decided it was time for me to step outside my comfort zone and create some packages for the public to use (unrelated to my daily work). At first it was fun creating them, but later it became fun looking at the downloads statistics (even if they were low, they still meant that someone, human or robot, was downloading my work). Feel free to take a peek yourself:</p><ul><li><a href="https://www.npmjs.com/package/jsdoctor">JSDoctor</a> — A smart jsdoc documentation generator.</li><li><a href="https://www.npmjs.com/package/texting">texting</a> — Add additional styles to a block of text</li><li><a href="https://www.npmjs.com/package/constring">constring</a> — Utility string constants</li><li><a href="https://www.npmjs.com/package/semita">semita</a> — A visual hierarchy representation tool</li></ul><p>Now, you’ll notice that some of the stuff I was and will be referring to is not implemented in those packages and this is where the most important takeaway from this section shines (somewhat borrowed from the LEAN startup methodologies):</p><blockquote><strong>Release your package as soon as its core functionality is done and build upon it in future releases!</strong></blockquote><p>Trust me, it’s the right way to go about it. Not because there are no alternatives, but because there would be less chances of you dropping out as a result of frustration, there would be more downloads for your package (each version adds downloads) and most importantly you would have more time to receive feedback and pivot accordingly. The most important features for the public are not necessarily what you envisioned, which is why it is a good idea to wait and hear their requests first.</p><p>With all of that in mind, I’d like to proceed to the guide itself (hopefully you will find somethings useful for yourself in there).</p><h3>Ultimate Package guide</h3><p>In this section I’ll address a lot of the aspects you should consider, when developing a node.js package. Keep in mind this is not gospel truth. The subsections below are merely advice and recommendations for your development experience. Feel free to incorporate your own techniques, methods and style into your development process. I would also gladly hear about it in the comments.</p><p><em>Note: I haven’t done 100% of the recommendations bellow. Besides my own experience, I have based this guide on heavy research I have done. And even though I intentionally shared imperfect projects on npm, with the intent to improve them over time, I learned new things, which I’ll prioritize over what I had in mind so far and hopefully include them in future releases. I encourage you to do the same: read more, learn more and gradually expand your knowledge and abilities. No shame in not knowing absolutely everything all the time.</em></p><h4>package.json</h4><p>Requirement: must.</p><p>According to the official <a href="https://docs.npmjs.com/files/package.json">npm docs</a> (which also contain more details about the package.json structure):</p><blockquote>This document is all you need to know about what’s required in your package.json file.</blockquote><p>Basically, <em>package.json</em> is a file, which describes the current state of your node.js application/project: Basic info. How to use it? What are the usage conditions and requirements? Where to look for additional information? And so on and so forth.</p><p>I’ll address here the less obvious parts:</p><ul><li><strong>version</strong> (must)— consists of 3 numbers, i.e. <em>“1.2.3</em>” in the format of <em>“major.minor.patch”</em>. Usually starts at <em>“1.0.0”</em>, but oftentimes versions below that are published in order to demonstrate development on the way to the initial <em>“1.0.0”</em> mark. The format is intended to show the level of change each version brings with it. <em>“patch”</em> is for minor bugfixes and changes. <em>“minor” </em>is for new features and changes that don’t break existing code. Lastly, “major” is for big features and changes, which are not backwards compatible and institute adaptations in order to upgrade to them. Please follow these rules when versioning, as they are a considered common convention. I also recommend using the following command in your terminal to perform the versioning:</li></ul><pre>npm version {patch/minor/major}</pre><ul><li><strong>bin </strong>(optional)— Contains paths to binary scripts within your project. Mainly for exposing a cli interface for running your module.</li><li><strong>scripts</strong> (optional) — An object, which contains scripts for performing certain command line actions. The key is the name of the script and the value is the script itself. For instance: <em>“test”: “mocha --reporter spec”</em>. Once you have written your scripts you can run them by typing in your terminal:</li></ul><pre>npm run {script name}</pre><ul><li><strong>main </strong>(must) — The entry point for your module. Whatever you export from that file is what will be required upon using the <em>require </em>keyword with your module name. Usually it is the <em>index.js</em> file, but in some occasions, you might want to export something else (like a dist file).</li><li><strong>bugs </strong>(optional) — A url/mail address for reporting bugs.</li><li><strong>keywords </strong>(optional) — An array of words, which best describe your project and help people in finding it.</li><li><strong>dependencies </strong>(optional) — An object with the key-value pairing of a module you are using and its version. While the <strong>dependencies</strong> object is used for modules you need for your package’s functionality to work, <strong>devDependencies</strong> object is used for modules required for your development process solely. Other dependency types also exist.</li><li><strong>license </strong>(must) — The license you are using for releasing your open-source code. The most common one is <em>“MIT”</em> as it allows full sharing and usage by the community without special strings attached (I am not a lawyer, so I recommend reading it yourself and not taking my word for it).</li><li><strong>engines </strong>(optional) — Similar to the dependencies object, only here you specify the node/npm versions needed to install and run your package.</li></ul><p>For further reading, I recommend the following link:</p><p><a href="http://browsenpm.org/package.json">package.json: an interactive guide - browsenpm.org</a></p><h4>README.md</h4><p>Requirement: must.</p><p>In my book, a README file is a must. After all it describes why and how users can use your product to their benefit. Without it, most developers may be lost and may decide to give up on your node.js package. You might lose lots of potential users and they may lose a potentially great package. In order to avoid all that, you should write a clear and descriptive README file, which would help everyone get started. It should contain:</p><ul><li><strong>Description </strong>— A short one line description.</li><li><strong>Description </strong>— If necessary, a longer, more detailed description, in addition to the shorter one.</li><li><strong>Why </strong>— A statement explaining, why people should use it.</li><li><strong>Install </strong>— <em>“How to install”</em> section.</li><li><strong>Usage </strong>— “<em>How to use</em>” section (both programmatically and using the terminal if such an option exists).</li><li><strong>API </strong>— Detail here the different functions and options that your package exposes. Make sure you clearly explain their behavior, default values, accepted parameters, return values, aliases, etc. It may be a deciding factor in people’s choice of which package to use.</li><li><strong>Examples </strong>— Give usage examples through code excerpts, so it will be clear how exactly it is intended to be used.</li><li><strong>TODO </strong>— You may want to share future development plans. It is completely up to you.</li><li><strong>Credits </strong>— If your project is heavily based on another package it is considered a common courtesy to thank them. Also some licences require the users of the packages they are attached to, to do so.</li><li><strong>License</strong>— Talking about licenses, it is always a good idea to attach your license in your README file.</li><li><strong>Tags</strong> — You can add tags to your README file if you believe they hold a substantial value for your users (like amount of downloads or state of dependencies).</li><li>There are many other sections you may want to include, like “About”, “Features Summary” and more. I’ll leave it up to your judgement.</li></ul><p>On that note, I would like to emphasize the importance of updating you README file every time you make changes with implications your users should be notified about. I know it can be a drag, but it says a lot about your level of professionalism and can be of great significance.</p><h4>CHANGELOG.md</h4><p>Requirement: recommended.</p><p>I always recommend adding a CHANGELOG file as it is a great way for you and your users to keep track of the changes that occur in your package. Sometimes those changes can’t be reflected in the README, sometimes you forget about making the change and sometimes your users and potential contributors want to explore your package development even further. Either way, A CHANGELOG file is a great way to address all those issues.</p><p>In general it should contain each version as a title and under it every change as a bullet. Additional info like commit links and contributors credit is also welcome. You are free to check how I’ve done my CHANGELOG files in my projects (links in the beginning of the article).</p><h4>CONTRIBUTING.md</h4><p>Requirement: optional.</p><p>While there is no absolute need to write a CONTRIBUTING file or a contribution section in your README, it becomes a recommendation if you are working on a big project and/or aim to involve other contributors along the way.</p><p>I have to warn you, this is not an easy file to write. If you want to cover all your bases, you have to address a lot of different aspects. The upsides are, your project will remain organized, it will look professional and will help in avoiding uncomfortable issues in the future. Also once you write one, there is a lot of copy pasting 😄.</p><p>I’d like to give a shout out here to <a href="https://www.npmjs.com/package/generate-contributing">generate-contributing</a> for helping me get started with writing my CONTRIBUTING file. It is very recommended as a basis for your version.</p><p>So as promised, here is a list of things you can mention in your CONTRIBUTING file:</p><ul><li>A “thank you” paragraph to everyone who takes their time to contribute. Imho it is very important and shows you value any help.</li><li>A paragraph talking about the authenticity of the submitted content.</li><li>Detailed outline of the different forms of contribution.</li><li>Issues submission and treatment.</li><li>Feature requests format.</li><li>Pull requests submission, prerequisites and other related notes. May refer to tests, styleguides, documentation, work with git, etc.</li><li>Helpful references, i.e. forums, docs and code which may help in deciding whether to contribute and how to do so.</li><li>Other conditions, requests and guidelines you want your contributors to follow.</li></ul><h4>Code of Conduct</h4><p>Requirement: optional.</p><p>Some projects also include a <em>Code of Conduct</em> file. While it is not an absolute must, the idea is quite nice actually. This file is mainly comprised of definitions of acceptable and unacceptable behavior within the community, as well as the view of the project’s maintainers and applicable enforcement.</p><p>While I haven’t written one of those myself, I came across several. I also found a package called <a href="https://www.npmjs.com/package/conduct">conduct</a>, which may prove useful in writing such a file.</p><h4>LICENSE</h4><p>Requirement: recommended.</p><p>This file should contain the text of the license you are publishing your code under (as mentioned in the <em>package.json</em> section of this article). My advice, generate it with GitHub’s help, when creating a new repository (it’s a built in functionality you can’t miss).</p><h4>Ignores</h4><p>Requirement: must.</p><p>As with the README, in my book this is a must. There are files you use for development only or you don’t want people to download because they don’t contribute to your package’s functionality in any way. Once you have a file like that, and trust me, you have, you should create an ignore file to prevent uploading it. The most common ignore files in our case are:</p><ol><li><strong>.gitignore </strong>— In here you would like to mention auto-generated reports, IDE generated files and any other file you would not like to see pushed into your repository.</li><li><strong>.npmignore</strong> — Whatever is ignored here won’t be uploaded to npm. I assume you would want here everything ignored by the <em>.gitignore</em> file with several additions, such as the tests directory, README exclusive assets and so on. Basically you want to keep everything development related in your repository, but outside of npm.</li></ol><p>I should mention here that upon creating a new repository, GitHub helps you in generating a default <em>.gitignore</em> file as well.</p><h4>.editorconfig</h4><p>Requirement: recommended.</p><p>This is something I sinfully haven’t used in one of my public projects yet, thought I very much plan on doing so in the near future. This file aims at maintaining consistency of coding style across the different editors and IDEs. The main pitfalls here are whitespace and encoding, which can dramatically influence development if diverse applications are submitted. I mean it in a negative sense. For future reference, you may want to look at this example:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c0e18ae15b086db0e266ec4f578eb677/href">https://medium.com/media/c0e18ae15b086db0e266ec4f578eb677/href</a></iframe><h4>Project structure</h4><p>Requirement: must.</p><p>Once again, the importance of this topic is heavily based on my own interpretation, but it is not unfounded. The directories and files structure is one of the most confusing subjects out there, so hopefully the following recommendations will help straighten it out:</p><ul><li><strong>index.js</strong> — There are some exceptions, but in most cases this should be the entry point of your package. It should be inside your <strong>root</strong> directory.</li><li><strong>All previously discussed files</strong> — All the files we examined above are supposed to be inside your <strong>root</strong> directory as well.</li><li><strong>configurations </strong>— Most of your added tools will require extra configuration files (we will touch on that later). Your package might also require its own too. Commonly those configurations are also placed within your <strong>root</strong> directory, but if you feel like their amount is pilling up, it is quite okay to setup a <strong>config</strong> directory instead.</li><li><strong>assets</strong> — Often, you will have additional content you need your project to contain: images, audio files, videos and so forth. I usually create a separate folder for them and call it <strong>assets</strong>. It is also widespread to see a naming convention, such as “misc” or “media”, but I like “assets” more, because I feel it is less restricting and because Visual Studio Code recognizes it as a different type of directory. Once I have my “assets” directory set up, I create sub-directories for the specific assets I have: <strong>images</strong>, <strong>audio</strong>, <strong>video</strong>…</li><li><strong>docs</strong> — This one is similar to the assets directory, only it stores documentation. Once I have my <strong>docs </strong>folder setup, I create specific content oriented sub-directories here as well. For example: <strong>tutorials</strong>, <strong>about</strong>, <strong>guides</strong>…</li><li><strong>Code directories</strong> — Here is the juicy part. I have longly followed my own convictions in the matter only to stumble a few days ago onto an amazing project’s structure anatomical breakdown article. I implore you to read it and live by it: <a href="https://gist.github.com/tracker1/59f2c13044315f88bee9">https://gist.github.com/tracker1/59f2c13044315f88bee9</a></li></ul><p>The funny thing is, I wasn’t far of base.</p><h4>Unit Tests</h4><p>We have finally reached the part of the guide, where we talk about external tools. And what better subject to start with, other than testing?</p><p>There are many testing frameworks out there, so feel free to choose whatever you like. As a reference I’ll even throw a great comparison article in here:</p><p><a href="https://raygun.com/blog/javascript-unit-testing-frameworks/">JavaScript unit testing frameworks in 2020: A comparison</a></p><p>Personally, I prefer <a href="https://www.npmjs.com/package/mocha"><strong>mocha</strong></a> over the rest of them. It’s lightweight, easy to configure, unrestricting and very popular. I have had a blast with it. As an assertion mechanism I use <a href="https://www.npmjs.com/package/chai"><strong>chai</strong></a><strong> </strong>and chai plugins if I have a specific need. I also use <a href="https://www.npmjs.com/package/sinon"><strong>sinon</strong></a><strong> </strong>for stubbing and <a href="https://www.npmjs.com/package/supertest"><strong>supertest</strong></a> for API tests. Once again those are my preferences at the time of writing, yours might be different, which is completely fine.</p><p>As unit tests development goes, I encourage you to write tests for your package’s functionality as soon as possible. TDD is a great way to go about it, but it isn’t easy and demands quite a lot of conviction and execution quality. The important part is the code you upload should be tested, so you’ll know that the core functionality is working and nothing was broken by you or your collaborators.</p><p>At this point, I feel the need to insert a serious advice/joke: Whatever you choose, be it TDD, BDD or something else, <strong>don’t do RDD</strong> (Resume Driven Development), unless you absolutely hate your colleagues!</p><h4>Unit Tests Report</h4><p>Now, here is where unit tests falter in my opinion. While it was fun writing them, it was hard to comprehend the results, as they felt as if they were all over the place. I have to admit that Webstorm does a pretty good job at exposing a dedicated interface to unit tests, but I still feel like it isn’t enough. If several tests were failing I had to hop and jump between the interface and different files and it always felt like an exhausting investigation. And maybe it’s just me and my affinity towards beautiful and clear html reports, but those are my impressions.</p><p>Enter <a href="https://www.npmjs.com/package/mochawesome"><strong>mochawesome</strong></a>. A beautiful and slick html report, which is a joy to look at and share with your colleagues. Don’t take my word for it, go check it out for yourselves, I think you’ll reach the same conclusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5d4GMvRl8pJMnARKhTd7Hg.png" /><figcaption>Mochawesome is really awesome!</figcaption></figure><h4>Coverage</h4><p>This right here is the lost brother of unit tests. Coverage allows you to check, which parts of your code are untested, what are the specific cases that you haven’t covered yet and your current state of coverage in statistical format. The most popular coverage tool is <a href="https://www.npmjs.com/package/istanbul"><strong>istanbul</strong></a> and it is very understandable why:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*m-IUVsKbORspk0g-YCX6oA.png" /><figcaption>Istanbul</figcaption></figure><p>An additional tool you might be interested in checking out is called <a href="https://coveralls.io/"><strong>coveralls</strong></a>. It has many coverage statistical features for your repository, so give it a look.</p><h4>CI</h4><p>Continuous integration and continuous deployment are something you definitely should consider. It acts both as an assurance of tested code submissions and as a stronger testing infrastructure for your codebase. In other words you can sleep at night with a CI setup.</p><p>While admittedly, I haven’t done CI outside of my workplace, yet, after a tedious (in a good sense) research, I am certain that <a href="https://travis-ci.org/"><strong>Travis CI</strong></a> is the way to go. It is great in terms of popularity, presentability, comfort, etc. So I’m on team “Travis” now.</p><p><strong>Linting</strong></p><p>There are actually quite a lot of linting packages in npm, you would be surprised. Still, like in any other ecosystem, there are top dogs. You can read about them in here and see the comparison for yourself:</p><p><a href="https://www.sitepoint.com/comparison-javascript-linting-tools/">A Comparison of JavaScript Linting Tools - SitePoint</a></p><p>I guess it makes my choice very obvious, but was there any doubt to begin with? <a href="https://eslint.org/"><strong>Eslint</strong></a> it is! It is very easy to use, greatly customizable and it has a built in html reporter. Life could not be any better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BWbPLpqvKJxlNqEaytdzpg.png" /><figcaption>Eslint</figcaption></figure><p><strong>Code Quality</strong></p><p>During my research, I have stumbled onto this article:</p><p><a href="https://medium.com/london-nodejs/useful-tools-for-your-node-js-projects-20fd1f7c860a">Useful tools for your Node.js projects</a></p><p>While it is a great read from beginning to end, the part that caught my eye the most was about code quality. More specifically it mentioned <a href="https://codeclimate.com/"><strong>Code Climate</strong></a><strong> </strong>and <a href="https://www.codacy.com/"><strong>Codacy</strong></a> as somewhat of an analytical superset to linting and code analysis in general. I have to admit that after reading their websites I wasn’t sold on their necessity and added value, but they are free for open-source, so why not check them out for yourselves?</p><h4>Documentation</h4><p>We previously discussed documentation in the form of a README file or the docs folder, but this time I am referring to code documentation, which should be helpful to other contributors in your repository.</p><p>There are several ways to go about it:</p><ul><li><strong>jsdoc comments </strong>— I believe that this is a great way to add additional data to your code. Whether it is types, examples or descriptions, jsdoc comments allow you to add documentation, without actually affecting your code and in my opinion it is a great documentation option. It is also widely supported by IDEs so I consider it an additional plus.</li><li><strong>flow </strong>— compatible with the previous point, <a href="https://flow.org/"><strong>flow</strong></a> adds the power of types to JavaScript. Nothing else! This is a huge compliment by the way. Though it adds a compilation layer to your development, the overhead isn’t big and you should definitely consider it.</li><li><strong>TypeScript</strong> — I use <a href="https://www.typescriptlang.org/"><strong>TypeScript</strong></a><strong> </strong>at work and even in a personal project of mine so what I am about to say is not baseless: I am not a fan of TypeScript! I won’t elaborate too much (this guide is super detailed as it is so I’ll leave this topic for another article), but I’ll just say this: People are losing their head over TypeScript and their code remains as bad as it was with JavaScript, only this time with horribly written interfaces. If you are a solid developer you will write great code in TypeScript as well as in JavaScript. And the other way around. But it is a very common choice, so no judging on my part.</li></ul><p>It might be clear already, but I usually go with jsdoc comments. Ironically, a whole section could be written on different jsdoc tools / generators alone. So I’ll leave it to this article to sum up:</p><p><a href="https://www.fusioncharts.com/blog/jsdoc-vs-yuidoc-vs-doxx-vs-docco-choosing-a-javascript-documentation-generator/">Choosing a JavaScript Documentation Generator - JSDoc vs YUIDoc vs Doxx vs Docco</a></p><p>As for my choice, unsurprisingly it’s <a href="https://www.npmjs.com/package/jsdoc"><strong>JSDoc</strong></a>. You might have noticed a pattern already, so it is as good time as any to come clean. I like customizable and extendable products a lot. Even if they have other flaws, they are very open for correction and from my perspective is great. I thought I should mention it for objectivity purposes.</p><p>Lastly there is the theming issue. The output of JSDoc is pretty ugly and thankfully you can tweek it with themes. Here are some better ones I found:</p><ul><li><a href="https://www.npmjs.com/package/namis">namis</a></li><li><a href="https://github.com/smeijer/latodoc">smeijer/latodoc</a></li><li><a href="https://www.npmjs.com/package/toast-jsdoc">toast-jsdoc</a></li><li><a href="https://www.npmjs.com/package/loke-jsdoc-theme">loke-jsdoc-theme</a></li></ul><p>Out of those I only used the <em>loke</em> theme, yet I have to admit I am still a bit underwhelmed. I am searching for a better theme to use so I’ll gladly hear any suggestions you’ve got.</p><p>Another documentation option I just recently discovered is <a href="http://docs.raneto.com/"><strong>Raneto</strong></a>. It is a markdown based platform for sharing documentation. It might be of use to you, so check it out!</p><p>One thing I beg you not to do is: <strong>Don’t auto generate your README from comments or do anything of the sort!</strong> Sometimes lazy is good. This is not the case!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*6sfes-gvH4J3FrQA34xr2A.png" /><figcaption>Loke JSDoc theme</figcaption></figure><h4>Task Runners</h4><p>If this topic seems like a deviation to you, than trust me, it is not. There are amazing things you can do with task runners in package development, like generating reports, cleaning them, exposing a documentation server and so on. But since it is a hefty topic in itself, I’ll leave it to this article (which greatly stresses out the main differences and some of the strong suits of each runner):</p><p><a href="http://jpsierens.com/task-runners-a-comparison-between-grunt-gulp-broccoli-and-mimosa/">Task Runners, A comparison between Grunt, Gulp, Broccoli and Mimosa - Javascript Jedi Padawan</a></p><p>Predictably, I adore <a href="https://gulpjs.com/"><strong>gulp</strong></a> and choose it over every other task runner. I know the article didn’t refer to <a href="https://webpack.js.org/"><strong>Webpack</strong></a> and <a href="http://browserify.org/"><strong>Browserify</strong></a><strong> </strong>as they are bundlers and not task runners, but it is still a no-brainer for me. In my opinion mystical configuration files is not something that should be considered as positive development or any development for that matter. And gulp is an amazing tool for absolutely every task you want to accomplish.</p><h4>Yeoman</h4><p>If there is one section that could be considered a deviation it is this one, but I still have to talk about it.</p><p>If you or your team write a lot of private packages, do yourself a favor and create a custom <a href="http://yeoman.io/"><strong>Yeoman</strong></a> generator. Not only is it fun and a great experience, but everyone will thank you and claim it is the coolest time conserving tool they have ever seen.</p><h3>Summary</h3><p>It has been a long article, but I tried to deliver the “ultimate” package guide as I promised. Hopefully you found it useful. I would gladly hear any suggestions and comments you have, so feel free to share. Also, every clap, recommendation and social network share is appreciated. Thank you!</p><blockquote><a href="https://medium.com/jay-son">Jay Son</a>! Get it? Comical development mind at its best. If you like our content, be sure to 👏 clap, 📱 share and 👣 <a href="https://medium.com/jay-son">follow us</a>! Thank you!</blockquote><blockquote>Yasha Gootkin is a full-fledged developer, a part-time entrepreneur and part-time musician. Feel free to follow him on <a href="https://www.facebook.com/yasha.gootkin">Facebook</a> or connect with him on <a href="https://www.linkedin.com/in/yasha-gootkin-41b446148/">LinkedIn</a>!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=548169e70171" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jay-son/node-package-master-548169e70171">Node Package Master</a> was originally published in <a href="https://medium.com/jay-son">Jay Son</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>