<?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 Kenneth Worden on Medium]]></title>
        <description><![CDATA[Stories by Kenneth Worden on Medium]]></description>
        <link>https://medium.com/@kkworden?source=rss-53aa98972fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*M0CggAez2M0HaKDZSIuulA@2x.jpeg</url>
            <title>Stories by Kenneth Worden on Medium</title>
            <link>https://medium.com/@kkworden?source=rss-53aa98972fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:32:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kkworden/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[What is the Cloud?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kkworden/what-is-the-cloud-e75c6574953e?source=rss-53aa98972fd------2"><img src="https://cdn-images-1.medium.com/max/2600/1*YB42p4KRHrnYeGpoh4UVvQ.jpeg" width="6395"></a></p><p class="medium-feed-snippet">A light-weight explanation of an overloaded term.</p><p class="medium-feed-link"><a href="https://medium.com/@kkworden/what-is-the-cloud-e75c6574953e?source=rss-53aa98972fd------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kkworden/what-is-the-cloud-e75c6574953e?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e75c6574953e</guid>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[computing]]></category>
            <category><![CDATA[internet]]></category>
            <category><![CDATA[computers]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Mon, 08 Feb 2021 14:47:24 GMT</pubDate>
            <atom:updated>2022-02-25T20:15:55.141Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[5 Skills Every Aspiring Software Engineer Should Master]]></title>
            <link>https://medium.com/@kkworden/5-skills-every-aspiring-software-engineer-should-master-2b9108a94b9d?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b9108a94b9d</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[skills]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Sun, 17 Feb 2019 14:16:00 GMT</pubDate>
            <atom:updated>2019-02-17T14:16:00.630Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s more than just programming.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fJjo9jCynuVVeXQNgOmSDw.jpeg" /></figure><p>Your mind races as you deliberately place your zippered, black, nylon backpack by the front door. Your first internship at that cool tech company, creating software for the masses, starts tomorrow.</p><blockquote>“Am I really ready to head into the real-world and start coding?”</blockquote><p>You arrive early on the first day, hair and fingernails trimmed with microscopic precision. Cool morning sunlight streams from the transparent walls and fills the cavernous atrium. Trembling with anticipation, you cross the smooth, shiny, stone floor to greet a cheery, brunette receptionist. She motions you to wait in an eggshell seat, lined with a cushy blue fabric.</p><p>After a heavy half-hour, a scruffy, middle-aged man draped in a heather gray T-shirt and cargo shorts strides across the slick floor in sandals. He gives you a friendly smile. He introduces himself as Dylan. This man is your mentor.</p><p>Dylan whisks you past arrays of monitors, scrolling endlessly with terminal output, into a private, carpeted conference room. He sets his caffeine next to the rainbow of dry-erase markers ordered neatly on the bright, white, synthetic table. Wasting no time, he scoops up the red Expo marker and begins his masterpiece. Dylan sweeps his hands across the board, like a painter overwhelmed with passion, drawing complex system diagrams. A database here, a micro-service there.</p><p><em>“What will I be working on?” </em>you sheepishly interrupt.</p><p>Dylan flashes you another smile. Red marker in hand, he pries open his laptop.</p><p><em>“Here,”</em> he says, handing the laptop to you. An IDE and bustling terminal fill the screen. Your eyes quickly scan the code. How did the veteran developers come up with such efficient, elegant, esoteric solutions?</p><p>Whether you are a lowly intern or a full-fledged developer, software engineers do more than just code. Code plays a large role in our careers, of course, but a good software engineer will have mastered skills beyond the terminal.</p><p>I have personally found the following skills to be paramount in my career.</p><h3>1. Communication</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pU1lkvaAFFUP0FW_Rg93Eg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/IBUcu_9vXJc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Thomas Drouault</a> on <a href="https://unsplash.com/search/photos/meeting?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>When people think of software engineers, they think of socially inept, unkempt code monkeys. In reality, the best software engineers navigate social situations with ease.</p><p>Most likely you will work on a team and deal with people daily. People will hold all of the answers, especially when starting somewhere new, and people can also help improve your ideas. When you write code, empathize with future developers and clarify your code through comments to make development easier. Clear code comments will also keep people from constantly pinging you with semantic questions, keeping your bandwidth wide.</p><p>Value socialization. Talk to other teams in the break room. Invite your co-workers out to lunch. Make friends outside of work. Pursue your hobbies and interests. Remember that<em> no man is a failure who has friends</em>.</p><h4><strong>You can improve by…</strong></h4><ul><li>Commenting your code</li><li>Meeting with domain experts, explaining what you want to do, and listening to their advice</li><li>Talking to your supervisor often about your progress</li><li>Knowing your teammates on a friendly level</li><li>Talking to anyone and everyone, even outside of work</li></ul><blockquote>I personally recommend <a href="https://amzn.to/2WXtilz">How To Win Friends and Influence People</a> if you want to improve communication skills. It is a timeless book that has helped many successful people including Warren Buffett.</blockquote><h3>2. Reading code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PcTu-jNSmwxr82jdEEGtiQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/iar-afB0QQw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Markus Spiske</a> on <a href="https://unsplash.com/search/photos/code?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You should be reading more code than you are writing. Before writing, understand all systems that your new code will affect. Communication also plays a massive role here. Remember that reading code is a collaborative process, so talk to senior developers to clearly visualize how things currently work. Eventually, you will jump into the code, but take your time.</p><p>If you ask nothing, you learn nothing. <em>A wise man’s question contains half the answer.</em></p><h4>You can improve by…</h4><ul><li>Learning <strong>why </strong>your systems exist</li><li>Thinking how you, personally, would solve the same problems</li><li>Reading merge requests made by your team</li><li>Reading up on documentation, and writing documentation if none exists</li><li>Asking plenty of questions</li></ul><h3>3. Data structures + algorithms</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/354/1*IDT7D55LRvMGHCjVTQ26uw.png" /><figcaption>The most basic, the binary tree.</figcaption></figure><p>Data structures and algorithms are any programmer’s bread and butter. They allow you to write stellar code and make informed design decisions. If you received a formal education from a university, you will already know these. Still, sharp tools make good work. Make sure you at least know the following data structures, and review them periodically.</p><p>Check out <a href="https://leetcode.com/">Leetcode</a> and <a href="https://www.hackerrank.com/">Hackerrank</a> problems to stay practiced.</p><h4><strong>Know the following data structures…</strong></h4><ol><li><a href="https://www.tutorialspoint.com/data_structures_algorithms/linked_list_algorithms.htm">List</a></li><li><a href="https://www.geeksforgeeks.org/stack-data-structure/">Stack</a></li><li><a href="https://www.tutorialspoint.com/data_structures_algorithms/dsa_queue.htm">Queue</a></li><li>Arrays</li><li><a href="https://www.youtube.com/watch?v=shs0KM3wKv8">Hash tables</a></li><li>Trees</li><li>Graphs</li></ol><h4>Know the following algorithm topics…</h4><ol><li>Divide-and-conquer</li><li><a href="https://medium.com/@codingfreak/top-50-dynamic-programming-practice-problems-4208fed71aa3">Dynamic programming</a></li><li>Flow networks</li><li><a href="https://www.geeksforgeeks.org/backtracking-algorithms/">Backtracking</a></li><li>Greedy algorithms</li><li>Asymptotic analysis (Big O complexity)</li></ol><blockquote>I recommend the book <a href="https://amzn.to/2WZbjLr">Competitive Programming (3rd edition)</a>. I personally have used this book to prepare for interviews and strengthen my problem-solving skills.</blockquote><h3>4. Design patterns</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h22q4NX_2i2dWWViMmjRSA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/7o6-pXbVAZ0?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel</a> on <a href="https://unsplash.com/search/photos/blueprint?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Have you heard of a <a href="https://www.geeksforgeeks.org/singleton-design-pattern/">singleton</a> class? This is one of the most common <a href="https://sourcemaking.com/design_patterns"><strong>design patterns</strong></a>.</p><p>If you have been coding for some time, you may have realized that some patterns are repetitive. Things such as event handling, customization, and object creation are common. Designs patterns exist for many of these common situations. These patterns will keep your code DRY and prevent you from re-inventing the wheel.</p><h4>You can improve by…</h4><ul><li>Learning the common design patterns</li><li>Noticing when a design pattern can be used</li><li>Implementing the design patterns in personal projects</li></ul><blockquote>A good book on the subject is <a href="https://amzn.to/2GpKECs">Head First Design Patterns: A Brain-Friendly Guide</a>. This book has many common design patterns and explains simply when they are used. My team used this book when we created an Android workout tracker app.</blockquote><h3>5. New technologies</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xpO4LbpWO-UB3uOE_N8Uaw.png" /><figcaption><a href="https://www.inrhythm.com/mike-fisher-horror-code-lounge/graphql-logo-1/">https://www.inrhythm.com/mike-fisher-horror-code-lounge/graphql-logo-1/</a></figcaption></figure><p>The wise developer never reinvents the wheel. Instead, he stands on the shoulders of giants, using new and exciting technologies to achieve his goals. Ideally, you have a personal project or two where you use new technologies.</p><p>You do not need to know how to use every new library or framework, however. Even perusing Medium developer subreddits and blogs will help keep your ear to the ground. Knowing where the industry is headed will allow you to freshly tackle problems, rather than be confined to your old habits. Deliberate on the usefulness of new technologies before accepting or dismissing them.</p><p>On top of everything, make sure to stay curious. The moment you believe you are the best you can be is when you start falling behind. Companies will offer tech talks, workshops, and pay for you to attend conferences and hackathons. Take full advantage of these.</p><h4>You can improve by…</h4><ul><li>Following developers (like me!) and tech companies on social media</li><li>Attending developer conferences</li><li>Participating in hackathons</li><li>Building a personal project</li><li>Reading research papers</li><li>Taking an online course</li><li>Staying curious</li></ul><p>Always keep on improving. Achieving mastery takes practice. In the past, I personally struggled to communicate my ideas clearly due to arrogance surrounding my programming language prowess. After years of practice, I am now a well-rounded developer- ready to take on the world. If I can do it, then you can, too.</p><p>What skills have you mastered? What skills need improving? Let me know in the comments. Peace ✌️✌️✌</p><blockquote>Special thanks to <a href="https://www.linkedin.com/in/david-gardiner-267a3315a/">David Gardiner</a>, <a href="https://www.facebook.com/mohmeet.singh">Mohmeet Singh</a>, and <a href="https://www.linkedin.com/in/sukrith-akula/">Sukrith Akula</a> for helping me edit!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b9108a94b9d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Growing Friend Circles and Shrinking Attention Spans]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kkworden/on-growing-friend-circles-and-shrinking-attention-spans-e96b4ead497c?source=rss-53aa98972fd------2"><img src="https://cdn-images-1.medium.com/max/2600/1*4Gxe9Fyrl3ozWgHxS917Ug.jpeg" width="3909"></a></p><p class="medium-feed-snippet">How tiny Instagram and Snapchat &#x201C;stories&#x201D; have had a huge impact</p><p class="medium-feed-link"><a href="https://medium.com/@kkworden/on-growing-friend-circles-and-shrinking-attention-spans-e96b4ead497c?source=rss-53aa98972fd------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kkworden/on-growing-friend-circles-and-shrinking-attention-spans-e96b4ead497c?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/e96b4ead497c</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[instagram]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[society]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Wed, 30 Jan 2019 12:31:00 GMT</pubDate>
            <atom:updated>2019-01-30T12:31:00.808Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What Happens to Your Data When You Die?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/design-and-tech-co/what-happens-to-your-data-when-you-die-7365fce3553f?source=rss-53aa98972fd------2"><img src="https://cdn-images-1.medium.com/max/1920/1*dyXtx8ls9ZpDrT-Ivw0N_w.jpeg" width="1920"></a></p><p class="medium-feed-snippet">Should we erase our profiles before we kick the bucket?</p><p class="medium-feed-link"><a href="https://medium.com/design-and-tech-co/what-happens-to-your-data-when-you-die-7365fce3553f?source=rss-53aa98972fd------2">Continue reading on Design and Tech.Co »</a></p></div>]]></description>
            <link>https://medium.com/design-and-tech-co/what-happens-to-your-data-when-you-die-7365fce3553f?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7365fce3553f</guid>
            <category><![CDATA[society]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[self]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Sat, 05 Jan 2019 12:31:00 GMT</pubDate>
            <atom:updated>2019-01-09T22:14:15.016Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Trading Bots, The Economy, and You]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.datadriveninvestor.com/trading-bots-the-economy-and-you-3d24a1032b3d?source=rss-53aa98972fd------2"><img src="https://cdn-images-1.medium.com/max/1920/1*iXAPzk2MF86OQ0RbWefXtQ.jpeg" width="1920"></a></p><p class="medium-feed-snippet">As trading bots become more commonplace, what do the markets actually represent?</p><p class="medium-feed-link"><a href="https://medium.datadriveninvestor.com/trading-bots-the-economy-and-you-3d24a1032b3d?source=rss-53aa98972fd------2">Continue reading on DataDrivenInvestor »</a></p></div>]]></description>
            <link>https://medium.datadriveninvestor.com/trading-bots-the-economy-and-you-3d24a1032b3d?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d24a1032b3d</guid>
            <category><![CDATA[trading]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[stock-market]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[economics]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Fri, 28 Dec 2018 12:31:00 GMT</pubDate>
            <atom:updated>2018-12-30T09:56:48.109Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A Beginner’s Guide to Homebrew]]></title>
            <link>https://medium.com/@kkworden/a-beginners-guide-to-homebrew-4b665956a74?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b665956a74</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[homebrew]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Thu, 27 Dec 2018 15:30:07 GMT</pubDate>
            <atom:updated>2018-12-27T15:30:07.974Z</atom:updated>
            <content:encoded><![CDATA[<h4>Every programmer on a Mac should know this package manager</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/256/1*CBCWQowzYqU83B0capCTQA.png" /><figcaption>The Homebrew logo. Credit <a href="https://brew.sh/">brew.sh</a></figcaption></figure><p>Chances if you are a developer or tinkerer and you run macOS, you install tons of software.</p><p>Libraries, virtual machines, server software, version control, build systems, language compilers, fixes.</p><p>Installing software on a Mac typically involves dragging an application icon to the Applications folder. Easy peasy lemon squeezy, no?</p><p>No. What about the configuration files the application generates? You configure something, and now the application is broken. If you want to uninstall the application later, now you have delinquent data files and folders scattered on your hard-drive. This eats up precious hard-drive space- gigabytes if you are not careful.</p><p>Wouldn’t it be nice if there were something to keep track of all of this, making installing and uninstalling software a surgical procedure, rather than a patch job? Turns out there is!</p><h3><strong>Meet Homebrew</strong></h3><blockquote><strong>“The missing package manager for macOS”</strong></blockquote><p><a href="https://brew.sh/">Homebrew</a> prides itself as <em>“the missing package manage for macOS”</em>. If you have ever used Ubuntu or a Debian-based linux installation, you might be familiar with <a href="https://wiki.debian.org/apt-get">apt-get</a>, <a href="https://wiki.debian.org/Aptitude">aptitude</a>, or <a href="https://wiki.debian.org/dpkg">dpkg</a>. These are all very powerful package managers that allow you to control every piece of software on your system. Homebrew attempts to capture the functionality of these managers. It manages packages locally on your machine and can download packages from online sources as well.</p><p>At first you may find yourself confused, mainly because Homebrew boasts a cheeky vernacular when it comes to describing software. You need not learn every term, but knowing a few will help:</p><p><strong>Tap:</strong> A Git repository of packages. Typically, you will find Homebrew has the homebrew/core tap already “tapped”, meaning that you can install packages from this source.</p><p><strong>Cellar: </strong>Where your local packages are installed by Homebrew. A cellar exists only on your local machine.</p><p><strong>Formula: </strong>A software package. When we want to install new programs or libraries, we install a formula. Homebrew keeps multiple versions of formula (formulae) in the Cellar, so that you can downgrade if a new version of a package breaks something.</p><blockquote><a href="https://docs.brew.sh/Formula-Cookbook">You can find all of the definitions here.</a></blockquote><p>So, <strong>tap </strong>= <strong>repository, cellar = local install location, formula = software package. </strong>Got it? Good.</p><h3>Installing Homebrew</h3><p>Installing Homebrew is simple. Simply open a terminal and run:</p><pre>/usr/bin/ruby -e &quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&quot;</pre><p><a href="https://brew.sh/">As defined on the Homebrew homepage.</a> This command will always get you the latest version. Now that we are installed, let’s check out how to actually use it!</p><h3>Using Homebrew</h3><h4>Finding packages (formulae) to install</h4><p>To find packages to install, you can run:</p><pre>$ brew search &lt;name&gt;</pre><p>Although in today’s world, a quick Google search for “<em>&lt;package name&gt; homebrew” </em>can usually find you what you are looking for.</p><p>Once we find the package we want to install, we need to install it.</p><h4>Installing formulae</h4><p>The most common use of Homebrew is installing packages. Say we want to install <a href="https://nodejs.org/en/">Node.js</a> on our machine. We need only do the following:</p><pre>$ brew install node</pre><p>This searches all of the taps (repositories) that you have configured Homebrew with, and finds a matching formula (package) with the provided name. <a href="https://github.com/Homebrew/homebrew-core/blob/a707496e6b8457255b3f8942df87bb074ed46ead/Formula/node.rb">Node is located in the default core tap</a>. However, sometimes you may not be able to find the formula you want.</p><p>In this case, you need to add a new tap.</p><h4>Adding taps (repositories)</h4><p>If Homebrew cannot find the package you want, it may be hosted in a different repository. As mentioned before, homebrew/core is already “tapped” (Homebrew searches this repository) for you. To view what is already tapped, simply run:</p><pre>$ brew tap</pre><p>Your output may look like this:</p><pre>homebrew/cask<br>homebrew/core</pre><p>But what does homebrew/core mean? Why is there a slash?</p><p>By default, Homebrew assumes that you are looking for a repository on Github. The convention for tap names is &lt;user&gt;/&lt;repo&gt;. That means that there is a Github user, homebrew, with a repository, core. <a href="https://github.com/Homebrew/homebrew-core">And so there is</a>.</p><blockquote>Because this is a Homebrew special repository that is tapped by default, the repo is actually called homebrew-core. Note that the &lt;user&gt;/&lt;repo&gt; form is a <strong>convention, </strong>not a strict requirement.</blockquote><p>To actually add new taps, use one of the following commands:</p><pre>$ brew tap &lt;user&gt;/&lt;repo&gt;</pre><p>This command assumes that the repository is hosted on Github, and is a shorthand. If you want to tap repositories hosted elsewhere, use:</p><pre>$ brew tap &lt;user&gt;/&lt;repo&gt; &lt;URL&gt;</pre><p>The &lt;URL&gt; argument specifies the clone URL. The &lt;user&gt;/&lt;repo&gt; form thus denotes how we refer to this tap in the future- you can call it whatever you want.</p><p>After tapping a new repository, you can install whatever formula you were trying to before. To find new repositories, again, a quick Google search will usually yield the answer.</p><p>Homebrew keeps a list of packages and their versions in a local cache. Obviously, if you do not use Homebrew for a few weeks, this cache will be outdated and may cause you to install outdated software. To correct this, we can keep our taps fresh.</p><h4>Keeping taps fresh</h4><p>Before running brew install, it is best to get the latest versions of formulae so you do not accidentally install an old package version. This is simple:</p><pre>$ brew update</pre><p>Now installing packages will get you the latest version, which is typically what you want.</p><blockquote>Homebrew will typically keep itself up-to-date when you run other brew commands, but calling this is still a good practice.</blockquote><h4>Upgrading local packages</h4><p>Software moves fast. Packages get updated frequently- thehomebrew/core tap was updated 16 minutes ago as of my writing this. To upgrade installed formulae, simply run:</p><pre>$ brew upgrade</pre><p>This takes all of the formulae you have installed, checks their respective taps for new versions, and installs the new versions for you automatically. Typically, you will want to brew update right beforehand:</p><pre>$ brew update &amp;&amp; brew upgrade</pre><p>This keeps you from upgrading to the non-latest versions of packages.</p><p>So brew update gets the latest versions of packages and brew upgrade installs the latest versions.</p><h4>Removing formulae</h4><p>Say you want to uninstall a package. This is self-explanatory:</p><pre>$ brew uninstall &lt;formula&gt;</pre><p>For example:</p><pre>$ brew uninstall node</pre><p>However, say you upgraded this package a few times. Homebrew keeps old versions of packages, and thus you might have a few Node.js binary versions in your Cellar. If you find yourself strapped for hard-drive space, run:</p><pre>$ brew uninstall -f node</pre><p>This tells Homebrew to uninstall all versions of the node package.</p><h4><strong>Reducing clutter</strong></h4><p>To remove old versions of packages and free up space, you can run:</p><pre>$ brew cleanup</pre><p>This cleans up old versions, lock files, and outdated files, keeping your hard-drive squeaky clean!</p><h3>Conclusion</h3><p>Although Homebrew introduces nomenclature that can be off-putting to the beginner, it is a capable software that has earned its place as the de facto package manager in the macOS system.</p><p>This tutorial walked us through how to install and use Homebrew to manage software on our Macs. Hopefully this helped you! If it did, remember to clap it up!</p><p>Thanks for reading! Peace ✌✌✌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b665956a74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using GraphQL and Node.js to Make a Basic Chat App — The Frontend]]></title>
            <link>https://medium.com/@kkworden/using-graphql-and-node-js-to-make-a-basic-chat-app-the-frontend-5bab2b98be21?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bab2b98be21</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Sun, 16 Dec 2018 20:07:27 GMT</pubDate>
            <atom:updated>2018-12-16T20:07:27.282Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using GraphQL and Node.js to Make a Basic Chat App — The Frontend</h3><h4>Using the GraphQL backend to build a chat application</h4><blockquote>In the <a href="https://medium.com/@kkworden/using-graphql-and-node-js-to-make-a-basic-chat-app-1ed2e6a7a6d3">previous tutorial</a>, we created a dead-simple GraphQL API for a chat application. In this tutorial we build on that code and construct a frontend for our chat application.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Pz652MGdXILZcL-hamqpeg.png" /><figcaption>The GraphQL logo</figcaption></figure><p>Now that we have a working API, we should create a webpage to make it useful. Nothing too fancy- for this tutorial we will use HTML and <a href="https://code.jquery.com/">jQuery</a> to make requests to our API backend.</p><p>Go ahead and create some input fields, a button, and a container for the chat messages.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/33500ecb66346f8a1c1441f5f9e820d2/href">https://medium.com/media/33500ecb66346f8a1c1441f5f9e820d2/href</a></iframe><p>We now have a nickname field, a messages field, a send button, and a div which will hold the contents of our chatroom. All we need to do now is make requests to the chat API!</p><p>Let’s fill in that script tag at the bottom of the page. Now that we have jQuery, we can make a POST request and populate our messages div:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fbbb1dacb36066ccee115d65f2ab16ab/href">https://medium.com/media/fbbb1dacb36066ccee115d65f2ab16ab/href</a></iframe><p>We define a function, getChatroom(), which runs every 2 seconds. Using the jQuery $.post function, we send our GraphQL query in the query field. The form is exactly as we saw in the interactive console. It makes an HTTP POST request for the messages array, as we saw in the <a href="https://medium.com/@kkworden/using-graphql-and-node-js-to-make-a-basic-chat-app-1ed2e6a7a6d3">previous tutorial</a>. We then set the value of the messages div to the contents of the array. Refresh the page, and we should be in business!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DO0BCZYHXuzO6XetHOXb9A.png" /></figure><p>Hmmmmm…. nothing shows up. That’s because we haven’t sent any messages! Let’s write some code so we can do that.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/de52dc2c5aae318d741ffee22046bf29/href">https://medium.com/media/de52dc2c5aae318d741ffee22046bf29/href</a></iframe><p>We use getChatroom as the callback to the POST request so the chat gets updated after we send a message.</p><p>Cool! Now we can send messages and receive them. But all of the messages are on the same line!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ijtIP84EICqDsgfl5Sfprg.png" /></figure><p>No big deal. We can fix this with just a few lines of code. All we need to do is add linebreaks to the message strings.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a6500ddd9c20bf49161d5ab9e8c59445/href">https://medium.com/media/a6500ddd9c20bf49161d5ab9e8c59445/href</a></iframe><p>Refresh the page and voila! We now have a working chatroom! I got some of my friends to join in the fun.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d86Htk1-r_B5MBlc_kBugA.png" /></figure><p>Simple! This was not intended as a full stack tutorial with good UX practices, but hopefully this gives you some ideas about how to use GraphQL in your applications! Happy coding!</p><p><a href="https://github.com/kkworden/express-graphql-chat">kkworden/express-graphql-chat</a></p><p>Thanks for reading! Peace ✌️️️️✌️✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bab2b98be21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using GraphQL and Node.js to Make a Basic Chat App]]></title>
            <link>https://medium.com/@kkworden/using-graphql-and-node-js-to-make-a-basic-chat-app-1ed2e6a7a6d3?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ed2e6a7a6d3</guid>
            <category><![CDATA[expressjs]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Mon, 10 Dec 2018 21:37:37 GMT</pubDate>
            <atom:updated>2018-12-16T20:08:15.795Z</atom:updated>
            <content:encoded><![CDATA[<h3>Using GraphQL and Node.js to Make a Basic Chat App — The Backend</h3><h4>A cool introduction to a hot technology</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Pz652MGdXILZcL-hamqpeg.png" /><figcaption>The GraphQL Logo</figcaption></figure><p>Quite a large hype surrounds GraphQL nowadays. Developers <a href="https://medium.freecodecamp.org/the-state-of-javascript-2018-8322bcc51bd8">feel the buzz and want to join the hive</a>. Put me on the list. I want to learn it, too! So today we are going to use GraphQL to set up a simple chatting website.</p><p>In this tutorial, we will set up the backend necessary to facilitate a chat app.</p><p>The <a href="https://medium.com/@kkworden/using-graphql-and-node-js-to-make-a-basic-chat-app-the-frontend-5bab2b98be21">next tutorial</a> will walk through the frontend setup and flesh out the application.</p><p>This tutorial assumes you have working knowledge with Node.js and Express. If you need to learn, <a href="https://www.tutorialspoint.com/nodejs/nodejs_express_framework.htm">look here</a>.</p><p>Let’s get started!</p><blockquote><a href="https://github.com/kkworden/express-graphql-chat">Click here to get the source code for this tutorial.</a></blockquote><h3>Why GraphQL?</h3><p>With GraphQL, you always know the shape of your data. Rather than writing your own JSON API, figuring out which fields you need in the returned JSON object, and programming in your own error-handling logic, you can simply write a <a href="https://graphql.org/learn/schema/">GraphQL schema</a> and write a resolver for each field in the schema. Errors are handled for you, and when you query your API, you know exactly what you will get back.</p><h3>Express and GraphQL</h3><p>We need to install a few basic dependencies in order to get up and running.</p><p>npm install -S express body-parser graphql</p><p>To make sure everything works, create a basic Express app and copy the GraphQL code <a href="https://graphql.github.io/code/#javascript">right off the GraphQL website</a>.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c180a3b330debd67b2a67861d66e8102/href">https://medium.com/media/c180a3b330debd67b2a67861d66e8102/href</a></iframe><p>When this runs we get some console output:</p><pre>$ node src/index.js</pre><pre>...</pre><pre>{&quot;data&quot;:{&quot;hello&quot;:&quot;Hello world!&quot;}}<br>App is listening</pre><p>Cool! But GraphQL will always print this out on server startup, no matter what we do. To make this logic more useful, move it into its own route:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/abc7e52434315dc36a5cdcb50314892e/href">https://medium.com/media/abc7e52434315dc36a5cdcb50314892e/href</a></iframe><p>Now when we POST to /api with a query field, the schema executes our query. However, we can save ourselves some headache. The express-graphql package already has a middleware for executing queries against the schema. Do the following:</p><p>npm i -S express-graphql</p><p>To neaten the code, move the schema into a separate schema.js file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b68f55242c42366083f9dad41b3fa168/href">https://medium.com/media/b68f55242c42366083f9dad41b3fa168/href</a></iframe><p>And let’s do the same for a resolvers.js file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d768df20dd0d9511a9ddd413ebe41061/href">https://medium.com/media/d768df20dd0d9511a9ddd413ebe41061/href</a></iframe><p>Then update the route code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/19623dfa374d9804ba62094d9342c585/href">https://medium.com/media/19623dfa374d9804ba62094d9342c585/href</a></iframe><p>The graphqlHTTP middleware handles the schema validation and resolver execution for us. Also note that the graphqlHTTP middleware has a graphiql field. When set to true, this allows us to navigate to <a href="http://localhost:8000/api">http://localhost:8000/api</a> and play around with queries. Start the server, navigate to the aforementioned page, and admire the magic!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5x-pDX42qbRjqcCQIqjbQA.gif" /></figure><p>We can easily extend this to house our chatting logic. All we have to do is update schema to define how our data looks, and update rootValue (our resolvers) to actually return the queried data. Simple in principle, so let’s get cracking!</p><h3>Defining our chat operations</h3><p>To make a useful chat API, we’ll need to define some basic operations. Of course, our users will need to be able to retrieve and send messages, so we will define two operations:</p><ol><li>Retrieve messages</li><li>Send messages</li></ol><p>For the sake of simplicity, we will forego user authentication. Our user will be able to choose an arbitrary nickname and start sending messages without any validation.</p><p>Let’s tweak the schema to define these operations:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/366adad7f757e5873595c55b42577f9f/href">https://medium.com/media/366adad7f757e5873595c55b42577f9f/href</a></iframe><p>Note that our schema now has two types of operations: the Query type, which we had before, and now a Mutation type. We define the sendMessage operation as a Mutation and define parameters to be passed to it. For the parameters, we define nickname and message as String types. The ! indicates that we <strong>must </strong>provide these arguments in our request- they cannot be null. The return type of the mutation is a Boolean, which we will return always as true.</p><blockquote>While we technically could define sendMessage as a Query, it is convention to have write operations defined as a Mutation. A Mutation must be executed serially, which is usually what you want. <a href="https://facebook.github.io/graphql/June2018/#sec-Mutation">See here for more information</a>.</blockquote><p>Then we need to tweak our resolvers. We define a simple array messages which will hold all of our messages in memory:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c5bd480fdb003aa583557c462fca243d/href">https://medium.com/media/c5bd480fdb003aa583557c462fca243d/href</a></iframe><p>The messages resolver will return the array of messages from our defined array, and sendMessage gives us the <a href="https://stackoverflow.com/questions/37661166/what-do-function-parameter-lists-inside-of-curly-braces-do-in-es6">destructured parameters</a> from our mutation, which we use to update the array. Obviously, in a real chat application, you may want to use a database or at least some sort of file hierarchy. But a simple array will do for demonstration purposes.</p><p>Regardless, this should work, so let’s send some messages!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*SRiqbSqahQYUCG1mxN9YEQ.gif" /></figure><p>Alright! Our GraphQL API is able to take data and return it! In the <a href="https://medium.com/@kkworden/using-graphql-and-node-js-to-make-a-basic-chat-app-the-frontend-5bab2b98be21">next tutorial</a>, we will build out a basic web interface so that we have an actual chat application!</p><p><a href="https://github.com/kkworden/express-graphql-chat">kkworden/express-graphql-chat</a></p><p>Thanks for reading! Peace ✌️️️️️✌️✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ed2e6a7a6d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I quit Facebook — and then rejoined]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kkworden/i-quit-facebook-and-then-rejoined-7583d196303f?source=rss-53aa98972fd------2"><img src="https://cdn-images-1.medium.com/max/1200/1*on_k9N1Ps3S5QLg5AUyAHA.png" width="1200"></a></p><p class="medium-feed-snippet">How quitting social media can give us a healthier perspective</p><p class="medium-feed-link"><a href="https://medium.com/@kkworden/i-quit-facebook-and-then-rejoined-7583d196303f?source=rss-53aa98972fd------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kkworden/i-quit-facebook-and-then-rejoined-7583d196303f?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/7583d196303f</guid>
            <category><![CDATA[society]]></category>
            <category><![CDATA[self]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Tue, 04 Dec 2018 12:31:00 GMT</pubDate>
            <atom:updated>2018-12-04T12:31:00.803Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What a Rogue Chatbot Can Teach Us About Ourselves]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@kkworden/what-a-rogue-chatbot-can-teach-us-about-ourselves-226760db133c?source=rss-53aa98972fd------2"><img src="https://cdn-images-1.medium.com/max/710/1*n0XOYI_RCQYjW5KuFaZTQQ.jpeg" width="710"></a></p><p class="medium-feed-snippet">First, nothing. Then, everything. A million messages per minute; a true deluge of dialogue. Tay suddenly found herself drowning in a sea&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@kkworden/what-a-rogue-chatbot-can-teach-us-about-ourselves-226760db133c?source=rss-53aa98972fd------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@kkworden/what-a-rogue-chatbot-can-teach-us-about-ourselves-226760db133c?source=rss-53aa98972fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/226760db133c</guid>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kenneth Worden]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 17:01:04 GMT</pubDate>
            <atom:updated>2018-11-28T05:26:03.000Z</atom:updated>
        </item>
    </channel>
</rss>