<?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 Ben Junya on Medium]]></title>
        <description><![CDATA[Stories by Ben Junya on Medium]]></description>
        <link>https://medium.com/@MrBenJ?source=rss-e5c0d297befb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*S2PoPk1yujrdz7wJ.</url>
            <title>Stories by Ben Junya on Medium</title>
            <link>https://medium.com/@MrBenJ?source=rss-e5c0d297befb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 17:08:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MrBenJ/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[Don’t Just Be a Technical Writer. Be a Writer.]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@MrBenJ/dont-just-be-a-technical-writer-be-a-writer-4091af771b77?source=rss-e5c0d297befb------2"><img src="https://cdn-images-1.medium.com/max/2600/0*Q0QrRsHHxCXMdtST" width="4608"></a></p><p class="medium-feed-snippet">Many of the immensely popular thought leaders in the tech world write beautiful and elegant blog posts, articles, and opinion pieces&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@MrBenJ/dont-just-be-a-technical-writer-be-a-writer-4091af771b77?source=rss-e5c0d297befb------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@MrBenJ/dont-just-be-a-technical-writer-be-a-writer-4091af771b77?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4091af771b77</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[software-documentation]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[readme]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Thu, 02 Jan 2020 22:44:37 GMT</pubDate>
            <atom:updated>2020-01-02T22:44:37.566Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Front End Development is Hard…]]></title>
            <link>https://medium.com/@MrBenJ/front-end-development-is-hard-7bd5ed22ccfa?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bd5ed22ccfa</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Fri, 29 Nov 2019 20:53:35 GMT</pubDate>
            <atom:updated>2019-11-29T20:53:35.885Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ljeAPeupOa31GMn3" /><figcaption>This is hard too. How will they get internet on that piece of ice? Does he have service via hotspot? Can they push to Git? Is their computer water resistant? How are they holding a computer? It looks cold.</figcaption></figure><p>Remember that <a href="https://twitter.com/skirani/status/1149302828420067328?lang=en">10x Engineer thread</a> on Twitter that got a stupid amount of attention and backlash from the technology community? There’s a line in there that got me, a primarily front end developer, a bit riled up:</p><blockquote>Most of the 10x engineers are full-stack engineers. For them code is code, they don’t care whether it is front-end, back-end, API, database, serverless, etc. I have rarely seen them doing UI work.- <a href="https://twitter.com/skirani/status/1149302838746464256">Source</a></blockquote><p>First off, <strong>UI work is front end development</strong>. And the general tone and candor of the entire thread portrays an extremely narrow minded perspective of what a great engineer is. Furthermore, it reveals a glaring misunderstanding of what UI/front end engineering is, and why it’s hard.</p><p><strong>This isn’t to downplay that databases, API, servers, serverless, and/or devops are not hard. </strong>Everything is hard and has its own set of challenges. I’ve worked with some truly brilliant database, back end, and devops engineers in my career and I’m constantly amazed at their depth and mastery in those disciplines. <strong>Everything is hard</strong>, but to some old school developers that still think it’s cool to bash Javascript and be gatekeepers — they’re wrong.</p><p>The front end developer is the first line of defense between the actual product that gets displayed, and the client or customer. You only get one chance to make a great first impression, and that lies on the shoulders of the front end. Contrary to popular belief, <strong>it’s not the designer, because Sketch or Photoshop files are not what clients use.</strong> Clients interact with the software. The software’s look and feel is built by the front end developer.</p><p>What’s this mean? This means the designer has a piece of ownership when it comes to the front end. The front end engineer is constantly communicating with the designer to see what works, what doesn’t work. What may look great in Sketch or Photoshop may not look so great when a browser window is resized. The front end developer is partially responsible for handling these contingencies and edge cases.</p><p>Great! The design is done and it looks great, but where’s the data? Isn’t the front end supposed to get some data and show it in the view? Of course!</p><p>This means that the front end engineer isn’t just partially responsible for the design coming to life, but retrieving and potentially parsing and/or formatting the data coming from the back end. That’s another stakeholder the front end developer has to work with.</p><p>“Wait! We need some error states for this form!” says User Experience. There’s another person who’s jumping in giving more feedback to the front end.</p><p>Customer support is reporting an overwhelming response to why “new feature” is super important and would be an excellent quality of life update for them. Guess what? That’s on the shoulders of UX, and also in the back of the mind for the front end engineer too.</p><p>Oh, and the executive team wants this new feature to have another thing on there because it’s important to their stakeholders and..</p><p>and..</p><p>And now we have all these people all relying on the front end engineer who is responsible for delivering the ever-so-important <strong>first impression</strong>.</p><ul><li>Back end engineers</li><li>User experience</li><li>Designers</li><li>Business teams</li></ul><p>Which tool should the front end engineer use? We haven’t even started coding and we know we have a minimum of 3–4 people to keep in mind for this feature…</p><ul><li>React?</li><li>GraphQL?</li><li>Redux?</li><li>Angular?</li><li>Vue?</li><li>Polymer?</li></ul><p>These are (mostly) Javascript frameworks, and by the time you read this sentence they’ll all be deprecated because the front end moves way too fast.</p><p>Oh, don’t forget unit or integration testing, component libraries, documentation, setting up Webpack, environments, build systems, task runners, pizza delivery, fixing the dishwasher, and E2E testing, right?</p><p>Oh yeah, you also need to figure out how this is going to be styled and the HTML structure. Are you going to use JSS, CSS-in-JS, Sass, Less, stylus, or PostCSS? Have you heard of the new hotness of Houdini? Let’s use that?</p><p>Oh wait, some of those tools need to be compatible with IE11, since our user base uses outdated browsers and hardware. 5% of users are on IE11, along with 10% of our users on Firefox and 8% on Microsoft Edge, just another thing to juggle, right? By the way, it still needs to work on Chrome.</p><p>The back end developers may be evaluating whether SQL or NoSQL would be best to store the data coming in, and which caching mechanism like Redis or memcached should be used sending data out. Meanwhile, the front end developers are evaluating whether using React Context, the useReducer hook, Redux, or MobX would be the best way to handle state management. It’s not easier or harder. It’s different. Both developers on the team are demonstrating and learning new skills in their craft.</p><p>Sure, listing out EVERYTHING any engineer has to do will make anyone’s head spin, but it’s not just tooling that’s important. It’s <strong>communication</strong>. Front end developers need to explain their rationale for <em>why</em> we’re choosing React, or <em>why</em> choosing Redux store for this data is better than storing it in local component state. It’s important for teams and stakeholders, and it’s crucial to creating that great first impression to the user.</p><p>Because there are so many stakeholders and hands on the product or feature, the <strong>front end engineer translates business requirements into technical ones, deftly selecting the right tools for the job.</strong> In a way, every front end engineer needs some experience or expertise in architecting their own products, <a href="https://medium.com/@MrBenJ/code-boilerplates-and-the-hidden-benefits-of-starting-from-scratch-58778226436c">because knowing what’s happening under the hood is valuable knowledge</a>.</p><p>It’s neither easier nor harder than back end development. Front end developers may not be writing API endpoints or managing data going in and out of tables, but they’re working with UI state management, page load optimization, implementing split testing, and so much more that the back end doesn’t have to do. It’s not harder, it’s just different, and comes with its own set of challenges.</p><p>Is front end development hard? Of course.</p><p>Is any sort of software engineering hard? Absolutely.</p><p>If there’s a bug being reported by a customer, it often (but not always) gets placed on the shoulders of the front end engineer first to triage and fix. “This data is incorrect” might not be a front end issue, but they’ll certainly hear about it and potentially have to debug it.</p><p>Is it hard? Yes… But more importantly…</p><p><strong>It’s worth it</strong>.</p><p>It’s worth shipping a product that users are delighted to see working with stunning design and elegant UX.</p><p>It’s worth ensuring the data is correct and visualized on the screen, allowing a user to easily understand their performance metrics.</p><p>It’s worth knowing the business team is happy with their new feature and the profits coming down the pipeline.</p><p>It’s worth knowing the end-users feel their voices and concerns are being heard, and that they have a say in the product they’re using.</p><p>It’s worth it to learn all the different tools and demonstrate a deep and wide array of skills to take a seemingly impossible challenge and turn it into something that people can use.</p><p>It’s worth it to build something you can look back at, and say, “I’m proud of what I’ve built.”</p><p>It’s worth it to look at the team of amazing people you work with and say that we accomplished this task, together.</p><p>It’s worth it to deep dive into the front end.</p><p>As a front end developer, you are the first line of defense between the end-user’s eyes, and the pivotal amazing first experience, <strong>and you are not alone</strong>. You have a whole team of business stakeholders, user experience, designers, and backend/data engineers to help you build an amazing piece of software together.</p><p>Front end development is hard, and because it’s hard, it’s always worth it.</p><p>Hey you! Thanks for reading! If you liked this and want to learn some awesome Javascript tips, I post JS tips everyday at 11:00 AM Pacific Time. Follow me on <a href="https://twitter.com/MrBenJ5">Twitter</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bd5ed22ccfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Undervalued Skill of Teaching in Software Engineering]]></title>
            <link>https://medium.com/@MrBenJ/the-undervalued-skill-of-teaching-in-software-engineering-58658fabc8d9?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/58658fabc8d9</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[teaching]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Tue, 10 Sep 2019 03:18:45 GMT</pubDate>
            <atom:updated>2019-09-20T21:56:49.479Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*csk1vQ_8k3xsDfDk" /><figcaption>Photo by <a href="https://unsplash.com/@helloquence?utm_source=medium&amp;utm_medium=referral">Helloquence</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the United States, teachers aren’t paid enough and often have to pull additional income from service jobs like waiting on tables or serving coffee. Choosing the career path of a grade school teacher is seen by some as a dead-end profession, and remain extremely undervalued and underrepresented. The skill of teaching however, is slowly starting to become a lost art, a mere relic of what it used to be. It’s becoming harder year after year to find people who know how to teach well.</p><p>In the world of software engineering and programming, demand is so high that companies are forced to hire anyone who has the skill. <a href="https://www.cnbc.com/2018/08/16/15-companies-that-no-longer-require-employees-to-have-a-college-degree.html">Companies like Google, IBM, and Apple have removed their college degree requirement from their hiring process.</a> No one cares where you learned how to code. As long as you can code and do it well, you’re going to get hired somewhere.</p><p>It’s important to note that for larger companies like Google and Facebook, they’re going to most likely ask you technical questions that correspond to computer science, data structures, and algorithms. <a href="https://medium.com/@MrBenJ/algorithms-are-important-so-stop-bitching-about-it-cf45b7462cbc">These concepts and fundamentals are important </a>. However, they’re <a href="https://www.freecodecamp.org/news/why-is-hiring-broken-it-starts-at-the-whiteboard-34b088e5a5db/">not the most accurate form of evaluating a developer’s skills</a></p><p>One may start as an entry or junior level software engineer at a company, but as their career progresses and they’re no longer juniors, they become mid levels, and eventually senior level developers. <strong>As a senior level developer, you’re expected to mentor the new junior developers that come in. </strong>Often times, we confuse the words “mentorship” with “teaching,” but when you’re mentoring someone, you’re teaching them something and explaining foreign concepts to them. You’re teaching them how the code works. You’re teaching them what the best practices are. You’re reviewing code and finding ways to make it better. You’re not just mentoring, you’re teaching and leading by example. If anything, mentoring is another form of teaching.</p><p>I won’t say that mentorship IS teaching. There are some subtle nuances between the two, but that explanation is out of scope for this article. However, I will say that the two skills go hand in hand with one another. Being a great mentor requires teaching skills, and vice versa.</p><p>I find some, but not all developers lack the skill of teaching, and for anyone who wants to progress in this field, knowing how to teach is essential. If you want to build out a team and train them to code a specific way, you have to train them how to code this way. If you want to introduce a new tool into your project and have others use said tool, you have to train them how to use it.</p><p>In both of these situations, training = teaching.</p><p>If teaching is so important, why aren’t we focused on it? We’re so focused on knowing what React Context is or how to optimize render performance on a page because it directly deals with our core hard skill — programming. Teaching isn’t seen as a hard skill in this field. Senior (and even mid) level developers have to guide the newer entry and junior levels devs to understand the codebase and what makes it strong or weak. They have to convey these ideas, messages, and tooling to management and PM’s. They have to fight for their reasoning on why tool XYZ will bring in more revenue or boost site performance.</p><p>A great way for someone without much teaching experience is to mentor a junior or entry level developer. Just the act of helping them set up their local dev environment and letting them know the lifecycle of feature and bug tracking in your company’s system is helpful. If there’s gaps in their knowledge, it’s because <strong>you missed something</strong>, and that’s totally ok! We all have gaps in our knowledge, and teaching someone will help you fill in those gaps.</p><p>You might not know enough… But teach anyway. You’ll get better from it.</p><p>My sister told me the teaching procedure at her medical school. I find it an extremely valuable philosophy when it comes to solidifying your own knowledge on any subject matter:</p><ul><li><strong>See one</strong> — See a procedure and observe how it’s done.</li><li><strong>Do one</strong> — Do the procedure and practice it.</li><li><strong>Teach one — </strong>Teach someone else how to do the procedure.</li></ul><p>Teaching isn’t just for the person receiving the lesson. <strong>It’s for you too. </strong>When you’re teaching someone how to use React hooks, or the difference between a LEFT JOIN and an INNER JOIN, or how Array.prototype.map works, you’re solidifying your own knowledge in the subject, and to explain the concept to someone who knows little to nothing about them, you’re making yourself better. <strong>Teaching is the true test of comprehensive knowledge</strong>.</p><p>Maybe you don’t want to teach, and maybe you just want to be a better developer. But by refusing to teach, you’re stopping yourself from getting better. Teach. It’s OK not to know everything. Your mentee or student will understand, and respect you even more for humbling yourself and not knowing the answer.</p><p>What any determined and highly motivated student or mentee will realize is how you don’t know, but you’re going to find out the solution. Let your own determination light a spark for them. The investment today will reap valuable dividends in the future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58658fabc8d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Absolute Comedic Insanity (and Success) of my Technical LinkedIn Profile]]></title>
            <link>https://medium.com/@MrBenJ/the-absolute-comedic-insanity-and-success-of-my-technical-linkedin-profile-558a15163705?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/558a15163705</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[linkedin]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Tue, 28 May 2019 20:51:32 GMT</pubDate>
            <atom:updated>2019-06-05T04:06:57.651Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Award Losing Full Stack Computer Person.”</blockquote><blockquote>“I write shitty software with bugs.”</blockquote><blockquote>“My code sucks. Don’t hire me.”</blockquote><p>You may laugh at these completely unbelievable and stupid headlines I’ve had on my LinkedIn profile, but they’ve gotten me some of the best jobs I’ve ever had in my 6+ years of programming.</p><p>At the time of this writing, here’s my headline and description:</p><h3>Ben Junya — Award Losing Software Engineer</h3><blockquote>Ben Junya is an award-losing (but 97th funniest in his current workplace) professional full stack web engineer/architect and mobile application developer working in west Los Angeles. He does all the Javascript things on the front end like React single page apps and React-Native along with (some) native Android development in Java. Ben’s pretty active in the technology meetup scene and enjoys going on stage and talk to the audience about technical stuff. Most of the time it’s about corgi’s and how he is extremely awkward at parties. There might be some technical tidbits in there, but it’s usually about how he wants to pet dogs at parties.</blockquote><blockquote>Ben is currently 100% booked and cannot undertake any new full time or contact positions at the moment, however, he is currently open to building long term relationships with other developers, staffing agencies and recruiters. Ben loves people, and would be happy to help out.</blockquote><blockquote>In his fleeting spare time, Ben likes SCUBA diving, surfing, holding onto Bitcoin for dear life, playing video games, studying and analyzing game design and development, improv comedy, tweeting goofy things from his Twitter account, and writing about himself from a silly third person perspective on his LinkedIn profile.</blockquote><p>It might not be 100% professional, but it’s definitely funny (to me. You don’t think it’s funny? You are a jerk, but I still like you. Please keep reading). It might rub a few people the wrong way, but <strong>it gets remembered</strong>. I don’t care about the people it rubs the wrong way because <strong>they aren’t my audience, and sure as hell aren’t my desired coworkers</strong>. The people who laugh and enjoy the oddball writing are the people that I want to work with. Don’t believe that this is my current profile? <a href="https://www.linkedin.com/in/benjunya/">See for yourself right here.</a></p><p>And before anyone says, <em>“there’s no way this works”</em> — Here’s some responses:</p><blockquote>You have one of the best summaries I have ever read and I must know you.</blockquote><blockquote>I think if you and I worked at the same place, I think you could easily be the 96th funniest person.</blockquote><blockquote>By the way, I’m not buying this “97th funniest at work” claim. With that profile, you HAVE to be at the very least, top 90.</blockquote><blockquote>Ok you have the best bio summary I’ve come across yet! I was intrigued and looked up your Twitter, nice Unicorn costume hahah. You gotta at least give me 1 call to tell you about [REDACTED]. I’m not like any other recruiter and I take time in handpicking possible award-losing candidates. :)</blockquote><blockquote>Everyone at the office is losing their shit reading your profile. Some of us want to send an offer as long as you’re wearing that unicorn onesie.</blockquote><p>At the time of this writing, my workplace employs ~60 people total. Semi-related unicorn photo for reference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ejgrj1otS5r967hPHkuQ3Q.jpeg" /><figcaption>It ain’t easy being pink…</figcaption></figure><p>Like any other developer in a tech hotbed market like San Francisco or Los Angeles, I still got plenty of emails and messages on LinkedIn that are straight-up copy and pasted from another email with a couple of names and details changed out, but <strong>by having a humorous and crazy profile, I’m able to instantly weed out copy and paste recruiters.</strong> I’ve designed my profile to be extremely memorable, so that anyone who reads it will remember me as the “award losing developer.”</p><p>I can see who’s actually reading my profile, and those who really take the time to delve in can see the <a href="https://www.modernjsbyexample.net/?referrer=medium">book I’ve self-published</a>, my <a href="https://www.github.com/MrBenJ">open source contributions</a>, and the <a href="https://www.medium.com/@MrBenJ">many articles I’ve published on Medium</a>.</p><p>If someone isn’t going to take the time to read through my profile and see if I’m a good fit for whatever position they’re looking for, then it’s better that they skip me.</p><p>Yes, it’s important to be professional and network/get to know others in said environment at meetups, conferences, events, etc. But when does “professional” meet “personality?” 20 years ago, it was common to go to work in a suit and tie every single day, and project this “work-personality” where we’re putting up this “oh I’m a representative of the company and have to be totally uptight all the god damn time” persona, and that mask we wear is painfully similar to everyone else’s “work-personality.” You never really get to know someone outside of work other than “they’re a front end engineer” or “they’re a database engineer” and a gauge of their skill level. Cool. That works. This is what makes our whole world run on our current level of technology.</p><p>But when you’re looking for that next team member, judging just from skill alone is asking for trouble. Sure, someone might be one of the world’s greatest Python developers that knows the language inside and out, but if said developer has as deep a personality as dried paint on the wall, do you really want to work with them?</p><p>Having the “crazy standout” profile gives potential employers and recruiters a fun and harmless look into who I am, what I’m like to work with, and a little bit of my life outside of work. As I’ve <em>never </em>heard a company say, “We don’t value work-life balance” — wouldn’t they want to learn a little bit about your life outside of coding?</p><p>Practice empathy and look at this from the role of a tech recruiter. <strong>Tech recruiting is a shitty job.</strong> You’re pushing candidates to answer the phone, send resumes, schedule interviews, code challenges, and pushing up crazy numbers to get a commission. You’re actively browsing profile after profile on LinkedIn, reading hundreds of profiles a week to align them with just the right job. <strong>It is not easy work.</strong></p><p>After a long, exhausting day, you encounter, “AWARD LOSING DEVELOPER” as someone’s headline. Who is this guy? His bio is funny as hell… Oh shit, he’ published a book, actively contributes to open source… Holy crap! I should talk to this guy!</p><p>A few things can happen here:</p><ol><li>I’m not a good fit and the recruiter decides not to message me.</li><li>I’m an awesome fit and they message me to see if I’m open for work (I’m not open right now recruiters, sorry!).</li><li>I’m not a good fit, but they want to keep in touch and save my profile as an awesome candidate for a job that might show up in the future.</li></ol><p>Regardless of any of the three outcomes, the bare minimum is <strong>they get a really great laugh and a little bit of fun in their lives to brighten up their workday</strong> — money, compensation, whatever or not, I put a smile on their face and that’s all that matters to me. You had fun reading my profile. I had fun writing it. We both walk away happy. Everyone wins.</p><h3>But I’m not funny!</h3><p>And that’s ok! If you aren’t a weirdo goofball who runs around the streets of Los Angeles doing questionable things in a unicorn onesie, don’t make your profile reflect that.</p><p>If you’re going to write a profile, express yourself in a radically genuine and sincere manner. Talk about you, and make it unique<strong>.</strong> <strong>You’re competing against other programmers who are smarter than you and willing to take less money. Stand out.</strong> Be someone that’s interesting and unique enough to warrant a conversation, and if you can’t think of anything interesting about yourself, the world’s a place that’s there for you to experience it. Take a crazy trip, have a wild adventure, or do that one thing that you’ve been putting off for way too long. Explore and dig into this beautiful world with the passion and energy that lies within yourself, and when you’re ready to hit the grindstone and crank out some code — write that profile and talk about that crazy thing that happened. It’ll stand out, and so will you.</p><h3>But I’m a Terrible Writer!</h3><p>No, you’re not a terrible writer. You code, and that means you write. You may not be communicating with a human, but you’re talking with a computer. <strong>Coding is writing, and writing is communicating. </strong>Regardless of whatever position you take, there has to be some level of written communication skill on there. Practice the skill of writing with your profile, and keep on revising it. It’ll never be perfect, and as you grow as a writer, you’ll find the imperfections with it and revise as needed. There’s little risk, and an essential skill to gain.</p><h3>A Note for the Recently Graduated:</h3><p>For those finishing up a bootcamp or university degree, your admissions officers and career mentors may have said something along the lines of: “be super professional on your profile and resume!” Listen to them. They are right. LinkedIn profiles are the place to put the sincere uniqueness and personality, not a resume. Don’t be afraid to reflect your own personality and what you’re into in that profile. In fact, many of your career mentors and coaches will approve of it, but <strong>omit any shock value in your writing</strong>. Without the proper experience under your belt, it’ll come off as aloof and cocky, and no one wants to hire anyone with those traits.</p><p>There’s already enough bland writing and shitty profiles that show no exuberance and vivacious zeal for life. Don’t make yours another one to skip past. We don’t need more bland developers writing milquetoast prose and meaningless code, so if you have little interest in being a cog in someone else’s machine, then don’t write like a cog. Write about yourself <strong>as your best self</strong>, whether it be humorous, adventurous, or full of quirks. It’s up to you to stand out in a world of carbon copy profiles. Don’t wait for inspiration to write about your best self, or it will never get done.</p><figure><a href="https://usejournal.com/?utm_source=medium.com&amp;utm_medium=noteworthy_blog&amp;utm_campaign=tech&amp;utm_content=guest_post_image"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PYxBP_WV7LI6zc-zdUkNqQ.png" /></a></figure><p>📝 Read this story later in <a href="https://blog.usejournal.com/r/?url=https%3A%2F%2Fusejournal.com%2F%3Futm_source%3Dmedium.com%26utm_medium%3Dnoteworthy_blog%26utm_campaign%3Dtech%26utm_content%3Dguest_post_read_later_text">Journal</a>.</p><p>👩‍💻 Wake up every Sunday morning to the week’s most noteworthy stories in Tech waiting in your inbox. <a href="https://blog.usejournal.com/r/?url=https%3A%2F%2Fusejournal.com%2Fnewsletter%2Fnoteworthy-in-tech%2F%3Futm_source%3Dmedium.com%26utm_medium%3Dnoteworthy_blog%26utm_campaign%3Dtech%26utm_content%3Dguest_post_text">Read the Noteworthy in Tech newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=558a15163705" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Escaping from Tutorial Hell]]></title>
            <link>https://medium.com/@MrBenJ/escaping-from-tutorial-hell-c774bbf67d6?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/c774bbf67d6</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Thu, 11 Apr 2019 20:22:12 GMT</pubDate>
            <atom:updated>2019-04-11T20:22:12.955Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v5LBjJlnM5gBBvv4" /><figcaption>Photo by <a href="https://unsplash.com/@golfarisa?utm_source=medium&amp;utm_medium=referral">Arisa Chattasa</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the programming communities I’m a part of, one of the most common questions often asked is:</p><blockquote>What are some resources or tutorials to learn [insert tool/framework/library/language]?</blockquote><p>This is a great question for <strong>anyone that doesn’t know where to start</strong>. Just like going for a run, cleaning the dishes, or hitting the gym, sometimes the hardest part is getting started.</p><p>After pointing them to resources and hearing their progress, I start to see the cogs turning which inevitably leads to more tools to be learned and knowledge to be consumed. Excellent! All is going well. Someone driven and committed to learning about coding is starting to get into the everyday flow of discovering, learning, building, and delivering. Great!</p><p>Some people do fine with just this bit of guidance, but a trend I’m noticing that I can no longer ignore is:</p><blockquote>I need a tutorial to build this! Where can I find a tutorial to build this?</blockquote><p>These particular developers have unfortunately fallen into a trap, which is dependency and expectation that there’s a tutorial for everything. <strong>This trap is tutorial hell</strong>.</p><p>Tutorial hell typically comes around the time where one “sort of” knows how to build some simple things, but nothing really complex or scalable. They know some basic tools and skills, but they still want that hand holding and security blanket given from online guides and tutorials.</p><p>It’s wonderfully convenient with the power of search engines that so many tutorials and guides are just a couple of keystrokes away, but some libraries and tools just don’t have tutorials, or even worse, their un-official tutorials are terrible, and don’t follow best practices while sometimes encouraging bad habits.</p><p>While the curiosity is high and the desire for knowledge lives on, these guides and tutorials will only let someone learn through the perspective of the author, thus leading to a less intimate relationship with the subject material. They’re going to get this knowledge purely from the guide’s author or writer, not their own firsthand experience.</p><p>Would you rather look at pictures and videos of the Great Pyramids in Egypt? Or would you rather be in Egypt looking at the Pyramids with your own eyes? Through photos and videos, you see the wonders of the world from only the photographer’s perspective, not your own.</p><p>There’s a way to getting out of tutorial hell, and it’s not by doing a tutorial. It’s something that every developer has to learn in their career if they want to get out of tutorial hell — breaking down big tasks into smaller ones.</p><h3>Deconstructing a Tutorial</h3><p>Rome wasn’t built in a day, and neither will a large scale development project.</p><p>What tutorials do very well for newer developers is they break down a project into steps:</p><p>A good tutorial resource will <strong>never</strong> just list one giant thing to do:</p><p><strong>HOW TO BUILD A TO-DO APP</strong><br><strong>STEP 1</strong>: BUILD A TO-DO APP.</p><p>A good tutorial resource will often break things down into small, digestible chunks for you to consume and learn from slowly:</p><p><strong>HOW TO BUILD A TO-DO APP<br></strong>STEP 1: Make sure you have prerequisites installed on your computer, like Node.js, MySQL, etc.<br>STEP 2: Create a database named todo_app and fill it with these columns: (…)<br>STEP 3: Define a data structure for each TODO item<br>STEP 4: Etc…</p><p>Note that each of these steps is directly correlated to a particular skill</p><p><strong>STEP 1:</strong> Install prerequisites<br>This teaches you how to get Node, MySQL, and other tools on your machine</p><p><strong>STEP 2:</strong> Create a database<br>This teaches you MySQL basics, querying, altering, updating columns, etc.</p><p><strong>STEP 3: </strong>Define a data structure<br>This teaches you how to define data for your todo app, and creates a bigger picture of how data works in and out of MySQL…</p><p>A good tutorial will clearly break down a seemingly large task (building a todo app) and put them into smaller chunks for you to consume and learn from.</p><h3>Deconstructing and Breaking Down a Task</h3><p>You’ve been instructed to build a really long page with lots of marketing information for your company. The server and route are already set up. You just need to build out the HTML, CSS, and Javascript for this page. You’ve been given a photoshop mock of what the site will be and all your assets like photos, videos, and fonts have been provided for you.</p><p>It’s silly to think that this would be the approach:<br><strong>STEP 1: BUILD A REALLY LARGE PAGE</strong></p><p>That won’t work. Break it up into smaller tasks like we did our TODO App:</p><p><strong>STEP 1: </strong>Identify common/repeated elements on the page.<strong><br>STEP 2: </strong>Create CSS classes for these common/repeated elements.<br><strong>STEP 3: </strong>Start with building out the mobile version for the first top section on the page<br><strong>STEP 4:</strong> Build out the desktop version for the first top section of the page.<br><strong>STEP 5: </strong>Move onto the section below.<br>Rinse and repeat.</p><blockquote>Break down the task. Identify the first step. Identify what action needs to be done. Then execute.</blockquote><p>Figure out that first step and what needs to get done, then when that’s done, move onto the next.</p><p>If you don’t know what step 1 should be or have absolutely no clue on where to go, then you’re probably in a good spot to hunt for a tutorial.</p><p>If you DO know what step 1 should be, then you shouldn’t be using a tutorial in the first place. Use knowledge from your past tutorials and projects to start this task.</p><p>At the end of the day, you’re not looking for tutorials, you’re looking for step one. Stop hunting for a tutorial, and start thinking critically about the tasks at hand to accomplish what you’re trying to build.</p><p>When your task is done, and you feel good about this project or can foresee the next iteration of your project — Break down the task. Identify the first step. Identify what action needs to be done. Then execute.</p><h3>Through Algorithms</h3><p>Algorithms are given during a programming interview because the interviewer is specifically testing this capability in younger developers. If I give you a task, how do you break it down?</p><p>Take this simple algorithm challenge:</p><blockquote>“Write a function that takes in a string and returns it in reverse”</blockquote><p>The more inexperienced developers will immediate go to Google and search for, “How to reverse a string in [language]” — but that’s not the point here. While if it’s your first algorithm challenge, this makes sense, it’s not really the point here.</p><p>There’s multiple ways to do this. You can do it with Array methods, or with a for loop that goes in reverse. Either way it’s done, you’ll need to break down the task into smaller bits.</p><pre>function reverseString(string) {<br>  /* <br>    I want to use Array.prototype.reverse() to do this. I need<br>    to start off by turning the string into an array.<br>  */</pre><pre>  // STEP 1: Turn the string into an array.<br>  const array = string.split(&#39;&#39;);</pre><pre>  // STEP 2: I need to reverse this array.<br>  const reversed = array.reverse();</pre><pre>  // STEP 3: I need to turn this array back into a string.<br>  const reversedString = reversed.join(&#39;&#39;);</pre><pre>  // STEP 4: I&#39;m done. Return the newly reversed string<br>  return reversedString;</pre><pre>}</pre><p>This type of critical thinking and ability to break down larger tasks into smaller ones is essential to day-to-day developer work. It’s a proper representation of what we do as software engineers.</p><p>Each task that finished makes you a better developer just by a little bit, and some tasks more than others. The more foreign the task, the better you get, and being a better developer is an everyday goal in this line of work.</p><h3>I Don’t Know Step #1… I Need to use a Tutorial!</h3><p><strong>If you have to use a tutorial, that’s fine</strong>, but if you have to google “How to reverse a string” and see some method or approach you’re not familiar with, then you’ll need to find out <strong>what that method or approach is. <em>You must know what your code does</em></strong><em>.</em> Copying and pasting in someone else’s code not knowing what’s happening is a sweet shortcut to cheating yourself out of the opportunity to learn something new. This careless approach takes the potential knowledge to be gained from the tutorial into waste. Know the <strong>how and why</strong> this code works, and like each task finished makes you a better developer — each foreign method that’s not-so-foreign anymore makes you an even better developer than you were before. Remember what you learned from every experience, and use this newfound knowledge when a similar situation arises in the future.</p><p>Trust me, you’ll have to use it sometime 😜.</p><h3>Closing Thoughts</h3><p>The best developers I’ve met and worked with are the ones who are hungry for knowledge, and hold an insatiable appetite for learning more, building up their skills, and playing around with cool new technologies that they want to learn. The knowledge from project #1 carries over to project #2, and project #3, and project #29, and so on, and on, and on…</p><p>After long enough, you’ll find the need for tutorials on completely foreign concepts where you just don’t know where step 1 is, but the more foreign the concept, the greater the challenge which reaps a larger reward and depth of knowledge.</p><p>Continue this cycle, and enjoy the process of continual self-development and mastery in programming. There’s no shortage of stuff to learn, and the only thing that never changes, is that everything will change.</p><p>Stay hungry, stay curious, and bring out the best in yourself through applying knowledge. Think critically, and execute your skills with graceful precision that will only get sharper and stronger over repeated and continual practice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c774bbf67d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automate Team Code Style in 10 Minutes]]></title>
            <link>https://medium.com/@MrBenJ/automate-team-code-style-in-10-minutes-e97fb46d66b7?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/e97fb46d66b7</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Wed, 27 Feb 2019 23:53:59 GMT</pubDate>
            <atom:updated>2019-02-27T23:53:59.145Z</atom:updated>
            <content:encoded><![CDATA[<p>Stop arguing about code style. Do this right now:</p><pre>$ npm install --save-dev prettier lint-staged husky</pre><p>Make a .prettierrc — This one is what I use at work and on personal projects, but go ahead and steal it. IDGAF.</p><pre>{<br>  &quot;printWidth&quot;: 80,<br>  &quot;bracketSpacing&quot;: true,<br>  &quot;useTabs&quot;: false,<br>  &quot;singleQuote&quot;: true,<br>  &quot;semi&quot;: true,<br>  &quot;trailingComma&quot;: &quot;none&quot;,<br>  &quot;arrowParens&quot;: &quot;avoid&quot;,<br>  &quot;jsxBracketSameLine&quot;: true<br>}</pre><p>Add the husky and lint-staged keys to your package.json. Replace \&quot;src/**/*.js\&quot; with wherever your JS is:</p><pre>{<br>  &quot;name&quot;: &quot;awesome-app&quot;,<br>  &quot;version&quot;: &quot;0.1.0&quot;,<br>  &quot;description&quot;: &quot;Lol sure&quot;,<br>  &quot;main&quot;: &quot;index.js&quot;,<br>  &quot;author&quot;: &quot;You &lt;are_awesome@buddy.com&gt;&quot;,<br>  &quot;license&quot;: &quot;MIT&quot;,<br>  &quot;husky&quot;: {<br>    &quot;hooks&quot;: {<br>      &quot;pre-commit&quot;: &quot;lint-staged&quot;<br>    }<br>  },<br>  &quot;lint-staged&quot;: {<br>    &quot;*.js&quot;: [<br>      &quot;prettier --write \&quot;src/**/*.js\&quot;&quot;,<br>      &quot;git add&quot;<br>    ]<br>  },<br><br>}</pre><p>[OPTIONAL]: Run prettier to make sure all your current code is styled and purdy:</p><pre>$ npx prettier --write \&quot;src/**/*.js\&quot;</pre><p>BOOM. YOU. IS. DONE.</p><h3>More “Why” Explanation</h3><p>The worst comments that can pop up in a code review are “code style” comments. These things don’t matter to the compiler, but need to be agreed on by contributors for consistency. Don’t spend time discussing these things during code review... Every time someone says “add a newline to the end of a file” or “stick to indentation for this method please” — there’s a small part of my fractured and lifeless soul that clings to the absolute hell we call “being human” starts screaming for the moment of the heat death of the universe to happen now instead of later in this meaningless life.</p><h3>Tooling Explained</h3><ul><li><a href="https://prettier.io/">Prettier</a> — an opinionated code formatter. This tool does the bulk of the work when it comes to styling your code across your team.</li><li><a href="https://github.com/okonet/lint-staged">lint-staged</a> — Runs any linters on your files that are staged to be committed to git.</li><li><a href="https://github.com/typicode/husky">husky </a>— Git hooks made easier and shared across teams.</li></ul><p>By combining all three of these tools, you’re able to effortlessly automate your code style, no matter how large or small your team is.</p><p>Take the 10 minutes (or less) today to automate this and stop wasting time in code review on “code style.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e97fb46d66b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Book: Modern Javascript by Example]]></title>
            <link>https://medium.com/@MrBenJ/my-book-modern-javascript-by-example-93c6d40a18b2?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/93c6d40a18b2</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Mon, 18 Feb 2019 16:15:51 GMT</pubDate>
            <atom:updated>2019-02-18T16:15:51.114Z</atom:updated>
            <content:encoded><![CDATA[<p>I haven’t been publishing much on Medium because I have been a very busy bee focusing my time and energy into a free and open source book called <a href="https://www.modernjsbyexample.net/">“Modern Javascript by Example.”</a></p><h3>About the Book</h3><p>Modern Javascript by Example is all about what it says — “learn by example.”</p><p>It started in a Slack chat room where someone who was learning Javascript asked, “Can someone show me how a Promise works?”</p><p>I dug into my previous projects and found an XMLHttpRequest that I converted to using Promises — and annotated it with comments explaining what’s going on. The immediate reaction was something along the lines of:</p><blockquote>“Reading about this stuff is hard, but seeing it in a real-world example makes this so easy to understand!”</blockquote><p>That’s when I started looking around on all the resources I typically go to like <a href="https://developer.mozilla.org/en-US/">MDN</a> and <a href="https://eloquentjavascript.net/">Eloquent Javascript</a> — I looked at their examples and all I saw was console.log(some_variable). While I can see what they’re trying to do, I saw noticed parts where a total beginner or intermediate might get confused — like</p><ul><li>When would using Generators be useful in a real-world project?</li><li>Why should I use fetch over XmlHttpRequest?</li><li>What’s the real world implementation of Proxy or Symbol? Why?</li></ul><p>It was at this moment I saw where I could help out. I’ve used a handful of these things in real-world production level projects, and sharing this knowledge could help some poor confused soul out there searching the web like mad, vying for an example or the right information to fix their problem.</p><p>I’ve been working on this book on and off, but writing around 4–10 hours a week just trying to show off as many examples as possible, and to solidify my own knowledge of the language. After a full year’s worth of work, I’m happy to announce Modern Javascript by Example is ready!</p><p>Sure, there’s a few gaps and missing stuff, but I know that this book will never truly be “done.” It will just be iterated, edited, and changed continually to keep up to date with the quickly changing landscape that’s Javascript.</p><p>If you haven’t checked it out: go have a look: <a href="https://www.modernjsbyexample.net/">https://www.modernjsbyexample.net</a></p><p>And if you like it or hate it: <a href="https://www.twitter.com/MrBenJ5">Tweet at me!</a> I will try to help you out as best as I can :).</p><p>Feel free to fork or make a pull request on the <a href="https://github.com/mrbenJ/modern-js-by-example/">Github repo</a> if you find anything wrong (I’m sure there’s plenty of things that are wrong, because I am human and make lots and lots of mistakes).</p><p>Happy reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93c6d40a18b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Aren’t We Writing Unit Tests?]]></title>
            <link>https://medium.com/@MrBenJ/why-arent-we-writing-unit-tests-da6a10f2f8b0?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/da6a10f2f8b0</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[tdd]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 17:49:12 GMT</pubDate>
            <atom:updated>2019-02-04T17:49:12.798Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>It works right? Why bother?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-AUSo74aWsQk3PcS" /><figcaption>I wonder what happens when we put pink fluid in beakers?</figcaption></figure><p>It seems so innocent to just say <em>“screw the tests!” </em>and just keep trucking along, building out features and making things fly around on the screen. This is so painfully common for startups and newbie programmers. Why bother with testing the UI!? It changes so much anyways, it’s not even worth trying to write tests!</p><p>Of course the UI will constantly change. Businesses and Scrum masters want to keep iterating on an idea and make it better and better, so if it’s always going to keep on changing and getting more features, does that mean the tests from before even make any sense?</p><p>When the business is iterating over an idea, you’ll still need all previous functionality to always be working when you’re building out new features with each iteration. With this kind of logic, why <em>wouldn’t</em> you wan’t that safety blanket of unit tests to make sure this is always working? Otherwise, you’re just asking for regressions and features from past iterations to no longer work.</p><p>I will confidently and immediately say YES to building a foundation of unit testing. For those unaware, unit tests just test one small piece to make sure it’s always working.</p><p>This is best seen through example. Here’s a very straightforward function that adds two numbers together:</p><pre>function addNumbers(x, y) {<br>  return x + y;<br>}</pre><p>To test this, we’d use something like expect and a framework like mocha or chai. For the purposes of this article, I’ll be using jest with jasmine since those come right out of the box with minimal configuration:</p><pre>describe(&#39;addNumbers()&#39;, () =&gt; {<br>  it(&#39;Adds two numbers together&#39;, () =&gt; {<br>    expect(addNumbers(5,4)).toBe(9);<br>  });<br>});</pre><p>Great! Now we know every time we run this function, it will add these two numbers together. It didn’t take that much time to write up a quick test to make sure this works…</p><p>Business requirements have changed and we’re iterating on this little helper function we’ve made. It now has to accept up to 4 arguments and add them together now. no problem, we can refactor this to make that happen.</p><pre>function addNumbers(a, b, c, d) {<br>  return a + b + c + d;<br>}</pre><p>Easy, right? That totally fulfills the requirements, but then…</p><pre>TEST FAILED: expected 9 but received NaN</pre><p>You probably shouldn’t add 5 + undefined. That returns NaN. If it weren’t for that test, you’d change up the function without even thinking of all the previous usage of it, and sadly, break the project. <strong>Your 2 minutes of test writing and running it saved you 5 to 10 minutes of debugging</strong>, and this is only for a simple addNumbers() example too.</p><p>Time’s your most valuable asset. Investing minutes today can save hours down the road. For those who aren’t used to writing tests, it might feel asinine, or even counter-productive to write up some tests. It’ll take more like 20 minutes instead of 2, and that’s most likely why lots of developers just skip writing unit tests. It takes time to learn how to write good tests, in addition to writing the tests themselves.</p><p>It’s like eating vegetables and eating healthy. Veggies aren’t really that tasty up front, and they’re not filling… But in the end, they’re really good for you. When you’re dragging your fork to stab that nasty piece of broccoli, stick it in your mouth and feel the sucky texture and taste… It doesn’t feel good. It feels empty and hollow. You want cheesy mashed potatoes and slabs of hot BBQ ribs, not chicken breast and broccoli.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/1*RWxzYbtFv72LOgrVYOd44w.gif" /><figcaption>NO WANT GREEN THING.</figcaption></figure><p>Your code works just fine and it meets the requirements of the product team. You know that you should probably write a test or two just to make sure your work is air-tight and solid, but… You still haven’t set up your testing framework and you have to learn all these boring libraries. It doesn’t feel good and you keep seeing FAILED across your terminal. You want to push your wonderfully working code live, not write tests.</p><p>The next time you eat your veggies, it gets a little easier. Sure, it can still be a bit of a struggle. Maybe you try something a little different, like cauliflower, or asparagus and things start to get a little bit better since you’re finding what’s normal about veggies.</p><p>You just finished up a new feature and you start writing up tests, it still a struggle, but you’ve been experimenting and have read enough documentation to have a pretty good idea of what you’re doing and what’s normal about testing.</p><p>Before you know it, you’ve eating a ton of clean food and veggies, and you’re losing weight and feeling great. Eating veggies is no longer a chore, it’s just something that you just do at every meal because you know it’s the right thing to do. It’s become a lifestyle for you, not a chore.</p><p>You’ve written hundreds of tests and without even thinking about it, you write tests for every feature and bug fix you make. It’s not a chore. It’s just something you start doing because you’ve engrained it into a habitual practice for yourself. Hell, sometimes you even write the test before you start coding and get into some Test Driven Development practices.</p><p>Learning how to write unit tests for your code just isn’t the most fun thing to do, but after so long, you get into it, and you can push your code up to production with confidence and certainty. Your fingers don’t just hover over the ENTER key, afraid something catastrophic might happen. You just push, and deploy, and have peace of mind that everything you’ve done will work.</p><h3>PROBLEM: My project is already huge</h3><p>It may seem like a problem that the project is already large and has zero tests, but in reality, it isn’t. Unit tests alone are very small and only test to make sure one or two little things work at a time.</p><p>All you have to do is <strong>get started with writing your first test</strong>.</p><p>You don’t need to test your gigantic codebase. Start with little pieces that can be tested and aren’t too ingrained. If that’s not the case, find a feature or bug to work on that can be testable.</p><p>After writing your first couple of tests, it’s just like the analogy from before — the first will feel a little weird, but it’ll get easier over time.</p><h3>How do I get started?</h3><p>Most likely, the biggest barrier to entry for those getting themselves acquainted to unit testing is getting your testing framework and tooling set up.</p><p>Luckily in the land of Javascript, testing tools are aplenty, and some like Jest don’t require much configuration to get started. For the most part, a straightforward npm install jest --save-dev will get you started.</p><p>Of course, nothing is one size fits all in the world of development, so here’s a few JS testing frameworks for you to check out:</p><ul><li><a href="https://jestjs.io/">Jest</a> — This is my personal favorite because it offers snapshot testing, and my current work + self-owned projects are React based, and Jest works excellent with React (and <a href="https://github.com/airbnb/enzyme">Enzyme</a>!).</li><li><a href="https://mochajs.org/">Mocha</a> — Another excellent and lightweight testing framework.</li><li><a href="https://jasmine.github.io/">Jasmine</a> — A behavior driven development framework for JS that doesn’t need a DOM. Jest actually uses Jasmine’s syntax and is included, but you can always use it piecemeal should you choose to do so.</li><li><a href="https://www.chaijs.com/">Chai</a> — Assertion library for Node and the Browser. The syntax is a little different than you’d see in Jasmine, but at the end of the day, they do the same thing.</li><li><a href="https://github.com/avajs/ava">Ava</a> — An exciting and new library for testing which runs all of your tests concurrently. Extremely fast, and very powerful, now utilizing all the goodies of Babel 7.</li><li><a href="https://qunitjs.com/">QUnit</a> — If you’re still in regular DOM manipulation land with jQuery, QUnit is excellent for testing out any DOM manipulation tests to make sure your JS is doing all the right things.</li></ul><p>For those who are more Python oriented, My only experience with unit testing in Python is <a href="https://nose.readthedocs.io/en/latest/">Nose</a>, which I have enjoyed.</p><h3>One Test is Better than Zero Tests</h3><p>If you’ve set up your first framework and script to get your testing framework firing away, now it’s time to write that first test!</p><p>Start with something small, whether it’s a small utility function, or just making sure one of your views is rendering without crashing the process. It can be as simple as adding two numbers together, or making sure a class has been added or removed from an element.</p><p>Even if you have just one test, that’s better than zero, and you’re on the road to making your application stable, less bug free, and setting the foundation for adding new tools like Continuous Integration, which will prevent you from pushing broken code to production and save yourselves a bunch of time and headaches from fixing live bugs on production.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da6a10f2f8b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Algorithms Are Important, so Stop Bitching About it]]></title>
            <link>https://medium.com/@MrBenJ/algorithms-are-important-so-stop-bitching-about-it-cf45b7462cbc?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf45b7462cbc</guid>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Fri, 06 Jul 2018 16:57:07 GMT</pubDate>
            <atom:updated>2018-07-06T16:57:07.969Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3p68JqhFgnRlYvT7" /><figcaption>Algorithms are dumb. Look how stupid this code is.</figcaption></figure><p>For self taught developers, doing code challenges and algorithmic challenges feel like asinine wastes of time. Why bother learning to invert a binary tree when you know you’ll never use it when you’re writing your day to day code? Why should I know how to manually sort an array when I can just use Array.sort()? Why bother learning all the computer science bullshit that no one ever uses?</p><ul><li>Writing algorithms is non-reflective of the day to day work as a programmer</li><li>Whiteboard exercises do not provide employers with a clear sense of the candidates skill level</li><li>There’s little to no practical use for the algorithms and problems solved with these exercises.</li></ul><p>That’s what we developers <em>like</em> to think, and we know to a degree some of the above points are true, right? <strong>WRONG</strong>.</p><p><strong>MYTH: </strong>Writing algorithms is non-reflective of the day to day work as a programmer.</p><p><strong>TRUTH:</strong> Everything we write as programmers, from endpoints, to React Components, and Redux Reducers <strong>are algorithms</strong>.</p><p>From the dictionary:</p><blockquote>al·go·rithm — a process or set of rules to be followed in calculations or other problem-solving operations, especially by a computer.</blockquote><p>The following algorithm might not sound interesting or fun, but <em>it’s still an algorithm.</em></p><pre>function addFiveTo(x: number) {<br>  return number + 5;<br>}</pre><p>addFiveTo may not be an interesting or difficult algorithm, but if we need to add 5 to something, this is the function that does it consistently. The “process or set of rules to be followed” is:</p><ol><li>Take in a number.</li><li>Add 5 to it.</li><li>Return a new number.</li></ol><p>Think of it like a machine that inputs something, transforms it, and then outputs whatever it transforms. <em>That’s what algorithms do.</em></p><p>In the context of algorithms in modern web development, a <strong>redux reducer</strong> is an algorithm that takes a payload of data from some database and then reduces the payload down to a single value or object to return to state.</p><pre>case &#39;GET_BLOG_POSTS_OK&#39;: {<br>  const { payload } = action;<br>  const posts = payload.dataArray.map( post =&gt; {<br>    return {<br>      id: post.id,<br>      content: post.body,<br>      author: post.writtenBy,<br>      date: post.createdAt,<br>      tags: post.tags<br>    };<br>  return [...posts];<br>}</pre><p>In short, this data comes in:</p><pre>{<br>  type: &#39;GET_BLOG_POSTS_OK&#39;,<br>  payload: {<br>    dataArray: [<br>      {<br>        id: 11,<br>        body: &quot;This is the body of the post&quot;,<br>        writtenBy: &quot;Lurf Smelderpoff&quot;,<br>        createdAt: &quot;2018-06-31T21:26:51.625Z&quot;,<br>        tags: &quot;body example post&quot;<br>      },<br>      { ... }<br>    ]<br>  }<br>}</pre><p>And this data comes out:</p><pre>[<br>  {<br>    id: 11,<br>    content: &quot;This is the body of the post&quot;,<br>    author: &quot;Lurf Smelderpoff&quot;,<br>    date: &quot;2018-06-31T21:26:51.625Z&quot;,<br>    tags: &quot;body example post&quot;<br>  },<br>  { ... },<br>  { ... }<br>]</pre><p>Data comes in one way, and data comes out another way. Not only is this reflective of day to day work as a programmer, but it’s also an algorithm. We’re telling the computer to take a series of steps to transform data into a manner that user/framework/tool whatever can use.</p><p><strong>Fun side note: </strong>They call them “reducers” because just like Array.prototype.reduce — it takes a value/object/etc and <em>reduces </em>it down to a single value.</p><p><strong>MYTH: </strong>Doing algorithms in coding interviews is a waste of time and doesn’t accurately show a developer’s skill level.</p><p><strong>TRUTH: </strong>Algorithms in coding interviews give a basic, yet incomplete understanding of a candidate’s thought patterns, their coding abilities, and general attitude under pressure.</p><p>For a while, I was very much against doing coding interviews with algorithms and preferred for people to do take-home tests and projects, but after seeing how take-home tests can totally be cheated on and a couple of bad hires, I see the importance of doing some light algorithms to see how candidates work is important. You know it’s bad when one of your close, but extremely talented programming buddies offers you some cash to do his take-home coding test for an interview (this actually happened, twice).</p><p>I’ve seen guys unwilling to answer questions or raise a stink about whiteboarding, algorithms, or XYZ, but whenever I see this, I can already tell that they’re not a good fit for the job. <strong>No job is perfect</strong>, and you’ll see quickly how the candidate will react to pressure and adversity just by having them do an algorithmic challenge.</p><p>With how many bootcamp graduates and “hackers” are out there, you’ll get to see who actually knows what their doing, and who’s just copy/pasting without comprehensive knowledge of what’s going on.</p><p>Understand that because you pass or fail an algorithm challenge, this <strong>should not be a determining factor</strong> for the candidate. Myself, and surely many others have failed tons of these challenges. When I’m interviewing a candidate, I see a candidate’s attitude and how they work under pressure between the fumbling and working out a solution.</p><p>The jobs that push developers to do well are the jobs worth fighting for, because they’ll make you a better developer and communicator. If you’re looking for a job that you can sit around and be comfortable at, then you’re barking up the wrong tree. The best developers I know embrace and tackle challenge. They want to feel pressure, and they want to succeed and make whatever they’re building awesome and something they can be proud of. These are the developers I want to work with on my team, so we can push each other to get better.</p><p>When we’re all writing algorithms in our day to day work and reviewing all the code that’s written between each other, we want to push each other to get better, write cleaner, and level up our skills.</p><p>Stop bitching about your algorithms, because they’re what you write every day.</p><p><strong>Did you like this article? Share it with your friends, colleagues, and coworkers! If you really liked this article, giving me a </strong>👏 <strong>or many more really helps me out!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf45b7462cbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be a Full Stack, and Admit the Shortcomings]]></title>
            <link>https://medium.com/@MrBenJ/be-a-full-stack-and-admit-the-shortcomings-444b4dbe75ea?source=rss-e5c0d297befb------2</link>
            <guid isPermaLink="false">https://medium.com/p/444b4dbe75ea</guid>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming-interviews]]></category>
            <category><![CDATA[personal-development]]></category>
            <dc:creator><![CDATA[Ben Junya]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 00:13:23 GMT</pubDate>
            <atom:updated>2018-06-14T00:13:23.266Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bD815k0dU-Xlsfip" /></figure><p>Earlier this year, I wrote a fairly critical piece of how <a href="https://medium.com/@MrBenJ/shut-up-every-developer-is-full-stack-938bf54218c4">every developer is full stack</a>, and how just about everyone bloats their resume (myself included) just a little bit to sound like we can do everything.</p><p>Thing is… We kinda can.</p><p>I’m the first to admit that I’m primarily a front end guy, but like I said in the last article, I can do a few joins, navigate my way through tables, and all that stuff, but it’s pretty obvious that my backend architecture sure as hell won’t be as solid as my front end code.</p><p>But hey, I’m technically full stack, and if I wanted to build out a full app by myself, front and back, I could totally do it. If I ever wanted my backend to scale, be super fast, and do all the cool things that pro level devops, server, and database guys do, it would probably take me months to years to truly get comfortable and solidify these skills.</p><p>When I look at my /frontend folder on my personal computer, there’s <strong>at least 40 unfinished or shitty projects. </strong>These terribly or halfway architected, incomplete, extremely flawed, and/or completely utterly fucked up beyond Mordor level projects and experiments inside that folder have consumed more of my time than I’d like to admit…</p><p>But because I’ve spent a great amount of time screwing up and learning the hard way inside that folder, it’s made me the developer I am today. In short, that heaping dumpster fire of a folder is why I feel so comfortable and confident working on the front end.</p><blockquote>I have failed so much on the front end, that it’s made me that much better as a front end developer.</blockquote><p>There’s another folder I have called /backend, and <strong>there’s only 10 or 20 </strong>little projects in there. Most are Node, some are Python, and there’s maybe one or two Golang projects I’ve dabbled in. My local Postgres instance has around 5–10 different databases living in there, each with a handful of tables. <em>None of these projects are portfolio showcase worthy</em>, while my frontend folder has a couple I wouldn’t mind showing off to some friends, family, and maybe even an interviewer.</p><p>It’s because of this I openly admit that I’m probably not the best person suited for building out a fully fleshed out API and servers. Can I do it? Of course, but I know I’m not the best at it, and to anyone asking me about it, I will candidly say, “you could probably find someone who could do that much better than me.”</p><p>To most people, admitting that you’re not great at the backend turns some heads and I can already hear someone thinking, “But that sounds like you’ll never get hired anywhere! It’s career suicide!”</p><pre>Interviewer: Do you know Haskell?</pre><pre>Dev: (I took a 2 month class a couple years ago in college about Haskell...) Yeah! I know Haskell! </pre><p>If I was interviewing someone and they openly said, “I don’t know React very well,” or “I do not understand why we’d use Redux with React,” I will have significantly more respect for them opening up. My follow up to this statement would be along the lines of, “would you be willing to learn how redux interacts with React?” and 99% of the time they’ll respond with a resounding “yes.”</p><p>Pulling the ego to the side and admitting fault, shortcomings, and weaknesses is not easy. There is a subtle, yet humble confidence that’s required to really tell someone that you’re not the right fit for something, and it’s not because of lack of confidence (that’s a totally different beast), but the willingness to face the not-so-shiny truth about one’s own skill makes one stronger. It takes more guts to admit you suck than to admit you’re awesome.</p><p>One of the most important skills for developers is to be able to learn and pick up new skills and technologies quickly, regardless of where it sits in the stack. Experiment, play, break shit, get better. The only way you’re going to get better is by failing, so fail quicker, and get better fast</p><h3>The Market Demands Full Stack Developers</h3><p>The world wants full stack developers more than ever today. You’ll see more “Full Stack Developer” positions open today than ever before. If you’re studying to be a developer, it’s important you stack the deck in your favor as much as possible. Be a polyglot. It’s totally ok!</p><p>In my current job, I’ve had to touch quite a bit of the API layer and write my own Node scripts to automate the managing of data. While building out API’s and maintaining Express applications just isn’t my strong suit, this experience has given me a whole new understanding and respect for server-side development. I understand more SQL than I did a few months ago, and I’m applying these important principles of performance and unit-testing on the front end now (not that I wasn’t testing my front end code, I’m just 1000% even MORE strict about it!).</p><p>This type of full stack knowledge that encompasses all layers of an application, from design and UX, UI engineering layer, to servers, data storage, and deployment is extremely powerful, and it allows me to convey information to non-technical product teams in a manner that shows a high level overview of the entire technical stack and what each piece does. This kind of person is exactly what these hot venture capital startups are looking for, and these companies aren’t stupid, they know that full stack guys are going to be at least “OK” with everything, and they also understand that they’re going to have a tendency to be weighted either on the front or the back.</p><h3>I Don’t Know, and That’s OK</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NNEwmOWzawdi7mvc" /></figure><p>As a true full stack developer, you’re going to be confronted with situations that you just plain aren’t going to know, and it’s better to just admit your shortcomings than to bullshit your way through it.</p><p>“I don’t know” is one of the most difficult phrases to say.</p><p>In a meeting a couple of days ago, I was asked a ton of Node questions and had to think of some solution to a data syncing problem we were having with a few of our services.</p><p>“What is the level of effort is going to be to get all of this done?” asked my project manager.</p><p>As much as I wanted to blurt out an answer and make my PM happy, I gave myself 20 seconds to really formulate my answer, and I knew that if anything, I had to be confident in my response:</p><blockquote>I don’t know, but I’m going to find out. Can I get back to you mid day tomorrow after I look into a couple of potential solutions?</blockquote><p>The best developers I’ve worked with in the field are objective-driven and solution-oriented. We definitely don’t have the answers, but we’ll find them out.</p><p>I don’t know, and that’s OK, because I’m going to find a solution. I have an objective, and I’m going to find a solution.</p><p>Every time I solve an “I don’t know” moment makes me a better programmer than I was before.</p><p>Happy coding!</p><p><strong>If you liked this article, give me a 👏 or two, and share it with your colleagues!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=444b4dbe75ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>