<?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 Mitch Kosowski on Medium]]></title>
        <description><![CDATA[Stories by Mitch Kosowski on Medium]]></description>
        <link>https://medium.com/@mitchkosowski?source=rss-9ac47f80fbd4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ewWZzJncDCTqSHmszLnLCw.png</url>
            <title>Stories by Mitch Kosowski on Medium</title>
            <link>https://medium.com/@mitchkosowski?source=rss-9ac47f80fbd4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:17:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mitchkosowski/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[Announcing the ECF Web 3.0 Infrastructure Fund]]></title>
            <link>https://medium.com/ecf-review/announcing-the-ecf-web-3-0-infrastructure-fund-cbe1d2d1c071?source=rss-9ac47f80fbd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbe1d2d1c071</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Mitch Kosowski]]></dc:creator>
            <pubDate>Sat, 08 Sep 2018 10:15:01 GMT</pubDate>
            <atom:updated>2018-09-08T10:15:01.589Z</atom:updated>
            <content:encoded><![CDATA[<p>The Ethereum Community Fund is proud to announce the <strong>ECF Web 3.0 Infrastructure Fund</strong>! This fund will deploy 10,000 Dai (equivalent to $10,000 USD) monthly for 6 months to fund GitHub issues on popular Web 3.0 repos that do not have more established funding. This is a mechanism to speed up development in existing projects in Web 3.0, and to bring new developers into the fold.</p><p>The Gitcoin platform is a perfect fit for this initiative as it has an active development community eager to use their skills on great projects in the space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*zUi_l8UwWlAP1E1G2IFFHw.gif" /><figcaption>The <a href="https://gitcoin.co/explorer">Gitcoin Issue Explorer</a> enables developers to find issues that match their skillset</figcaption></figure><p>This fund came about after a successful run of a <a href="https://medium.com/ecf-review/announcing-the-ecf-web-3-0-infrastructure-fund-pilot-program-ab8894af35fa">pilot program</a>. A quick post mortem for this study:</p><ul><li>5,000 Dai was deployed across 24 GitHub issues in 6 repos: <a href="https://github.com/exthereum">exthereum</a>, <a href="https://github.com/ethereumjs/">EthereumJS</a>, <a href="https://github.com/XLNT/gnarly">gnarly</a>, <a href="https://github.com/duaraghav8/Solium">Solium</a>, <a href="https://github.com/WalletConnect">WalletConnect</a>, <a href="https://github.com/walleth">WALLETH</a>, and <a href="https://github.com/web3j">web3j</a></li><li>The average funding per issue was 208 DAI (equivalent to $208 USD)</li><li>At the time of this writing, 13 of these issues have been completed, 8 have been started, and the remaining 3 are still open (take a look <a href="https://github.com/XLNT/gnarly/issues/8">here</a>, <a href="https://github.com/exthereum/ethereumex/issues/25">here</a>, and <a href="https://github.com/walleth/walleth/issues/143">here</a> if you’d like to participate!)</li><li>Of the issues that were completed, 16 days was the average completion time</li><li>11 (!) new developers were onboarded and completed issues for repos that were new to them. This was great to see, really awesome to bring new blood to great projects 👍</li></ul><p>The pilot program was a success but did not go off entirely without a hitch. Gas prices spiked during the study and there were a few hiccups in the processing of Gitcoin bounties, which both led to a few delays in paying out of some bounties.</p><p>The good news is that gas prices have returned to a more sane level and also that the team has worked hard to streamline the processing of bounties so we expect these delays to be greatly minimized going forward.</p><h4>Are you a repo maintainer interested in applying to this fund?</h4><p>To apply, please submit your Github issues your project could use help with using the <a href="http://gitcoin.co/requests">Gitcoin Requests feature</a>, being sure to include ‘ECF’ in the comment.</p><p>Bonus points will go to repos that ensure they price bounties appropriately for the effort associated with the work (here’s a <a href="https://medium.com/gitcoin/tutorial-how-to-price-work-on-gitcoin-49bafcdd201e">guide on how to price these bounties</a>).</p><p>All repos within the Web 3.0 space are encouraged to apply, but special consideration will be given to those most actively used by the community that do not currently have more established funding. Happy developing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbe1d2d1c071" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ecf-review/announcing-the-ecf-web-3-0-infrastructure-fund-cbe1d2d1c071">Announcing the ECF Web 3.0 Infrastructure Fund</a> was originally published in <a href="https://medium.com/ecf-review">ECF’s Pensieve</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing the ECF Web 3.0 Infrastructure Fund Pilot Program]]></title>
            <link>https://medium.com/ecf-review/announcing-the-ecf-web-3-0-infrastructure-fund-pilot-program-ab8894af35fa?source=rss-9ac47f80fbd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab8894af35fa</guid>
            <category><![CDATA[ethereum-blockchain]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain-technology]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Mitch Kosowski]]></dc:creator>
            <pubDate>Wed, 13 Jun 2018 10:38:00 GMT</pubDate>
            <atom:updated>2018-06-13T10:38:00.355Z</atom:updated>
            <content:encoded><![CDATA[<h4>A partnership between ECF + Gitcoin to grow Web 3.0</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*Dcxo7sZ_qX1XQCv2iUArsA.jpeg" /></figure><p>The most overlooked yet perennially difficult part of any open-source software lifecycle is maintenance.</p><p>This is described in more colorful terms in the excellent <a href="https://medium.com/codezillas/a-bitter-guide-to-open-source-a8e3b6a3c1c4">A Bitter Guide To Open Source</a> — in case you haven’t yet come across the article, please take a moment to dig in. It does a great job of explaining in the best way possible, and important since we should all be more mindfully aware of the state of open-source.</p><p>The software maintenance issue holds true even still for the web3 ecosystem, where great new projects are started every day, yet existing projects that are popular in the community often don’t get the attention they deserve.</p><p>This should come as no surprise. Maintenance work of responding to the community, squashing new bugs, and building out requested features is a lot of hard work, and often a task that goes unnoticed.</p><p>In fact, when you think about it, it’s almost outrageous we’re not more aware of this issue and not encouraging devs to continue with maintenance tasks. So the <a href="https://ecf.network/">ECF</a> + <a href="https://gitcoin.co/">Gitcoin</a>, as a community, decided to help contribute in order to tackle this issue, together.</p><p><a href="http://gitcoin.co/">Grow Open Source: Get crowdfunding and find freelance developers for your software projects, paid in crypto</a></p><h3>The ECF + Gitcoin Pilot Study</h3><p>ECF + Gitcoin will conduct a pilot study to help address this issue through the ECF Web 3.0 Infrastructure Fund Pilot Program. 5,000 Dai (equivalent to $5,000 USD) has been allocated for Gitcoin bounties on Ethereum projects, specifically for GitHub maintenance issues appropriate for external contribution across the ecosystem.</p><p>This is a mechanism to speed up development in existing projects in web3, and bring new developers into the fold. The Gitcoin platform is a perfect fit for this initiative, as it has an active development community, with new bounties, on average, getting picked up in around 2 hours and completed in about 2 weeks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zUi_l8UwWlAP1E1G2IFFHw.gif" /><figcaption>The <a href="https://gitcoin.co/explorer">Gitcoin Issue Explorer</a> enables developers to find issues that match their skillset</figcaption></figure><p>This pilot study is intended to use incentives to tip the balance in the web3 community, from requesting new functionality on existing projects via <strong>feature requests,</strong> to delivering more functionality by valued contributors via <strong>pull requests</strong>. Here are some examples.</p><h4><strong>Examples of Successful Bounties</strong></h4><p>Some ideal GitHub issues to incentivize include well-documented:</p><ul><li><strong>Long-standing features requested by a large portion of the community</strong>. Some successful features funded via Gitcoin include <a href="https://gitcoin.co/issue/uport-project/sss-wasm/1/481">SSS-Wasm Project, uPort</a>, the <a href="https://gitcoin.co/issue/balance-io/balance-manager/195/553">Balance + Dharma Integration</a>, and the <a href="https://gitcoin.co/issue/AugurProject/augur/1472/335">Augur + TREZOR Integration</a>.</li><li><strong>Bugs of any and all kinds</strong>. Some great squashed bug examples can be found on <a href="https://gitcoin.co/issue/ethereum/solidity/3965/316">Ethereum’s Solidity repo</a>, <a href="https://gitcoin.co/issue/ethereum/sharding/80/436">Ethereum’s Sharding</a>, or <a href="https://gitcoin.co/issue/ethereum/cpp-ethereum/4981/444">CPP Ethereum</a>.</li><li><strong>Increasing test coverage of the project</strong> on <a href="https://gitcoin.co/issue/TimVanMourik/GiraffeTools/12/255">GiraffeTools</a> and <a href="https://gitcoin.co/issue/Bounties-Network/BountiesAPI/44/510">Bounties Network</a>.</li><li><strong>And finally, documentation, </strong>as shown on <a href="https://gitcoin.co/issue/ethereum/solidity/3764/344">Solidity</a> and <a href="https://gitcoin.co/issue/MetaMask/metamask-extension/4085/351">Metamask</a>.</li></ul><h4><strong>Are you a repo maintainer interested in being a part of this pilot study?</strong></h4><p>To apply, please <a href="https://goo.gl/forms/nYqawnOJu5kwRfMe2">submit your project here</a> with a link to your web3 repo, a short description of the project, and a few GitHub issues that you think would be good candidates to incentivize. Bonus points will go to repos that also include what they consider appropriate pricing for these issues (here’s a <a href="https://medium.com/gitcoin/tutorial-how-to-price-work-on-gitcoin-49bafcdd201e">guide on how to price these bounties</a>).</p><p>All repos within the web3 are encouraged to apply, but special consideration will be given to those most actively used by the community and do not currently have more established funding. This is an initial pilot study, and the results here will help determine further efforts in this area.</p><p><strong>If the pilot study is successful, ECF will allocate more funds to this program for further support.</strong> Good luck, we’ll be following closely ;)</p><h4>What about documentation?</h4><p>Ah, the big pink elephant in the room. We are also considering this, since it’s one of our most pressing needs. Stay tuned!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab8894af35fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ecf-review/announcing-the-ecf-web-3-0-infrastructure-fund-pilot-program-ab8894af35fa">Announcing the ECF Web 3.0 Infrastructure Fund Pilot Program</a> was originally published in <a href="https://medium.com/ecf-review">ECF’s Pensieve</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Video Games as Inspiration for UI/UX]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Now that I have a bit of UI/UX experience under my belt, it&#x2019;s really fun to go back and play video games I beat when I was younger to see&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@mitchkosowski/video-games-as-inspiration-for-ui-ux-c666506fd556?source=rss-9ac47f80fbd4------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@mitchkosowski/video-games-as-inspiration-for-ui-ux-c666506fd556?source=rss-9ac47f80fbd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c666506fd556</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Mitch Kosowski]]></dc:creator>
            <pubDate>Sun, 22 Apr 2018 16:51:17 GMT</pubDate>
            <atom:updated>2018-04-22T16:51:17.588Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Meeting of Mark Zuckerberg and 6 Humans]]></title>
            <link>https://medium.com/@mitchkosowski/a-meeting-of-mark-zuckerberg-and-6-humans-39d03b480dd7?source=rss-9ac47f80fbd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/39d03b480dd7</guid>
            <category><![CDATA[mark-zuckerberg]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[instagram]]></category>
            <category><![CDATA[zuckerberg]]></category>
            <category><![CDATA[whatsapp]]></category>
            <dc:creator><![CDATA[Mitch Kosowski]]></dc:creator>
            <pubDate>Wed, 28 Mar 2018 10:13:45 GMT</pubDate>
            <atom:updated>2018-03-28T10:13:45.151Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Scene opens with Zuckerberg’s face in extreme closeup. His face completely dominates the frame. Very important that Zuckerberg never blinks a la Hannibal Lecter! Zuckerberg is a menacing figure not because he has wild emotions but rather because he has none at all. He possesses a “flat affect”: monotonous voice, diminished facial expressions, and is apathetic.</em></p><p><strong>Zuckerberg</strong></p><p>I do not understand. All recent simulations that were run with the current protocol showed my universal likability numbers advancing, especially among females aged 18–49 years. But now it appears the numbers are going the wrong way. Why?</p><p><em>Scene shows a meeting room with Zuckerberg at the head of a white conference table that has a shiny gloss. There are 6 executives seated in black chairs at the table with Cheryl Sandberg to Zuckerberg’s right. The walls are full-length glass windows. The environment is sterile. There is no natural light.</em></p><p><em>Scene moves to extreme closeup of Mr. Anderson, executive to Zuckerberg’s left. He is a middle-aged man with thinning hair who looks extremely tired.</em></p><p><strong>Mr. Anderson</strong></p><p>Well, Mark, these things are a bit tough… there are a lot of moving parts. Public perception for visiting the Historic Black —</p><p><strong>Zuckerberg</strong></p><p>African American.</p><p><strong>Mr. Anderson</strong></p><p>Yes, of course, thank you. Public perception for visiting the Historic African American Church was generally positive although there was a bit of a rise in the cynicism numbers for certain demographics. There were some that questioned the true motives for this visit. But the real thorn in our side is still Cambridge Analytica. One approach we could consid —</p><p><strong>Zuckerberg</strong></p><p>I see. Cambridge Analytica is still a problem? And when we informed Them that They agreed to give us Their information and that it’s explained right there in the apps when They get started, did that mediate the situation?</p><p><strong>Mr. Anderson</strong></p><p>Unfortunately, Mark, that seems to have had the opposite effect. It looks like that protocol aggravated users with one focus group explaining that the users didn’t realize that they were giving up this info to Facebook in the first place and didn’t understand why Facebook needed it at all. But these things take time, and —</p><p><strong>Zuckerberg</strong></p><p>Time, Mr. Anderson, is unfortunately a resource that you are fresh out of.</p><p><em>Extreme close-up on Zuckerberg’s right hand. He snaps his fingers. Back to showing the conference room where two security officers briskly enter and grab Mr. Anderson under each arm.</em></p><p><strong>Mr. Anderson</strong></p><p>No, Mark, please! I’m begging you, I have a family! Mark, I have a family! Please! Mark, please! Please!!!</p><p><em>Mr. Anderson is carried outside of the room by the two security officers. After the door closes, there is 10 seconds of quiet punctuated by a few nervous coughs from the remaining executives. Finally, Cheryl Sandberg speaks.</em></p><p><strong>Cheryl Sandberg</strong></p><p>It’s a good thing you did that, Mark. A real good thing.</p><p><strong>Zuckerberg</strong></p><p>Thanks, Cheryl. Please run the usual statistics on the previous action and report back to me.</p><p><strong>Cheryl Sandberg</strong></p><p>Of course.</p><p><em>Zuckerberg stands up and begins staring outside the glass window of the conference room. The camera slowly pans behind him and it’s shown that through the glass window Zuckerberg is staring at a cement wall without any adornment.</em></p><p><strong>Zuckerberg</strong></p><p>I do not understand. I acquired a wife. I procured a child — two children. I’ve completed 13 outreach protocols and iterated on every one. And yet They persist in not accepting me as one of Their own…</p><p>No matter. The more of Their data I collect, the more I understand what it is to be human.</p><p>They will love me. I will make Them.</p><p><em>Camera shows view from outside of the conference room with Zuckerberg’s body in center of frame and executives seated flanking him. Executives are all looking at Zuckerberg. Zuckerberg is looking very slightly down as camera slowly zooms in on his face and </em><a href="https://www.youtube.com/watch?v=4Js-XbNj6Tk"><em>“For the Damaged Coda”</em></a><em> by Blonde Redhead begins to play. Zuckerberg does not blink. At 37 seconds in, Zuckerberg’s face is the entire frame and he looks up directly into the camera in time with the first music sting. Shot is held for 1 more second and then title screen is shown:</em></p><p><strong>Zuckerberg for President 2020</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39d03b480dd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Principles for Learning New Software Engineering Skills]]></title>
            <link>https://codeburst.io/3-principles-for-learning-new-software-engineering-skills-1342e751803e?source=rss-9ac47f80fbd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/1342e751803e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Mitch Kosowski]]></dc:creator>
            <pubDate>Thu, 11 Jan 2018 12:47:29 GMT</pubDate>
            <atom:updated>2018-01-15T14:07:09.143Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/edgar-mauricio-mojica-23688913/"><em>Edgar Mauricio Mojica</em></a><em> provided illustrations for this post. This is his </em><a href="https://www.thelastmojican.com/"><em>personal website</em></a><em>.</em></p><p>It’s January so lots of us out there are committing to New Year’s resolutions, and if you’re in software engineering that often means committing to learning new technical skills. 2018 may be the year you go after building your first web app in React, investigating a new programming language like Scala, or cementing your knowledge in data structures and algorithms (like me!).</p><p>Regardless of what skill(s) you’re trying to develop, it’s a sad fact that many of us will fall short of our learning goals. We’ll leave projects half-finished, only scratch the surface of learning a new language, or flat out not even start working on developing proficiencies in areas that could have a real positive impact on both our work and personal projects.</p><p>So what’s the fix? Simply put, I think software engineers could learn a lot from CrossFit. Yep, that CrossFit!</p><p>How does a fitness program have anything to do with learning skills in software engineering?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*5QsYHCLtC32QW2LZcbv5iQ.png" /></figure><p>In <a href="http://library.crossfit.com/free/pdf/CFJ_Widman_CFStartupGuide1.pdf">A CrossFit Startup Guide: Part 1</a>, it says, “The first and most important component of beginning CrossFit is to follow our charter of mechanics, consistency, and then intensity.” How are those defined and how could they relate to software engineering? In CrossFit,</p><blockquote>Mechanics refers to technique — your ability to move properly through our core movements.</blockquote><p>Just like weightlifting, there are <strong>Mechanics</strong> in software engineering like <a href="http://www.healthycomputing.com/office/setup/keyboard/">proper keyboard usage</a> and <a href="http://www.allaboutvision.com/cvs/irritated.htm">ways to avoid eye strain</a>. But in the field of software engineering, there are important things to keep track of beyond <strong>Mechanics</strong> that are often neglected like having a proper diet, getting enough exercise, and maintaining and nurturing relations with friends and family. Because of that I like to use the principle of <strong>Safety</strong> which includes these concepts and extends beyond just <strong>Mechanics</strong>. A proper sleep schedule would also be included in <strong>Safety</strong>.</p><p>Let’s talk about sleep for a moment. There are some people in software engineering who wear their lack of sleep like a badge of honor… it’s not! Lack of sleep is one of the least fun ways to <a href="https://www.theatlantic.com/health/archive/2013/12/how-sleep-deprivation-decays-the-mind-and-body/282395/">cause serious health consequences</a>. If your side projects are intruding on your sleep schedule, shuffle things around until they’re not. If your work is disrupting your sleep schedule for extended periods of time, I’d encourage you to update your resume and hit the job market. Your health is worth it!</p><p>With that lecture over (“And remember to eat your vegetables!”), what about <strong>Consistency</strong>?</p><blockquote>Consistency has a two-part application: 1) That you are consistent in performing the mechanics of the movement; and 2) That you are consistent in CrossFit workouts.</blockquote><p><strong>Consistency</strong> for our purposes means basically the same as it does for CrossFit: we consistently follow the principles of <strong>Safety</strong> and that we are consistent in our technical workouts. For me, I’ve found that hitting a subject 2–5 times a week is the sweet spot for my learning process. Less than that and I have difficulty retaining information and more than that I have difficulty processing new information. As for everything in life, finding the <strong>Consistency</strong> that works best for you is a matter of personal trial and error.</p><p>Finally, what about <strong>Intensity?</strong></p><blockquote>Intensity, as Coach Greg Glassman, founder and CEO of CrossFit, formally states, is the independent variable most commonly associated with the rate of return on favorable adaptation. More simply put, intensity brings about all the good results from working out.</blockquote><p>It might be strange to think of the concept of <strong>Intensity</strong> in developing software engineering skills so let me use a personal project to illustrate. I am currently working on developing my data structures and algorithms skills primarily by using a site called <a href="https://leetcode.com/">LeetCode</a>. LeetCode has a great body of questions to review as well as an online judge that runs your submitted code against test cases, which ensures that what you write actually works.</p><p>To stay on top of my studies, I maintain a personal GitHub repo with preferred solutions. But the intensity with which I practice data structures and algorithms might vary from day to day. Here’s a few different exercises in order of increasing intensity to demonstrate this:</p><ol><li>Reading new problems to get familiarity</li><li>Walking through my GitHub repo and quickly reviewing solutions to problems that I’ve already done</li><li>Solving problems that I’ve done before (Note: this is one of the lower intensity tasks but I’ve found this to be probably the most important for solidifying knowledge)</li><li>Comparing my solution to other solutions and using that info to add a new solution I like to my GitHub repo</li><li>Attempting new problems in a category that I am familiar with</li><li>Attempting new problems in areas that I’m not familiar with</li></ol><p>A workout could consist of one or any number of these depending on how intense I want to get on any given day. I’ve found <strong>Intensity</strong> to be an apt description for these exercises. If I try a whole bunch of new problems and give them my all, I am mentally drained afterwards and can’t really do more cognitive work for a bit of time. I’ve heard this described as only having so many mental “cycles” in a given day.</p><p>Alright, so those are the principles of <strong>Safety</strong>, <strong>Consistency</strong>, and <strong>Intensity</strong>. If you keep these in mind and stick to them you will achieve this beautiful Golden Pyramid!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*E7Wybb9GdXpHzIUtNwGdVw.png" /><figcaption>The Ideal: Safety, Consistency, and Intensity</figcaption></figure><p>This is the sweet spot of learning a skill in software engineering. We are safe so we’re learning in a way that is sustainable in the long-term. We are consistent so the knowledge that we gain throughout the process builds on itself. And we are intense so we can learn quickly and apply our new techniques right away. Awesome!</p><p>It’s important to note that these principles of <strong>Safety</strong>, <strong>Consistency</strong>, and <strong>Intensity</strong> build on each other and bad things happen if you are missing one or more. That’s why the <strong>Safety</strong> block is the biggest and rests on the bottom of the pyramid, followed by <strong>Consistency</strong>,<strong> </strong>and finally with <strong>Intensity</strong> on top. What happens when we don’t adhere to the principle of <strong>Safety</strong>?</p><h3><strong>Burnout</strong></h3><p>With just <strong>Consistency</strong> and <strong>Intensity </strong>we find ourselves in a situation that happens all too often in software engineering… An engineer is persistently attacking a problem with great energy, but finds they get eye strain from staring at their computer screen all day every day. Or they start foregoing exercise and sleep. Or they let their relationships suffer. This may work in the short-term but in the long-term it is a recipe for <strong>Burnout</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*xELtZR5kzT9dseQ52qbvbA.png" /><figcaption>The Pyramid of Burn Out: Consistency and Intensity without Safety</figcaption></figure><p>Without that bottom pyramid block providing stability, sooner or later it will all come crashing down. Without <strong>Safety</strong> you will be left burnt out from the whole process of trying to learn something new and may give up on the whole thing. Don’t fall into this trap! To ensure your learning is truly sustainable, make <strong>Safety</strong> a priority in learning technical skills. No matter what happens, always make time for your family, your friends, and yourself!</p><p>Now let’s say we do follow <strong>Safety </strong>and <strong>Intensity</strong> but forego <strong>Consistency</strong>. What’s the outcome?</p><h3>Frustration</h3><p>Let’s use an example of an engineer trying to work through <a href="https://www.educative.io/collection/5668639101419520/5649050225344512">Grokking the System Design Interview</a>. They’ve started a few times but keep getting sidetracked. Each time they sit down with the material, they find it’s been weeks since they’ve last looked through it and they need to basically start from scratch each time.</p><p>This engineer is learning in a sustainable way (and following <strong>Safety</strong>) and also vigorously studying when honing their skills (following <strong>Intensity</strong>). But even though they started the course a few months back they don’t have much accomplished. Without <strong>Consistency</strong> we will find ourselves with no results, just <strong>Frustration</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*qPhmS5cwtTl-uK9k7xZn5g.png" /><figcaption>The Pyramid of Frustration: Safety and Intensity without Consistency</figcaption></figure><p>Often times when starting a new project, there is a honeymoon period. You just can’t wait to go after learning a new skill and you make time for it every day. But after a while you hit a roadblock or something comes up in life that leads you to miss a day. One day turns to two and so on, until you pick it back up a few weeks later and can’t remember where you were.</p><p>What’s the best way to fight this? I like using scheduling with Google Calendar to remind myself to stay on top of things that I’m working on. <a href="https://www.amazon.com/Checklist-Manifesto-How-Things-Right/dp/0312430000/">Daily checklists</a> can also serve as helpful reminders to maintain <strong>Consistency</strong> in learning new skills. <strong>Consistency</strong> is crucial to cultivating skills so make sure to follow this principle and to set aside time in your schedule for developing your desired skill!</p><p>Finally, what happens when we have <strong>Safety</strong> and <strong>Consistency</strong> but lack <strong>Intensity</strong>?</p><h3>Slow Progress</h3><p>If we can’t devote a fair amount of <strong>Intensity</strong> to our studies, it will be hard to break new ground and learn new things. We can maintain our existing knowledge and add a new concept here and there but progress will be slow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*TouJjUfQMyo382zO94_uvw.png" /><figcaption>The Pyramid of Slow Progress: Safety and Consistency without Intensity</figcaption></figure><p><strong>Slow Progress</strong> is a bit different than <strong>Burnout</strong> or <strong>Frustration</strong>. <strong>Burnout</strong> and <strong>Frustration</strong> often lead to you stopping your personal development entirely (for those of you with a controls background, these are positive feedback loops leading to a change in state). Contrast that with <strong>Slow Progress</strong> that can be continued indefinitely.</p><p>So there is nothing necessarily wrong with <strong>Slow Progress</strong>, but you should be aware that if you added a bit of <strong>Intensity</strong> to the mix it could dramatically improve your results. But sometimes it’s fun to be working on something slowly over a longer period of time.</p><p>I’ll give a non-technical example from my personal life. I was fortunate enough to live in Korea for 6 months and focus entirely on learning Korean. I attended classes, read Korean, watched Korean TV, conversed with locals on the subway, and even made an effort to think only in Korean. This was very high <strong>Intensity</strong> but gave me great results; I brought my Korean language skills from nothing up to an intermediate level in that time.</p><p>Nowadays I’ve shifted my priorities, so I don’t study Korean with that same fervor. However, I still want to maintain and improve this skill by occasionally learning new vocabulary words or grammar. To accomplish this I use <a href="https://www.italki.com/">italki</a> to have a 30 minute lesson each week. This <strong>Slow Progress</strong> is great for me now, although I do want to bump up my Intensity in the future to go after real fluency.</p><p>Another way I maintain my Korean is by speaking only Korean to my 8-month old son, so hopefully he picks it up. And he can learn English on his own time! 😂</p><p>Disregarding <strong>Safety</strong> can lead to <strong>Burnout</strong>, forgoing <strong>Consistency</strong> can lead to <strong>Frustration</strong>, and neglecting <strong>Intensity</strong> can lead to <strong>Slow Progress</strong>. There’s nothing inherently wrong with <strong>Slow Progress</strong>, but <strong>Frustration</strong> can lead you to spinning your wheels and getting nowhere and <strong>Burnout</strong> can be devastating on both your personal and professional life.</p><p>So there you have it! <strong>Safety</strong>, <strong>Consistency</strong>, and <strong>Intensity</strong> are the 3 principles that I recommend to follow when pursuing new technical skills. What’s great is that you can apply these principles to whichever software engineering skills you want to improve!</p><p>Keep these in mind and best of luck in accomplishing all of your New Year’s Resolutions!</p><p><em>Thanks to Juan Lasheras, David Rhodes, Russell Kosowski, and Dr. Jenny Morana Kim-Kosowski who provided input and feedback on drafts of this post.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1342e751803e" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/3-principles-for-learning-new-software-engineering-skills-1342e751803e">3 Principles for Learning New Software Engineering Skills</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Junior Software Engineer’s Job Search Strategy Guide]]></title>
            <link>https://medium.com/hackernoon/the-junior-engineers-job-search-strategy-guide-69c98e396483?source=rss-9ac47f80fbd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/69c98e396483</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[job-hunting]]></category>
            <dc:creator><![CDATA[Mitch Kosowski]]></dc:creator>
            <pubDate>Mon, 26 Jun 2017 10:29:51 GMT</pubDate>
            <atom:updated>2019-05-17T05:02:58.085Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/ruthnaebeck/"><em>Ruth Naebeck</em></a><em> is a co-author for this post. This is her </em><a href="http://www.ruthnaebeck.com/"><em>personal website</em></a><em>.</em></p><p>You are on the <a href="https://hackernoon.com/tagged/job-hunt">job hunt</a> for a junior software engineering position. You could have just graduated from a CS undergraduate program, just finished a programming bootcamp, or just completed a great project that you would like to show off to prospective employers. As long as your portfolio of projects is polished, your background doesn’t really matter. Now how do you get a job as a junior software engineer? In general, what I found worked best was a “shotgun” approach: Send out as many connection requests, messages, and applications in the shortest period of time possible. When I changed to this strategy, I went from having 1 phone screen every 2–3 days to 2–4 phone screens per day, with technical challenges and onsites following shortly thereafter.</p><p>Because this is a shotgun approach, don’t be offended by getting rejected. Indeed, it’s all part of the process. But do use rejection to help guide you in the job hunt. If you are not getting any phone screens, have your resume reviewed and ask yourself if you’re applying to the right sort of jobs. If you’re failing out on phone screens, how could you better prepare for them? For onsites, do the same thing. Remember, it’s a learning process!</p><p>Since there is so much to be done during the job search, I wanted to be super efficient and land as many phone screens as possible in the least amount of time spent networking and completing job applications. This strategy does just that and even includes approximate time taken for each step to help provide a nice gauge for you on your search.<em> </em>Be consistent in your application process and good things will follow!</p><h3><strong>Job Search Strategy Summary</strong></h3><p><strong>Networking (repeat every day):</strong></p><ol><li>LinkedIn</li></ol><ul><li>Send 10 to 20 connection requests (5–15 minutes)</li><li>Send messages when people connect (5–10 minutes)</li></ul><p>2. Alumni Resources (Google Group, Slack, Facebook, etc) (5–10 minutes)</p><p><strong>Job Applications (repeat every day):</strong></p><ol><li>Browse LinkedIn Home Tab for Jobs (5–10 minutes)</li><li>Gary’s Guide Jobs (Programming Category) (5–10 minutes)</li><li>LinkedIn Easy Apply (5–10 minutes)</li></ol><p><strong>Interviewing (prepare every day):</strong></p><ol><li>Phone Screens (45–60 minutes)</li><li>Technical / Onsite Interviews (45–60 minutes)</li></ol><h3><strong>Networking</strong></h3><p>Far and above the highest percentage of all the strategies, networking eventually led to my accepted offer and there’s a very high chance it will be the same for you. What’s the best way to go about it?</p><p><strong>LinkedIn — Request 10 to 20 Connections Daily:</strong></p><p>When you start this process, you may have very few connections who are software engineers. If this is the case, search LinkedIn for “People with the title” Software Engineer, filter by your location, and connect with people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/1*g3aiHRroT0fYvVf6X6vX2g.png" /></figure><p>If you don’t want to pay for LinkedIn Premium after a certain number of connection requests, you will be locked out for the day. That’s fine, just return the next day and do the same search or switch to searching for Front End Developer, Back End Developer, or Software Developer.</p><p>When you’ve gained a significant amount of software engineer connections, people listed on the “My Network” tab under “People you may know” will mostly be software engineers. Using this tab will speed up connection requests significantly. Personally, I spent no more than 15 minutes per day sending connection requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/306/1*VO2ZTiTTYRDIrpItaIfV6Q.png" /></figure><p><strong>LinkedIn — Send Messages When People Connect:</strong></p><p>Great, now you’re attempting to connect with 10 to 20 people everyday and a fair amount of those people will accept your connection requests. What do you do with all those connections? Once they connect back, you can send a message to them (no LinkedIn premium required!). I found keeping it short and sweet worked best:</p><p><em>Hello ${NAME},</em></p><p><em>I am a recent { SAME_SCHOOL ? ${SHARED_SCHOOL} : software engineering } grad looking for a (software engineering) position in ${CITY}. How are you enjoying working for ${COMPANY}? Do you have any recommendations for someone looking to get into software engineering?</em></p><p><em>Thanks,<br>${CANDIDATE_NAME}</em></p><p>Use a common connection in the first sentence to establish why they should care, the more specific the better. Schools, cities, and hobbies can all serve as shared connections. If you have no connection other than they work as a software engineer, use that.</p><p>Why do I wait to get a connection back before I send a message? If someone connects with me it means they are active on LinkedIn and probably willing to <a href="https://hackernoon.com/tagged/network">network</a>. There is a good chance that they will respond to my first message. Personally, I received a response rate around 15% of messages sent. This might seem like a low percentage but remember all you need is one connection that leads to a job offer and this isn’t a huge timesink for you.</p><p>Once you get the conversation started, see where it leads. I had good success asking for general advice as a software engineer to start the conversation. Always keep the ball in their court and respond to messages as soon as you are able! If possible, schedule 1 or 2 in-person meetings (coffee chats) per week. If the person is too busy, schedule a phone, Google Hangout, or Skype call.</p><p>If you connect to a recruiter, the conversation will be different. Here is a sample message to a recruiter:</p><p><em>${RECRUITER_NAME}, <br> <br>I’m a software engineer looking for permanent roles in ${CITY}. I am proficient in ${LANGUAGES_FRAMEWORKS_ETC}.<br> <br>Here is a link to a project I am proud of:</em></p><p><em>${GITHUB_OR_DEPLOYED_LINK}</em></p><p><em>${PROJECT_NAME} is a ${PROJECT_DESCRIPTION}. I had a great time building it with 3 of my colleagues and learned a lot in the process. Etc.<br> <br>Attached please find my resume.<br> <br>Thanks,<br>${CANDIDATE_NAME}</em></p><p><strong>Alumni Resources (Google Group, Slack, Facebook, etc):</strong></p><p>If your school has alumni resources, sign-up, stay active, and reach out to other alumni to network. If possible, try to connect with 1 to 3 different people per day while you are on the job hunt. Try to connect with others also on the job search and pair up to practice algorithm and technical interview questions as well as sharing job search strategies.</p><h3><strong>Job Applications</strong></h3><p>Get as many job applications out there as possible and as quickly as possible! On most days, I applied to 25 or more jobs and each application only took a few seconds. I didn’t send a single cover letter during my job search! Your time is precious on the job search and doing things like changing your resume for each job application or writing cover letters doesn’t really move the needle for a junior engineer and takes away from time that you could be finishing more applications. Use your time wisely!</p><p><strong>LinkedIn — Browse the Home Tab for Job Postings Daily:</strong></p><p>Remember doing all that networking and getting all those connections? One great side effect is now your LinkedIn Home page will have a great feed of all your connections. What does this mean? Every few days you will see job posts from connections:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/558/1*sMUyY9ao8_fpLUEiukfbhg.png" /></figure><p>Reaching out to people who are already connections has a super high percentage for landing a phone screen (especially if they are alumni from your school). I recommend taking 5 to 10 minutes each day to read your Home page.</p><p>By default LinkedIn lists popular posts first so if you see a lot of old posts at the top of your feed, change the post order by clicking the “Sort by” drop-down and choosing Recent:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/107/1*oqaC3iDpKPf7O9mdLqOZbg.png" /></figure><p>Also, there is a lot of spam on the Home page. To unfollow people who write or like posts unrelated to your job search, click the three dots in the top right corner of a post and choose Unfollow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*93VGm7_RiGo4b8PdX-caIQ.png" /></figure><p><strong>Gary’s Guide — Apply to Jobs Daily:</strong></p><p>Check <a href="http://www.garysguide.com/jobs?category=programming">Gary’s Guide</a> every day to apply for “Programming” jobs in your region. If a company really interests you, it’s probably worth the time to go to the company’s web page and apply from there. I had a really good hit rate using Gary’s guide, so I definitely recommend adding it to your strategy!</p><p><strong>LinkedIn Easy Apply — Apply to Jobs Daily:</strong></p><p>Applying to jobs on LinkedIn had a much lower hit rate than the previous strategies, but I still landed the bulk of my interviews through it. How is this possible? Just by the sheer number of applications I sent through it! It’s helpful to note even though my current position came from networking, the interview practice I received from using this LinkedIn strategy was invaluable.</p><p>So how does the strategy work? Navigate to the LinkedIn Jobs tab, use the following search string(1), and your location:</p><p><em>(“software” OR “front End” OR “back End” OR “developer” OR Backend OR Frontend) NOT (Senior OR Sr. OR Intern)</em></p><p>After you search, use the “Date Posted” filter to show jobs posted in the “Past 24 hours”. This ensures the jobs you are applying for are fresh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/161/1*O0N2gWDsQ8GGY9qhConzYw.png" /></figure><p>Now, for each page and for each job that has a LinkedIn Easy Apply indicator:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*Iw7RGoVSFEB0Iok9sK48uQ.png" /></figure><p>Open the job’s link in a separate tab using Cmd + Left Click (Mac) or Ctrl + Left Click (Windows). Once you’re done with a single page, your browser should look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*TdI2KJXbTL2M7d7TNtUMIw.png" /></figure><p>You’ve got a ton of tabs open, now what? Go to last tab (far right) and apply! Click the Easy Apply button, enter your phone number, add your resume and submit the application. Applying to an Easy Apply job should take 5–10 seconds. After you submit, use Cmd + W (Mac) or Ctrl + W (Windows) to close the tab. When you have applied to all the jobs in the open tabs, navigate to the next page of job search results and repeat. You will be able to churn through applications like a real job hunting machine!</p><p>Want to increase your chances of being contacted?</p><ul><li>Look for jobs with the Clock icon and the words “Be one of the first 10 applicants” (reference image above).</li><li>Have at least 1 recommendation on your LinkedIn profile. According to a <a href="https://www.linkedin.com/pulse/what-employers-see-when-you-apply-linkedin-jessica-h-">former recruiter</a>: “<em>90% of the people who apply have ZERO RECOMMENDATIONS</em>.”</li><li>If you have LinkedIn Premium Business, you will receive an extra feature for LinkedIn Easy Apply: “Move application to the top of the recruiters’ list”.</li></ul><h3><strong>Interviewing</strong></h3><p>Now that you have a quick strategy for networking and job applications, you can use the bulk of your time on the job hunt for actual interview preparation.</p><p><strong>Phone Screens</strong></p><p>If you do these four things, you will have an extremely high chance of passing a phone screen for a position that you mostly qualify for:</p><ul><li>Smile and try to relax, it makes a big difference!</li><li>Practice answering the “Tell me about yourself” question daily. Practice in front of the mirror, practice with your significant other, practice with your friends!</li><li>Practice answering “What do you know about this company/role?”</li><li>Ask relevant questions based on the role of the person interviewing you.</li></ul><p><strong>Technical / Onsite Interviews</strong></p><p>If you are interviewing for a Junior Software Engineer position, I found the items below to be largely sufficient for preparing for most technical interviews.</p><ul><li>Have a live working demo of the project you are most proud of on the Internet ready for when you interview! You should know everything about this project backwards and forwards so that you can confidently answer questions.</li><li>I think this <a href="https://medium.com/@kevincennis/how-to-impress-me-in-an-interview-4fc00e96413">article</a> covers the level of technical depth that I saw for most of my technical/onsite interviews.</li><li>Leetcode is good practice but most of it was significantly harder than what I was actually asked in the vast majority of my interviews. If you are preparing for a Big 4 (Facebook, Google, Amazon, Microsoft) interview, understanding data structures/algorithms is extremely important but onsite interviews at most companies simply do not test for this level of knowledge!</li><li>This <a href="https://www.interviewcake.com/coding-interview-tips">InterviewCake article</a> also provides some great help on passing tech interviews.</li><li>Ask relevant questions based on the role of the person interviewing you.</li></ul><p>Consistency is key on the job hunt. If you take this guide, change the steps based on what you find works for you, learn from rejections, and perform this process every weekday you will see results in your job search. The networking and job application steps described here really do only take 30–60 minutes out of your day and I found them to be the most efficient use of my time. Good luck in your job search!</p><h3><strong>References</strong></h3><p>This guide (and my job search!) has been largely influenced by posts made by <a href="http://haseebq.com/">Haseeb Qureshi</a> and <a href="http://blog.calebjay.com/">Caleb Jay</a>:</p><ul><li><a href="http://haseebq.com/how-to-break-into-tech-job-hunting-and-interviews/">http://haseebq.com/how-to-break-into-tech-job-hunting-and-interviews/</a></li><li><a href="http://blog.calebjay.com/2016/10/18/how-this-coding-bootcamp-grad-found-a-job/">http://blog.calebjay.com/2016/10/18/how-this-coding-bootcamp-grad-found-a-job/</a></li><li><a href="http://blog.calebjay.com/2016/11/14/how-to-use-linkedin-as-a-coding-bootcamp-grad/">http://blog.calebjay.com/2016/11/14/how-to-use-linkedin-as-a-coding-bootcamp-grad/</a></li></ul><figure><a href="http://bit.ly/HackernoonFB"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hqOaABQ7XGPT-OYNgiUBg.png" /></a></figure><figure><a href="https://goo.gl/k7XYbx"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vgw1jkA6hgnvwzTsfMlnpg.png" /></a></figure><figure><a href="https://goo.gl/4ofytp"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKBpq1ruUi0FVK2UM_I4tQ.png" /></a></figure><blockquote><a href="http://bit.ly/Hackernoon">Hacker Noon</a> is how hackers start their afternoons. We’re a part of the <a href="http://bit.ly/atAMIatAMI">@AMI</a> family. We are now <a href="http://bit.ly/hackernoonsubmission">accepting submissions</a> and happy to <a href="/service/mailto:partners@amipublications.com">discuss advertising &amp; sponsorship</a> opportunities.</blockquote><blockquote>If you enjoyed this story, we recommend reading our <a href="http://bit.ly/hackernoonlatestt">latest tech stories</a> and <a href="https://hackernoon.com/trending">trending tech stories</a>. Until next time, don’t take the realities of the world for granted!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*35tCjoPcvq6LbB3I6Wegqw.jpeg" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69c98e396483" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/the-junior-engineers-job-search-strategy-guide-69c98e396483">The Junior Software Engineer’s Job Search Strategy Guide</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>