<?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 Justin Hough on Medium]]></title>
        <description><![CDATA[Stories by Justin Hough on Medium]]></description>
        <link>https://medium.com/@justinhough?source=rss-245280e6cbf5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*PWhV6P73W4YP3wWX.jpeg</url>
            <title>Stories by Justin Hough on Medium</title>
            <link>https://medium.com/@justinhough?source=rss-245280e6cbf5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 23:09:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justinhough/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[The Apps and Services We Use Everyday with a Multi-Location Team to Stay Connected and Awesome]]></title>
            <link>https://medium.com/@justinhough/the-apps-and-services-we-use-everyday-with-a-multi-location-team-to-stay-connected-and-awesome-847b01ea2f66?source=rss-245280e6cbf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/847b01ea2f66</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Justin Hough]]></dc:creator>
            <pubDate>Wed, 29 Apr 2020 16:18:24 GMT</pubDate>
            <atom:updated>2020-04-29T16:19:35.989Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HcKDkpkxFvhAIt91Tc83w.jpeg" /></figure><p>Since <a href="https://www.hounder.co/">Hounder</a> started we have always been working to improve and streamline our processes and workflows. Not only has this helped us to stay agile with our partners and clients, but it has helped us as we have started to grow our team.</p><p>Being highly collaborative and staying connected is difficult when you have multiple team members. Since we opened our second office in Boise, Idaho in 2019 it has made us even more aware that the tools and services need to help us move the needle forward.</p><h3>Communication</h3><p>Whether we are at the office, at a client meeting, waiting to board on a plane, drinking coffee at our favorite hipster location or anywhere for that matter we always need to make it easy to stay in touch with the rest of the team. For a remote team especially keeping those tools to a minimum has helped us all keep focus on what needs to get answered quickly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N4_YGHU2qEl2WrKD-oqalA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*QecG_xmGeiFhapwzRbL3sw.png" /></figure><h4>Asana</h4><p>Our project management tool of choice has been <a href="https://asana.com/">Asana</a> and our team finds it quick and easy to use. Using Asana we are able to plan our sprints in real-time and set deadlines for client support requests that come in. For the <a href="https://www.hounder.co/">Hounder</a> team even if we may not be on a particular project we can follow along and see every stage so that we never miss a deadline. You can start out using Asana for free and it has a good pricing tier for added features that your team might need.</p><p><a href="https://asana.com/">Manage your team&#39;s work, projects, &amp; tasks online * Asana * Asana</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*0pjenqMY2RAgJ5T2zmtC9w.png" /></figure><h4>Slack</h4><p>In working with a wide-variety of enterprise partners we have used a plethora of different communications platforms, but have been using Slack for the majority of our internal team communications. We do send the occasional email to work with clients but the slow nature of email responses tends to be the reason we keep using Slack. Most of time we use Slack to create quick daily scrums, check-in meetings for projects or that development discussion about a bug or talking how best to structure unit tests.</p><p><a href="https://slack.com/">AI Work Management &amp; Productivity Tools</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*VlKO37n5B3J_BWbdw6-0Fg.png" /></figure><h4>Zoom</h4><p>For online meetings or trainings that we need to both talk and see people we turn to Zoom, which we have integrated with Slack so that we can set up a new meeting in a few seconds and we are off and meeting. While most of us cringe at the idea of meetings and/or scheduling meetings there are those moments when meeting in person is ideal, but with Zoom while we may be separated by huge distances they have made it a breeze to be able to quickly jump on a call discuss what we need and get back to the rest our work easily.</p><p><a href="https://zoom.us/">One platform to connect | Zoom</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*zTW8WbVjIid4jDASFtYNsw.png" /></figure><h4>G Suite</h4><p>Probably one of the first decisions we made after buying a domain was to get Gmail setup for our email hosting. However, with our first couple clients we needed a good solution to collaborate on documents, spreadsheets and presentations that we were making and we found the real-time collaboration within G Suite to be perfect for our needs both then and now. Plus with the added sharing capabilities we are able to collaborate with our clients who also use G Suite within their own organizations so creating shares and managing documents has been a breeze to focus less on how to share and more time on providing great services. Though we also utilize a Synology DiskStation DS918+ as a backup for all our data and to provide a local development platform for our Developers to quickly setup a Docker container for testing and sharing with clients, but that is a discussion for another article.</p><p><a href="https://gsuite.google.com/">Google Workspace (Formerly G Suite): Business Collaboration Tools</a></p><h3>Design</h3><p>Our design process and tools has probably changed the most over the years and like development there is no set it and forget it approach because our design process is constantly evolving. For our clients we are always adapting and changing to challenge our processes in order to produce the best possible product for our clients needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6qTludQVinFOhcFRXNs7MQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*AS5eYdHH2bvRC5kM2bebOQ.png" /></figure><h4>Sketch</h4><p>For a majority of our UX and UI design projects we utilize Sketch which allows us to create reusable and dynamic components for prototyping. For most of us we especially get excited being able to use symbols that are more dynamic from buttons that we can change the text on or icon sets that allow us to select a different icon from a drop-down on the symbol has allowed us to customize our designs but keep a consistent structure with reusable components to take straight into the development phase. Plus the added benefit of being able to write or use plugins that extend the native features of Sketch has really opened up so many possibilities for creating beautiful web interfaces. So plugins like Anima Toolkit for creating timeline animations and Runner to add actions to our existing workflows.</p><p><a href="https://www.sketch.com/">Sketch · Design, prototype, collaborate and handoff</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/100/1*m5oBFG6L-26-q0U5KsIVPQ.png" /></figure><h4>Figma</h4><p>Another design tool that we have started to use and has really changed the way we think and build design components for the web has been Figma. One of the big things about Figma is centered around the idea of making every step of the process from design to development easier so that the hand-off is as seamless as possible. For our team we are all about collaboration and with Figma’s real-time collaboration tools we don’t need to use screen-sharing software to be able to share a design but only need to open a web link. Their approach to how to create a design system with reusable components is innovative with the ability to tie a master component directly to other similar components using layer overrides. With features like Auto Layout and additional plugins that can be added to extend functionality Figma we have found ourselves using more and more for designs so it may be our one interface design resource in the coming months.</p><p><a href="https://www.figma.com/">Figma: The collaborative canvas for design, code, and AI</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*V6emIvZkZ3u7hFJgWU3BQg.png" /></figure><h4>Photoshop</h4><p>Well, not sure I need to explain this one so much. We use Adobe Photoshop for serious photo editing or super custom image designs for various projects. Need we say more.</p><p><a href="https://www.adobe.com/products/photoshop.html">Official Adobe Photoshop - Photo &amp; design software</a></p><h3>Development</h3><p>We may spend time designing and prototyping cool interfaces and designs for our projects, but at the end of the day all those designs need to be built and become functional for our clients. When we get started on development we are serious about our coding environments and delivery. For all the other things we do enjoy testing out new platforms and services that deliver better web experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aY2vYXuBib48Ov2_iXDJqA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*XLEvSVeC9D42SnRNyM-GiA.png" /></figure><h4>Visual Studio Code</h4><p>For a long time we either Sublime Text or Atom when writing code, but with larger files and plugins we had installed with either noticed considerable slow down or frequent app crashing which is not always productive for a developer. When we saw that VS Code had released a Mac App we gave it a try and noticed that we were able combine a lot of apps into one interface that made us slightly more productive while watching Netflix at the same time. 🚀 For most of our projects we utilize code linting, testing and compiling with things like Webpack in order to keep our projects as optimized as possible. Plus since we all really enjoy plugins that extend core app functionality we started to peel back the onion more to see what we could add to VS Code to make our time developing that much more useful.</p><p>Some of the extensions that we use are:</p><ul><li>Git</li><li>Merge Conflict</li><li>Emmet</li><li>PHP CodeSniffer</li><li>TODO Highlight</li><li>Twig Language 2</li><li>VS Code Icons</li></ul><p>If you’re interested we run Hack for our font and Andromeda Bordered for our theme. We do enjoy dark themes.</p><p><a href="https://code.visualstudio.com/">Visual Studio Code - Build what comes next</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*qOzjkxTplXODnUBn1BinOg.png" /></figure><h4>Github</h4><p>For all our code repositories we use Github which allows us to write comments or issues, put in pull requests to merge new features and store code documentation right along with the source code. With the release of Github Actions we have been writing testing and deployment scripts directly in our repos that get pushed out to our various platforms more easily and without the need for an additional tool like Jenkins or Codeship. While we still use CI tools for more complicated deployment processes for multi-repo apps Github has been growing steadily in features and becoming a core place for our coding needs.</p><p><a href="https://github.com/">GitHub · Change is constant. GitHub keeps you ahead. · GitHub</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*7lMTNNXplY1aCOp1Dkia-w.png" /></figure><h4>Docker</h4><p>When building new apps or websites we needed a way to build in environments that closely mirrored our development or production environments and that we could port from one machine to another if necessary. With so many different developers and all using different machines it was important that we able to keep things consistent without worrying about what version of PHP a certain developer might be using or need to use. We also wrote custom scripts that allow us to scaffold projects quickly and get up and developing with very little headache. Plus the added benefit of being able to deploy those Docker containers to various services gives us the greatest flexibility to keep environments similar for testing and bug reporting.</p><p><a href="https://www.docker.com/">Docker: Accelerated Container Application Development</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/150/1*rfNbxzPhInuchN8CUAg9LQ.png" /></figure><h4>CrossBrowserTesting</h4><p>We don’t always use Windows or Macs so for more visual or even manual testing of bugs we turn to CrossBrowserTesting. Their interface allows us to spin up a quick instance of IE8 (or some other browser we dislike) to test a bug to get it fixed without having to setup our own virtual machines. They also provide some automated testing tools for visual testing that we use with other applications to compare screenshots so we can identify breaking changes that might have been introduced with a new feature or release.</p><p><a href="https://crossbrowsertesting.com/">Cross Browser Testing Tool: 2050+ Real Browsers &amp; Devices</a></p><h3>Fun Things</h3><p>As we work hard on various web projects we like to as a team or individually keep the fun in what we do each and every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*llAhd3g7dyp9Lz68C3OemQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*aUhzW3y2XqWk1x-mGO6R6g.png" /></figure><h4>Spotify</h4><p>On the fun side we do enjoy jamming out while designing and developing, but there are moments that we listen to a few of our favorite podcasts to either keep on top of code or hockey.</p><p><strong>Kes &amp; Juice Podcast</strong> (features two of the most respected and insightful NHL veterans in the Podcast world today — Ryan Kesler and Kevin Bieksa) <a href="https://open.spotify.com/show/4MV8cCTxg88sh9iS8CZN31">https://open.spotify.com/show/4MV8cCTxg88sh9iS8CZN31</a></p><p><strong>Syntax — Tasty Web Development Treats</strong> (features Wes Bos and Scott Tolinski who discuss a lot of different areas of coding) <a href="https://open.spotify.com/show/4kYCRYJ3yK5DQbP5tbfZby">https://open.spotify.com/show/4kYCRYJ3yK5DQbP5tbfZby</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/274/1*-u2yP6aVvu8XYSC8iE2PvQ@2x.png" /></figure><h4>Nozio</h4><p>When we need to stay focused on writing without getting distracted and there really isn’t any music that works well we turn on Nozio to curate the outdoors so we can focus more on the work before us.</p><p><a href="https://noiz.io/">Noizio - Calm, Meditate, Sleep</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*KRX0SmFtrCgFyAvGErV4DA.png" /></figure><h4>Be Focused</h4><p>Be Focused is is an unobtrusive task planner with a built-in timer. The built-in Pomodoro Technique timer of 25 minutes on and a five-minute break for each task helps us to stay focused and on the task at hand. It lets you track your progress and gain new insights about how long it takes you to finish specific tasks. You’d be shocked at how quick or long a routine task may take you. Knowing and understanding this helps you to plan out your day much more effectively.</p><p><a href="https://xwavesoft.com/be-focused-pro-for-iphone-ipad-mac-os-x.html">Xwavesoft - Be Focused</a></p><h4>Rocket</h4><p>Who doesn’t enjoy a good emoji. For those times when we aren’t in Slack or Github with built-in emoji keyboards we use Rocket. With a quick keystroke we can pull up the interface find an emoji and then put it where we need it, which is generally everywhere.</p><p><a href="https://matthewpalmer.net/rocket/">Rocket - the best emoji app for Mac</a></p><h3>What do you use to be more productive?</h3><p>If there are any apps, services or tools that you use everyday to make your day more productive we would love to hear about it. Send us a quick note on our website (<a href="https://hounder.co/contact">https://hounder.co/contact</a>) and let us know what you’re using or if there is something you think we should try. We are always interested to know what others are using and how it makes them more productive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=847b01ea2f66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating the Murky Waters of Web Accessibility and Compliance]]></title>
            <link>https://medium.com/hounder/navigating-the-murky-waters-of-web-accessibility-and-compliance-2270b83b1c14?source=rss-245280e6cbf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/2270b83b1c14</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Justin Hough]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 20:20:44 GMT</pubDate>
            <atom:updated>2020-01-23T20:20:44.997Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*BR1dGEDHe0r3hECc" /><figcaption>Photo by <a href="https://unsplash.com/@marvelous?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marvin Meyer</a> on <a href="https://unsplash.com/s/photos/website?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>Small side note.</strong> For those looking for the official and extensive resource on web accessibility standards then I would recommend reading the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines (WCAG)</a> which is the global standard for web accessibility and is also referenced when working with ADA (The Americans with Disabilities Act). The WCAG provides recommendations for using WCAG 2.0 and 2.1 along with other resources that aid in the process of ensuring your website is accessible.</p><p>Web accessibility is both a large and murky topic at the moment with so many companies and web sites coming under fire for not being accessible to individuals with disabilities. Being a web developer and working with several large enterprise companies has afforded me some insight into this topic and help others navigate the topic a little better. However, for those individuals or businesses that run web sites but don’t have ready access to development resources the topic of web accessibility can be about as easy as understanding tax law.</p><p>Web accessibility is an important topic and shouldn’t be overlooked when building a web site, however, it often goes neglected when launching new sites only because it isn’t fully understood what needs to be done in order to achieve it.</p><h3>What is WCAG 2.0?</h3><p>The Web Content Accessibility Guidelines or WCAG is basically the criteria that has been provided to understand what is considered accessible in regards to the web. WCAG also provides a <a href="http://www.w3.org/WAI/WCAG21/quickref/">checklist</a> for each area that may need to be addressed when looking to make your site accessible.</p><p>Within the standard there are 3 levels of compliance: A, AA, and AAA. Generally, using the AA standard is the best way to address the biggest barriers for helping users with disabilities navigate your web site since the level A only fixes the most basic issues of web accessibility.</p><p>The basic principles of WCAG 2.0 are:</p><ul><li><strong>Perceivable</strong>: information and user interface components must be presentable to users that they can perceive what is necessary (e.g., alt tags on images, transcripts for videos, and understandable text on form submit buttons)</li><li><strong>Operable</strong>: user interface components and navigation must be operable (e.g., you should be able to navigate pages with a keyboard, as well as, a mouse)</li><li><strong>Understandable</strong>: information and operation of the user interface must be understandable (e.g., text on error messages should explain the error or issue easily)</li><li><strong>Robust</strong>: content must be robust enough so that it can be interpreted reliably by a wide variety of user agents and assistive technologies.</li></ul><h3>Basic WCAG Breakdown for Areas to Cover</h3><p>The following list is a breakdown of all the various items that is provided by WCAG 2.0 and will help in creating both an understanding of what is being looked for and how to start implementing web accessibility standards on your web site.</p><ul><li><strong>Text alternatives </strong>— provide alternatives for non-text content, such as images. (e.g., images)</li><li><strong>Time-based media </strong>— for time-based media, such as audio or video, provide an alternative or transcript that provides equivalent information.</li><li><strong>Adaptable </strong>— create content that can be offered in different ways without loss of information.</li><li><strong>Distinguishable </strong>— make it easier for users to see and hear content by using readable or larger font sizes, using high-contrast colors on links and backgrounds.</li><li><strong>Keyboard Accessible </strong>— make all site functionality usable via a keyboard without any restrictions.</li><li><strong>Timing </strong>— provide ample time for users to read and use content.</li><li><strong>Seizures </strong>— do not use or include design elements that are known to cause seizures, such as rapid flashing.</li><li><strong>Navigable </strong>— provide multiple ways for users to navigate content either by prominent links or being able to use tabs on a keyboard.</li><li><strong>Readable </strong>— make text content readable and understandable with styles.</li><li><strong>Predictable </strong>— make your web site and pages appear and operate in predictable ways.</li><li><strong>Input Assistance </strong>— assist users with their web experience by correcting mistakes or describe errors in text</li><li><strong>Compatible </strong>— provide increased compatibility with current and future user agents and assistive technologies.</li></ul><h3>Use a Tool to Check your Web Site</h3><p>While the information provided above is only a primer towards understanding web accessibility and getting started with implementing it there still requires a place to start from. There are several tools that provide web accessibility checks and I would recommend looking at more than one in order to ensure that one tool is not missing something that another might cover.</p><p>Plus having a list of items to start working on with a web developer or agency is great way to get the conversation started on what is needed to make your site accessible and ready for the future.</p><p>For our own testing and projects we utilize a tool called <a href="https://developers.google.com/web/tools/lighthouse/">Lighthouse</a> by Google that provides not only accessibility checks, but also looks at other criteria: performance, best practices, and search engine optimizations (SEO). It has provided for our team a good way to continually check and test any new changes against having any issues before it reaches the public.</p><p>Some other useful web accessibility tools:</p><ul><li><a href="https://www.webaccessibility.com/">Web Accessibility by Level Access</a></li><li><a href="https://wave.webaim.org/">WAVE Web Accessibility Evaluation Tool</a> (provides a visual view of the actual web page with examples)</li><li><a href="https://achecker.ca/checker/index.php">Web Accessibility Checker</a></li></ul><h3>Are you interested in more?</h3><p>At <a href="https://www.hounder.co/">Hounder</a>, we work on a wide variety of web projects across e-commerce, startups, enterprise and more to ensure that everything we develop is clean, tested, scalable, and accessible for all users. We have spent a lot of time iterating and adapting our coding practices to provide the best possible user experiences.</p><p>If you’re interested in learning more about what Hounder can offer then check out our <a href="https://www.hounder.co/services/ada-website-compliance-accessibility-consultant-services-company">ADA Website Compliance and Accessibility Services</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2270b83b1c14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hounder/navigating-the-murky-waters-of-web-accessibility-and-compliance-2270b83b1c14">Navigating the Murky Waters of Web Accessibility and Compliance</a> was originally published in <a href="https://medium.com/hounder">Hounder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Reusable Front-end Development Project using Webpack and Tailwind CSS]]></title>
            <link>https://medium.com/hounder/building-a-reusable-front-end-development-project-using-webpack-and-tailwind-css-df1bddbce59?source=rss-245280e6cbf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/df1bddbce59</guid>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Justin Hough]]></dc:creator>
            <pubDate>Sat, 14 Sep 2019 19:39:20 GMT</pubDate>
            <atom:updated>2019-09-14T19:39:20.230Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Liu41_SATREQcDUG-Ld1Vw.png" /><figcaption>Creating a project with webpack and TailwindCSS in VS Code.</figcaption></figure><p>One of the areas that a web developer will spend the most time learning is a build system or process to streamline their directory own local development process. When I first started working with task runners I was using Grunt to automate tasks, such as compiling Sass, bundling JavaScript, and optimizing images. However, what amazed me was that all the same tasks that I ran locally to develop could be run before deploying to a production website using a Git repository.</p><p>The idea of using a task running or having a build process might be scary for some, but when working with one or multiple developers at a time on a single project it allows for everything to be kept in sync with a unified process that can be run on your computer or any number of other development machines in the same way.</p><p>Over the years and after having spent so much time in different development platforms like Drupal, Wordpress, and more I tried to find ways to remove as many extraneous pieces as I could to streamline my development processes. I started using Grunt and Gulp and eventually ditched those in favor of using Node packages directly with CLI commands within package.json to make it easier and eventually developed my responsive framework, called <a href="https://github.com/justinhough/Centurion">Centurion</a>, from scratch. It was a way to develop and learn a way to standardize a set of reusable classes and components for a wide variety of projects that I was working on. The rationale behind <a href="https://github.com/justinhough/Centurion">Centurion</a> will remain a discussion for another post, but suffice to say I am working on resurrecting it for some amazing new projects down the road. So stay tuned!</p><p>As of the publishing of this article, the process that I use primarily for development is <a href="https://webpack.js.org/">Webpack</a> and <a href="https://tailwindcss.com/">Tailwind CSS</a>. I won’t go into much detail about the benefits and drawbacks of each since there are plenty of articles across the internet that already discuss that in length, such as, <a href="https://webpack.js.org/concepts/why-webpack/">Why Webpack</a> and <a href="https://blog.algolia.com/redesigning-our-docs-part-4-building-a-scalable-css-architecture/">Building a Scalable CSS Architecture</a>.</p><p>If you’ve never used either then I would recommend you check out both projects and how they might help your current development projects. All the code that I have outlined in the walkthrough below is available on Github — <a href="https://github.com/Hounder-Co/webpack-tailwind-starter">https://github.com/Hounder-Co/webpack-tailwind-starter</a>.</p><h3>Getting Started</h3><p>The process of setting up a starter Node project with webpack is relatively straightforward and you as of webpack 4 you technically don’t need a webpack config file to use it.</p><p>If you’d like to learn more about the configuration options in webpack then check out <a href="https://webpack.js.org/concepts/">https://webpack.js.org/concepts/</a>.</p><ol><li>Create a project directory.</li><li>Within the project, initialize a node project npm init -y</li><li>Now we can install webpack: npm i --save-dev webpack webpack-cli</li><li>Create a file in the root of the project named: webpack.config.js</li></ol><pre>const path = require(&#39;path&#39;);</pre><pre>module.exports = {<br>  entry: &#39;./src/js/source.js&#39;,<br>  output: {<br>    path: path.resolve(__dirname, &#39;dist&#39;),<br>    filename: &#39;./dist.bundle.js&#39;<br>  },<br>  module: {<br>    rules: []<br>  },<br>  plugins: []<br>};</pre><p>5. Add an npm script to package.json so that we can run webpack from the command line.</p><pre>{<br>  ...</pre><pre>&quot;scripts&quot;: {<br>    &quot;dev&quot;: &quot;webpack --config webpack.config.js --mode development&quot;<br>  },</pre><pre>&quot;devDependencies&quot;: {...}<br>}</pre><p>6. Now we can run webpack using npm run build .</p><h3>Setting up Loaders and Tailwind CSS</h3><p>Now that we have a basic webpack project ready we can start having some fun. One thing to note is that natively webpack only understands JavaScript, so if we wanted to add CSS or image files it wouldn’t know what to do with them. This is where loaders come in, which allow webpack through the use of external modules to the necessary functionality to run PostCSS and even optimize images found within CSS files.</p><p>So now we are going to configure webpack to bundle our JS using Babel, compile CSS, optimize images and fonts, and output a bundled CSS file.</p><h4>Install and Configure Babel</h4><p><a href="https://babeljs.io/">Babel</a> is a JavaScript transpiler that will allow us to write modern JavaScript that is converted to be backward compatible with current and older browsers.</p><p>npm i --save-dev babel-loader @babel/core @babel/preset-env</p><p>Within your webpack.config.js we will add the following snippet. This will allow us to compile any JS file found in our source directory and bundle it using Babel.</p><pre>{<br>  // Apply rule for .js<br>  test: /\.js$/,<br>  exclude: /(node_modules)/,</pre><pre>// Set loaders to transform files.<br>  use: {<br>    loader: &#39;babel-loader&#39;,<br>    options: {<br>      presets: [&#39;@babel/preset-env&#39;]<br>    }<br>  }<br>},</pre><h4>Install PostCSS and Tailwind CSS</h4><p><a href="https://postcss.org/">PostCSS</a> is a tool that transforms styles with JavaScript plugins. The reason I chose to use PostCSS rather than say Sass is that in more recent years with the releases in CSS 3 most of the features that make Sass powerful are implemented natively into modern browsers. For all the other key features that you might need I am going to say that there is probably a “<a href="https://www.postcss.parts/">plugin for that</a>” which will accomplish the same thing. Allowing all of us to get back to writing CSS.</p><p>npm i --save-dev postcss-loader postcss-import css-loader mini-css-extract-plugin autoprefixer cssnano tailwindcss</p><p>Under rules we can now configure webpack to let it know how we want it to handle our CSS files, which will be to use PostCSS and then output an extracted CSS file into our dist directory.</p><pre>{<br>  // Apply rule for .css files<br>  test: /\.css$/,</pre><pre>// Set loaders to transform files.<br>  use: [<br>    { loader: MiniCssExtractPlugin.loader },<br>    { loader: &quot;css-loader&quot;, },<br>    {<br>      loader: &#39;postcss-loader&#39;,<br>      options: {<br>        ident: &#39;postcss&#39;,<br>        plugins: [<br>          require(&#39;tailwindcss&#39;),<br>          require(&#39;autoprefixer&#39;),<br>        ],<br>      },<br>    }<br>  ]<br>},</pre><p>Before we move on we need to ensure that we have included in our plugins the necessary plugin that will allow us to extract all CSS from our bundled JavaScript file and output a bundled CSS file. At the bottom of our webpack.config.js file inside of plugins we will add the following:</p><pre>plugins: [<br>  <br>  new MiniCssExtractPlugin({<br>    filename: &quot;dist.bundle.css&quot;<br>  })</pre><pre>]</pre><p>Before we can proceed we need to make sure that it’s required so webpack will know what it is. Right after const path near the top of the file add: const MiniCssExtractPlugin = require(&quot;mini-css-extract-plugin&quot;).</p><h4>Optimizing Images within CSS</h4><p>When developing applications or themes there are times when you may need to include images directly into your CSS files, but sometimes these images get forgotten about and end up taking huge amounts of space or have extraneous pathways that might not work in production environments. To solve these two issues we can now have webpack scan our CSS files for images and replace them with optimized, GUID referenced versions. The one great feature about this is that with a generated GUID it will prevent the browser from referencing an older image file with the same name since it will update the GUID each time webpack is run.</p><p>Let’s first install the necessary packages npm i --save-dev file-loader image-webpack-loader.</p><p>Then add the following to the rules section in our webpack.config.js.</p><pre>{<br>  // Apply rule for images<br>  test: /\.(png|jpe?g|gif|svg)$/,</pre><pre>// Set loaders to transform files.<br>  use: [<br>    {<br>      loader: &quot;file-loader&quot;,<br>      options: {<br>        outputPath: &#39;images&#39;<br>      }<br>    },<br>    {<br>      loader: &#39;image-webpack-loader&#39;,<br>      options: {<br>         mozjpeg: {<br>          progressive: true,<br>          quality: 65<br>        },<br>        // optipng.enabled: false will disable optipng<br>        optipng: {<br>          enabled: false,<br>        },<br>        pngquant: {<br>          quality: &#39;65-90&#39;,<br>          speed: 4<br>        },<br>        gifsicle: {<br>          interlaced: false,<br>        },<br>        // the webp option will enable WEBP<br>        webp: {<br>          quality: 75<br>        }<br>      }<br>    }<br>  ]<br>},</pre><p>You now can optimize CSS referenced images and output optimized versions.</p><p>Though we aren’t done, yet. We need to do some cleanup and make sure our dist folder doesn’t get out of control.</p><h4>Clean Your Project Before Each Compile</h4><p>A good thing to keep in mind is to ensure that your dist directory is clean each time we run webpack. If you don’t do this you may notice that generated files, such as our optimized images might start piling up duplicates quickly. So now we need to clean out the output folder before we run webpack to ensure that we have the latest and greatest versions of our code.</p><ol><li>Install npm i --save-dev clean-webpack-plugin</li><li>Require it in webpack const { CleanWebpackPlugin } = require(&#39;clean-webpack-plugin&#39;);</li><li>Then add it under plugins.</li></ol><pre>plugins: [</pre><pre>new CleanWebpackPlugin(),<br>  <br>  new MiniCssExtractPlugin(...)</pre><pre>]</pre><h3>Go Forth and Develop</h3><p>From here you should be able to use this starter to start adapting either your current web projects or start brand new ones from scratch. However, one thing to keep in mind is that this is not meant to be a set it an forget it type of starter. Depending on the project structure you can adapt this to work with theme building for Drupal or Wordpress or even to work with React apps to build something awesome.</p><h3>Are you interested in more?</h3><p>At <a href="https://www.hounder.co/">Hounder</a>, we spend a lot of time iterating and adapting our coding styles to ensure that everything we build is clean, tested and scalable. We work on a wide variety of web projects across e-commerce, startups, enterprise and more. If you’re interested in learning more than check us out</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df1bddbce59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hounder/building-a-reusable-front-end-development-project-using-webpack-and-tailwind-css-df1bddbce59">Building a Reusable Front-end Development Project using Webpack and Tailwind CSS</a> was originally published in <a href="https://medium.com/hounder">Hounder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[James McClung: Artist]]></title>
            <link>https://medium.com/hounder/james-mcclung-artist-e285a9686d6c?source=rss-245280e6cbf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e285a9686d6c</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[Justin Hough]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 22:39:00 GMT</pubDate>
            <atom:updated>2019-04-30T22:39:00.834Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hounder Artist Spotlight</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*AZ5d6zN4wfTafg826TQQmg.jpeg" /></figure><p><em>James McClung has quickly established himself as a sought after artist in the contemporary art and graphic design communities. He’s worked with clients such as </em><a href="https://www.stereosoundagency.com/"><em>Stereo Skateboards</em></a><em>, </em><a href="http://www.parliamentchocolate.com/"><em>Parliament Chocolate</em></a><em>, </em><a href="https://lifeandthyme.com/"><em>Life &amp; Thyme,</em></a><em> </em><a href="https://augies.coffee/"><em>Augie’s Coffee</em></a><em>, Wheel House LA., and </em><a href="https://strawfoothandmade.com/"><em>Strawfoot</em></a><em>, among others.</em></p><p>Josh from <a href="https://www.hounder.co/">Hounder</a> caught up with James to talk about some fresh topics that entrepreneurs are facing. Here is a look into that conversation.</p><p><strong>James, your work has been full of variety over the years. From ink, acrylic, pencil sketches, to endless types of papers and canvases. What influences you?</strong></p><p>I feel like there is a variety of aspects in my surroundings as well in unknown places that I’ve had the opportunity to travel to that has caught my eye the past couple years. From a building that seems somewhat out of place to a image of a woman walking by a sign that couldn’t be better timing in a perfect composition (picture a Wes Anderson movie clip here*). Artists such as Evan Hecox, and Geoff Mcfetridge have influenced my work for many years. Lately I’ve been digging in to the work of Ed Rusha and Jonas Wood.</p><p><strong>You took the plunge 6 years ago to leave your “day-job” to focus on your passion, your artwork. When do you think someone should just go for it? How do they know they are ready?</strong></p><p>For me I felt that I had a community of local business owners who were wanting to work with me to the point it was like having another job. It truly felt like it was time when there was communication almost every day of the week for upcoming projects etc.</p><p><strong>What’s your advise to artists who are trying to build a list of clients right now! How do you seek out opportunities?</strong></p><p>Build relationships. I think to get started it truly comes down to again having a community. Once you have a solid foundation where you are then it’ll be time to spread your wings and branch out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*-5BiF6pJE7FDIT1YHTst7A.jpeg" /></figure><p><strong>Pricing work can be tricky. From charging too little, too much, or simply not knowing what your work is worth. How do you price your work?</strong></p><p>This has always been a tricky one. But, when it seems like you’re desperate for some cash, try your best to stand by your worth. And I think you really cant put a price on anyones work or “worth”. I sold my first painting for $20 back in 2003. Since then I’ve always increased the price accordingly 30–50%. To me it’s not really about the hours or size of a work of art. It’s more about all the years of experience you’ve had to get to that point.</p><p><strong>Do you ever have periods where you feel a little bit disconnected from your work, or where you burn out? How do you deal with those?</strong></p><p>Almost every piece I work on haha. There always seems to be a mid point in a new piece of work where it feels like Im trudging along to complete it. Most of the pieces I do are pretty tedious and time consuming. Over the years I’ve had to learn to adapt to the mind set of being patient for the final out come and not rush through a new painting. It took a lot of years to being ok with working on one piece at a time.</p><p><strong>Overall, why do you do what you do, and why do you love it?</strong></p><p>I love a good story. I aspire to do my best to create some connection with people with each new series I work on. Since 2015 I’ve worked on 5 different projects that in a way connect to each other. Like chapters in a biography book. They’re all really about what it is I’m going through at the time. I think people really connect or fall in love with a image that has some kind of personal story to it. Lately I’ve been really focused on creating a narrative as well pushing my abilities in each new piece.</p><p>You can follow and see more of what James is up to on <a href="https://www.instagram.com/jmsmcclng/">Instagram</a>, <a href="http://vimeo.com/jamesmcclung">Vimeo</a> or on <a href="https://jamesmcclungart.com/">his website</a>.</p><p>If you want to keep in touch with <a href="https://www.hounder.co/">Hounder</a> you can follow us on <a href="https://www.instagram.com/hounder.co">Instagram</a> or <a href="https://twitter.com/hounderco">Twitter</a> or <a href="http://eepurl.com/cr1mar">subscribe to our amazing newsletter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e285a9686d6c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hounder/james-mcclung-artist-e285a9686d6c">James McClung: Artist</a> was originally published in <a href="https://medium.com/hounder">Hounder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a Design System]]></title>
            <link>https://medium.com/hackernoon/how-to-build-a-design-system-8574fbe93734?source=rss-245280e6cbf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8574fbe93734</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[agency]]></category>
            <dc:creator><![CDATA[Justin Hough]]></dc:creator>
            <pubDate>Thu, 18 Apr 2019 13:11:00 GMT</pubDate>
            <atom:updated>2019-04-18T13:11:00.824Z</atom:updated>
            <content:encoded><![CDATA[<h4>Semantics, syntax, accessibility, tone, and context that provide a base for a shared design language — benefits, drawbacks, and examples.</h4><h4>When do you start building a design system, where should you start? It can be difficult to know when the best time to start implementing a new process into your current workflow.</h4><p>Plus, there are a lot of areas to consider when starting from scratch and what should be built first — in terms of style guides, pattern and component libraries, and design systems. With each floating around it can be hard to where to start. While there are benefits to building a design system there are also downsides, however, we will discuss both the good and the bad — since they each depend on what you are looking to solve with a design system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kP80wBJzaX78DRnp3YcNFA.jpeg" /></figure><h3>The Difference Between Style Guides, Pattern Libraries, and Design Systems</h3><p>While style guides, pattern or component libraries, and design systems on the surface may appear to be similar each has its own use and purpose, but they can also be considered as pieces of a design system. At <a href="https://www.hounder.co/">Hounder</a>, we have lots of experience <a href="https://www.hounder.co/services/enterprise-design-systems">building design systems</a> that allow our partners to grow and to help you better understand the differences between all the options here are some brief explanations about each.</p><h4>Style Guides</h4><p>Are generally where we organize the actual styles and brand that our company uses every day, which will contain fonts, typography, icons, logo, grid layouts and spacing (margin and padding). For example, when an organization has a specific guidelines on how to place a logo, dimensions, size and/or colors to utilize then this is comprised within a style guide.</p><h4>Pattern and Component Libraries</h4><p>Are an organized set of related and reusable components that can contain code examples, design guidelines, and use cases for where / when to use each pattern or component. It’s better to visualize patterns as a collections of components. For example, a pattern for the homepage banner may contain headings, text, background images or video, and buttons which each on their own are seen as components.</p><h4>Design Systems</h4><p>Contain a set of semantics, syntax, accessibility, content tone, and context that provide a base for a shared design language. For example, a design system is generally where designers identify how to communicate through the use of the style guide and component library so that when they are designing new patterns or colors it all cohesively fits together.</p><p>When we think about each of these separately we can see that they each have their own distinct use cases and purpose, but collectively they each fit together to create a cohesive and what I like to think of as a shared language that can bring disparate teams (design, development, marketing) together. In the long run a design system is only a piece of the puzzle in bringing teams together since open communication and adoption are the real keys to having a successful design system.</p><h3>Getting Started with Design Systems</h3><p>While it might be nice to blankly say, “Everyone needs a design system.” While there are advocates on both sides of the fence when looking to build or not build a design system we should look rather at the benefits and the drawbacks to see if building a design system in your organization works. I first talk about the common drawbacks that are presented when talking about design systems and then I will discuss how a design system could benefit your organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BhsZq_fAGKRdLpTom--48Q.jpeg" /></figure><h3>Drawbacks of Building a Design System</h3><h4>1. Constrains designers and becomes inflexible over time</h4><p>When talking about constraints in terms of a design system it can make sense that building in a component and pattern based system will stagnate designers and constrain them to make new and more engaging experiences. When starting a new design with a partner we discuss how their current design process works and usually we begin to see repeatable patterns that can be moved into a design system. This extra time gained by the designer tends to allow them more creative freedom to build new features rather than building the same page layout again with different colors or imagery.</p><h4>2. It takes too much time to build a design system</h4><p>There is definitely a good amount of time spent to discuss, research, and implement a design system properly and when getting to engage with support from teams throughout the organization to start using it can be difficult. However, for this particular drawback this is more of a concern of upfront time spent, because a well implemented and communicated design system can actually start paying for itself in team efficiency quite quickly.</p><h4>3. Outdated designs and components</h4><p>When a concern over outdated designs or components is brought up with our partners it tends to lean more towards communication and engagement with the teams that will be utilizing the design system. We have seen quite a few style guides and pattern libraries created and then quickly abandoned because there was never really good engagement for those systems in the beginning and this is a hurdle to overcome in order to prevent a design system from being unused and forgotten.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bA4H1rCSvzn14KtTCDqh8g.jpeg" /></figure><h3>Benefits of Implementing a Design System</h3><h4>1. Allows for designs to be modular and reusable</h4><p>As design becomes more modular and reusable through patterns and components it actually allows designers and developers more time and freedom to build new features. Also, an added benefit is that when dealing with modular designs it means that only one area needs to be updated to fix a bug and can be tested in one spot rather than having to check, update, and test individual pages.</p><h4>2. Greater efficiency to build new features</h4><p>When a new feature is needed a designer can quickly mockup what is needed and a developer can build that feature with greater ease since code and testing is integrated directly into the design system so everyone can benefit from the new feature once it’s released.</p><h4>3. Better communication between designers and developers</h4><p>Before we started implementing design systems it was common to see a design created and then handed off to development to build with spec sheets that could sometimes be different depending on the designer and then implemented differently depending on the developer that received the update. Within a design system designs are spaced against pre-existing patterns and rules that everyone understands and when a component is developed the entire team is reviewing those updates within a repeatable, testable environment that allows for bugs or issues to be found more quickly. This type of workflow has led to better communication between designers and developers because of a shared knowledge and experience that everyone can see.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vN84I3T_CDE-CPHb4fYZ4A.jpeg" /></figure><h3>Our Process for Building a Design System</h3><p>Our process for building a design system is very similar to the approach that we take for most of our development projects. We start with discovery and research, breakdown timeline, identify technology, develop and test, and then finally run QA testing.</p><p>For a design system process we start by researching the brand and talk with the design and development teams along with a key stakeholders from other areas of the organization to gather as much research and information about what is needed. This can generally include survey’s or questionnaires that get sent out to individuals in the organization and we also conduct on-site interviews to talk face to face with stakeholders.</p><p>Once we have collected all the necessary information we need then we start identifying timeline, technology stacks and overall the workflow for building and maintaining the design system. We work in conjunction with the identified teams and stakeholders to identify key areas of the design system that will be touched daily and then discuss workflows that would benefit their own internal processes when updating the design system.</p><p>From there we move on to actually building the design system which involves building in all the necessary styles, branding and content that is identified. During this part of the process is where we start architecting tests for each component and pattern that is easily tested against and using visual regression testing tools we are able to capture and identify changes quickly that the team can review during an update and either approve as a valid change or reject as a bug that needs to be fixed. We believe in visual regression testing for a design framework because this is less reliant individual users remembering or comparing old to new code or designs that are generally missed during the review process.</p><p>Once all the necessary content, patterns, components and designs are in place and tested against we do a hand-off with our partners that involves training on how to use, update and overall maintenance of the design system.</p><h3>Design System Examples</h3><p>A great resource to bookmark is <a href="http://styleguides.io/examples.html">Website Style Guide Resources</a>, which has examples from a wide variety of organizations that have put their style guides, pattern libraries and design systems online for the public to see. A few of our favorites are:</p><ul><li><a href="https://www.carbondesignsystem.com/guidelines/accessibility/overview">IBM Carbon</a></li><li><a href="https://polaris.shopify.com/">Shopify Polaris</a></li><li><a href="https://rei.github.io/rei-cedar-docs/">Cedar REI</a></li><li><a href="https://www.lightningdesignsystem.com/">Lightning Salesforce</a></li><li><a href="http://ux.mailchimp.com/patterns/">Mailchimp</a></li><li><a href="https://alistapart.com/about/style-guide">A List Apart</a></li></ul><h3>Are you interested in Design Systems?</h3><p>At <a href="https://www.hounder.co/">Hounder</a>, we enjoy working on a wide-variety of different design and development projects and <a href="https://www.hounder.co/services/enterprise-design-systems">building design systems</a> are great because a great design system helps to bridge them both together.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fdde502%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fhackernoon%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href">https://medium.com/media/3c851dac986ab6dbb2d1aaa91205a8eb/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8574fbe93734" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-build-a-design-system-8574fbe93734">How to Build a Design System</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Get It Done]]></title>
            <link>https://medium.com/@justinhough/get-it-done-a22c8d82b816?source=rss-245280e6cbf5------2</link>
            <guid isPermaLink="false">https://medium.com/p/a22c8d82b816</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Justin Hough]]></dc:creator>
            <pubDate>Fri, 05 Jun 2015 16:00:17 GMT</pubDate>
            <atom:updated>2015-06-05T16:01:36.427Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ROcGOK4S4HaHhCro.jpg" /></figure><p>Over the last year, there have been two things that I have been dreaming about doing. First, write a book about development and second, going back to doing freelance work. Both are steadily becoming a reality as I start working on projects that better align with those goals. A lot of people these days want to be their own bosses and set their own hours, but to break that mold I would rather work on projects and take opportunities that allow me to build amazing web experiences for clients. The taste of that eventual goal was beginning to get to hard to pass up in my current work environment, which involves spending most of my time making sure experiences don’t break and the rest of the time fixing the experiences that have broken. We all should be able to work on projects we’re passionate about, right?</p><p>A few months ago I started with that question in mind then the answer was solidified when I read a post from Paul Jarvis, “<a href="https://pjrvs.com/a/shit">Stop doing shit you don’t like</a>”. To sum up that article we should all stop the things that we allow to take our time, stop being a “yes” man, and start looking at what makes us happy. We all know what we don’t like better than anyone, but it gets harder to figure out what we truly want to do that makes us enjoy our work. After doing a reassessment myself two things stood out, which were front-end development and responsive design. Okay, now I had my passions. What the heck was I supposed to do after?</p><p>Though simply saying, “Get it Done” doesn’t mean much if I don’t set goals to reach and drive the direction I wanted to go. A great habit to get into is to plan your days and your weeks beforehand. At the end of each day figure out what you need to do the next day to feel accomplished or successful. If sending emails to clients, working a few hours on a project, and writing a chapter of your book is what makes you feel successful then put those down. Now think about the things that you “really” have to do that may not be as fun, but are a necessary part of getting paid. Leave wiggle room for the fiery curveballs (projects with high value with a quick turnaround) that get thrown your way without fail. They happen so you might as well allow time for those moments.</p><p>For myself I sit down every day or at the end of the week before hitting the weekend to plan what needs to be done the next day or week. This habit helps to visualize and correct your goals, plus when you start the week after a long weekend you’re not trying to figure out what you need to do. Now you have the plan you only need to start. Another thing to note is that the weekends are for recharging, spending time with family or friends, and doing an activity that is not work related at all. Don’t spend your weekends working and allow yourself to recharge your batteries to tackle the tasks that you already know are coming. You can spend all your time preparing and getting ahead of yourself, but the time you take to rest is more important than being 3 days ahead of schedule.</p><p>In the end, figuring out a plan that works best for you and your dream is the hardest part of making a dream a reality. The more you venture towards getting to the tasks and milestones of achieveing that dream is one step further away from the moments that you might don’t like. Keep in mind that the planning and prepping stage is never fun work, but it falls on the necessary side of any goal since those are the moments that see you through the darker days of getting to your dream.</p><p>So go get it done already.</p><p><em>Originally published at </em><a href="http://www.justinhough.com/writing-the-journey/get-it-done"><em>www.justinhough.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a22c8d82b816" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>