<?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 Andrew on Medium]]></title>
        <description><![CDATA[Stories by Andrew on Medium]]></description>
        <link>https://medium.com/@shellscape?source=rss-a90ccd0747d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*T3qZ-d-yYwI1MQUC.jpeg</url>
            <title>Stories by Andrew on Medium</title>
            <link>https://medium.com/@shellscape?source=rss-a90ccd0747d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:56:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shellscape/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[Plugin to a Fresh Webpack Development Server]]></title>
            <link>https://medium.com/dailyjs/plugin-to-a-fresh-webpack-development-server-a8d4b859aa78?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8d4b859aa78</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[servers]]></category>
            <category><![CDATA[npm]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 20:30:57 GMT</pubDate>
            <atom:updated>2019-01-02T17:51:14.778Z</atom:updated>
            <content:encoded><![CDATA[<p>The developer experience is something that should be continuously improved upon. It is after all, just as important to the daily lives of developers as the user experience is to end-users of our efforts. For bundlers, a great development server and the experience that goes along with one is crucial.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*VsPIJe2WmJ_Nl-JxFjJLhg.jpeg" /><figcaption><em>Ice Skating Waiter, via </em><a href="http://historydaily.org/ice-skating-cocktail-waiters"><em>http://historydaily.org/ice-skating-cocktail-waiters</em></a></figcaption></figure><p>Nearly a year ago, I sat down to try and remedy the development server experience for <a href="https://www.npmjs.com/package/webpack">Webpack</a> by authoring webpack-serve. The <a href="https://www.npmjs.com/package/webpack-serve"><em>webpack-serve</em></a> project was meant to be a complete replacement for <em>webpack-dev-server</em>; a project that suffers from oodles of quirks and edge cases, development stagnation, extreme legacy support requirements, and an aging architecture increasingly difficult to maintain.</p><p>Unfortunately, what started as an effort to simplify with <em>webpack-serve</em> was revealed to have its own shortcomings. It was too large a departure from what devs had come to expect, many concepts behind it were too abstract, and it just tried to be too fancy.</p><p>Following a handoff to the Webpack organization, it was sadly, immediately deprecated <em>(For users of webpack-serve, the project is now being maintained on </em><a href="https://github.com/shellscape/webpack-serve"><em>this fork</em></a><em>).</em> For all of its faults, <em>webpack-serve</em> was still a step above <em>webpack-dev-server</em>, and was a step in the right direction.</p><p><strong>From all that has emerged </strong><a href="https://github.com/shellscape/webpack-plugin-serve"><strong>webpack-plugin-serve</strong></a><strong> - A Development Server fully-contained in a Webpack plugin.</strong></p><h3>Code Cadre Confab</h3><p>Unbeknownst to me, there was a solid chunk of users who enjoyed what webpack-serve was trying to accomplish. In late September I was approached by a few talented Brazilian developers who were super bummed about Webpack’s decision to shutter webpack-serve. Their idea was to, at the least, fork and maintain webpack-serve. For their taste, webpack-serve was a better choice than webpack-dev-server, despite its own set of quirks. And so we talked about how a fork might look. The idea quickly emerged that this could be a platform to launch a standard experience for many bundlers, not just restricted to Webpack, and it could be accomplished within a plugin.</p><p>Targeting Webpack was the most logical starting point. We had a lot of accumulated knowledge about how a server should and shouldn’t interact with Webpack compilers and bundles, and of maintaining webpack-dev-server and authoring webpack-serve. Between that and the real-world, day-to-day user perspective that Matheus and Sibelius were able to provide, we were able to create something really great.</p><p>Much of this plugin is just “plumbing,” but it’s how that plumbing is arranged that makes this project a stand-out in the space.</p><blockquote><strong><em>Our contributing team on this effort consists of:</em></strong></blockquote><blockquote><a href="https://twitter.com/bebraw"><em>@bebraw</em></a><em><br></em><a href="https://twitter.com/sseraphini"><em>@sseraphini</em></a><em><br></em><a href="https://twitter.com/matheus1lva"><em>@matheus1lva</em></a><em><br></em><a href="https://twitter.com/shellscape"><em>@shellscape</em></a></blockquote><blockquote>(And let me just say how great working with those folks it is! Please give them a follow.)</blockquote><h3>Scintillatingly Savory</h3><p>If you’re new to Webpack, it would be a great move to read up on <a href="https://webpack.js.org/concepts/plugins/">how to use Plugins</a>. webpack-plugin-serve is a Webpack Plugin, a self-contained development server triggered by a Webpack build, and part of the Webpack process. Users must add an instance of the plugin to their Webpack configuration. A configuration might look something like this:</p><pre>const { WebpackPluginServe: Serve } = require(&#39;webpack-plugin-serve&#39;);<br>const options = { ... };</pre><pre>module.exports = {<br>	entry: [<br>		&#39;app.js&#39;,<br>		&#39;webpack-plugin-serve/client&#39; // ← important: this is required, where the magic happens in the browser<br>	],<br>  plugins: [<br>    new Serve(options)<br>  ],<br>  watch: true  // ← important: webpack and the server will continue to run in watch mode<br>};</pre><p>When a Webpack build is initiated, the plugin sets itself up. That includes a <a href="https://koajs.com/">Koa</a> application, built-in and user-defined middleware is setup, and a few other static goodies that need to be ready to go down the line. Once a build starts, a web server is spun up and attached to the Koa application, a <a href="https://github.com/websockets/ws">WebSocket server</a> instance is attached to the web server, and the plugin begins listening to the compiler instance for notification of a refreshed build. If Hot Module Replacement is enabled, it’ll communicate changes via WebSocket to the client/browser and you’ll see changes based on the options passed to the plugin.</p><p>There is a myriad of different <a href="https://github.com/shellscape/webpack-plugin-serve/blob/master/README.md#options">options</a> available to configure and use the server. We’ve also <a href="https://github.com/shellscape/webpack-plugin-serve/tree/master/recipes">prepared a few recipes</a> that users can reference to get started, and we’re keen to add more.</p><h3>Decidedly Different</h3><p>First and foremost, it’s a plugin. Before starting development to we searched quite a bit to try and find a pre-existing, similar solution. We believe this is a novel approach for Webpack. As a plugin it doesn’t have the learning curve of a separate Command Line Interface and there are no subsets of flags to learn or understand to use it. Plugins are one of the first things that new Webpack users learn about — a perfect entry-point for a bolt-on development server. And by leveraging the compiler directly the server can offload responsibilities, like file watching, to the compiler and can avoid reinventing the wheel, thus reducing complexity.</p><p>Just as with webpack-serve, we chose to use WebSockets for server-client communication (the magic that enables Hot Module Replacement instructions in the client/browser). Unlike webpack-serve, we were able to leverage a new “serverless” WebSocket server implementation. We learned from webpack-serve that while the intention behind a secondary WebSocket server was good, it increased complexity and issues with very little benefit.</p><p>We also took the approach of building in support for the most popular feature sets of the other two development server options. Only this time around, there’s no getting fancy with it:</p><ul><li>User-defined and user-ordered middleware is available, though vastly simplified as compared to webpack-serve</li><li>Useful overlays for errors and warnings, and progress are included out of the box, and were developed using a somewhat-standardized approach, and have a sexy, uniform look and feel for a consistent experience.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eazThmuUWN0v1ppC.png" /></figure><ul><li>Features like HTML History API Fallback, Proxying, and Compression have support baked in, though we differ in that options are passed straight through to the underlying dependencies. That makes use and documentation much easier for the end user, as there’s no intermediate layer to have to understand.</li><li>Built-in Troubleshooting for common errors:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NJtajgSg8jvrgUmT.png" /></figure><p>I’d also argue that this approach is far cleaner than the others that preceded it. We’ve given a lot of consideration to how the feature set might be expanded and have put an architecture in place that should allow for new features to be supported without adding the kind of complexity that cripples maintainability. We learned quite a bit from the shortcomings of both webpack-dev-server and webpack-serve, and really made an effort to improve upon them.</p><p>Lastly, and what is sure to be a slightly controversial choice, we chose to support only the <a href="https://github.com/nodejs/Release">Active LTS versions</a> of Node, which is presently v8 and v10, and the <em>Current</em> version (Node v11 as of this post date). We’ve covered why in our <a href="https://github.com/shellscape/webpack-plugin-serve/blob/master/.github/FAQ.md">FAQ</a>.</p><h3>Forthright Finale</h3><p>Moving forward we’re open to adding more features, or developing the modules to provide pass-through features, as use-cases arise. The Node server space is so rich in functionality that we should be able to easily expand webpack-plugin-serve or, most importantly, provide excellent direction for how users can apply needed functionality, easily. Aside from that, the stack is pretty solid. I’m sure the Webpack user-base will surprise us with scenarios we haven’t considered.</p><p>We’re just a few developers hoping to provide a better experience for everyone, and would really appreciate folks spreading the word about it. Please don’t hesitate to open an issue or hit us up on Twitter. And if you’d like to help us improve the project, please consider <a href="https://github.com/shellscape/webpack-plugin-serve">contributing</a>.</p><h3>Cheers!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4877k4Hq9dPdtmvg9hnGFA.jpeg" /></figure><p><em>Originally published at </em><a href="http://shellscape.org/2018/11/27/webpack-plugin-serve"><em>shellscape.org</em></a><em> on November 27th, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8d4b859aa78" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dailyjs/plugin-to-a-fresh-webpack-development-server-a8d4b859aa78">Plugin to a Fresh Webpack Development Server</a> was originally published in <a href="https://medium.com/dailyjs">DailyJS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Webpack and JSF Stole Code, Returned It, and Assigned Bad Copyright]]></title>
            <link>https://medium.com/@shellscape/how-webpack-and-jsf-stole-code-returned-it-and-assigned-bad-copyright-b2a501f9b8cd?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2a501f9b8cd</guid>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[licensing]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Sat, 03 Nov 2018 15:41:45 GMT</pubDate>
            <atom:updated>2018-11-04T00:35:09.181Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*XnivSt-uf-IqRJ2yM9C53w.png" /><figcaption><em>Printing Press Image By African American Photographs Assembled for 1900 Paris Exposition [Public domain], via </em><a href="https://commons.wikimedia.org/wiki/File:Printing_with_printing_presses_at_Claflin_University,_Orangeburg,_S.C._LCCN93506648.jpg"><em>Wikimedia Commons</em></a></figcaption></figure><p>Or, <em>Why You Should be Dubious About Contributor License Agreements</em>.</p><p>In a corner of the webpack ecosystem lives a small, mostly unnoticed module: <a href="https://github.com/webpack-contrib/webpack-log">webpack-log</a>. webpack is a JavaScript Foundation project and contributions to webpack are subject to the JSF Contributor License Agreement (CLA). In August 2018, a webpack-contrib admin copied code from one of my modules into that project wholesale, verbatim, and without retaining the license. This is a short cautionary story of my efforts trying to get that corrected.</p><p><em>It is likely that this post will be attacked by those passionate about webpack and by those in the organization who dislike me personally. There are many good people whose livelihoods depend upon webpack, the organization, and the donations it receives. If you or your company are donating to the project, </em><strong><em>please</em></strong><em> continue to do so. However, if you feel the information in this post demands improvement of the organization, please ask them to do </em><strong><em>better</em></strong><em>.</em></p><p>I do not seek the spotlight in tech, and I do not like it. I prefer to be under the radar. However, I do feel that the information in this post needs to be shared. This post will not name names and will not call out individuals for action, or a lack thereof. Rather, already public information will speak for those involved.</p><p><em>Update (Nov 3rd 2018 23:12 UTC): Since posting and sharing this article, the webpack project has </em><a href="https://github.com/webpack-contrib/webpack-log/pull/14"><em>taken steps to remedy the situation</em></a><em>. It’s regrettable that it took this article to gain action, but it is appreciated. I don’t have knowledge as to whether or not JSF had a part in the remedy. This article should still serve as a cautionary tale on licensing, copyright, and Contributor License Agreements.</em></p><h3>Backstory</h3><p>I want to quickly share some backstory that I have not shared publicly prior, so that the issue, situation, and links contained in this post have some context for the reader.</p><p>In mid June of 2017 I was contacted by webpack leadership to assist on an <a href="https://github.com/webpack/webpack-dev-server/pull/942">emergency fix</a> for a somewhat serious <a href="https://medium.com/@mikenorth/webpack-preact-cli-vulnerability-961572624c54">SSL security flaw in webpack-dev-server</a>, because I had made some prior contributions to that project. Shortly thereafter I was invited to be a maintainer and, following that a <a href="https://github.com/webpack-contrib">webpack-contrib</a> admin and webpack core team member. I was also introduced to the contributor payment program at the time and actively participated. As a new husband with our first child on the way, that program was massively helpful in starting our new family and I benefited from it.</p><p>I created a bunch of new modules for the webpack community in webpack-contrib, and made a concerted effort to challenge the status quo in the project and in the User Experience. One of those modules happened to be webpack-log. To quote a favorite movie, <a href="https://www.youtube.com/watch?v=8kcgosLwPDE&amp;t=10s"><em>“I fight for the users”</em></a>. But I was naive. I pushed too hard, too fast and vastly underestimated the deep nepotism and significant hero-worship that exists in the webpack organization. The culmination of which occurred at the same time the organization started to run out of funding, forcing in a change in how donations were allocated and distributed that I vehemently disagreed with. As a core team member, it was my responsibility to make my dissent known. A later, ill-fated effort I undertook to replace the default CLI for webpack resulted in poor communication within the core team and by maintainers, poor decisions by leadership, and was ultimately the straw that convinced me to walk away from the team.</p><p>Communication from my end was not perfect. I can be brash, passionate, and have a deep sense of pride and ownership in code that I write. I acknowledge my flaws. Despite 18 months of dedication and work, several new projects for the benefit of users, and huge gains for the webpack user experience, I was subsequently accused of violating a non-existent Code of Conduct, cheating users and the project, labeled a thief, a poor developer, and <a href="https://github.com/webpack-contrib/webpack-log/issues/11#issuecomment-423636767">toxic</a> by most of the organization’s members. Those members who disagreed did not speak publicly in my defense.</p><p>I was shunned, an outcast — <strong>open dissent is not welcome in webpack</strong>.</p><h3>Enter webpack-log</h3><p>I got involved in webpack because it was starting to be used by the company I was working for at the time. I was aghast as just <em>how bad</em> the user experience for webpack was. In December 2017 I put together webpack-log to try and give some consistency to the log output webpack and ecosystem tools were generating, and to make my eyes bleed a little less while using it.</p><p>Just prior, I had created <a href="https://github.com/shellscape/loglevelnext">loglevelnext</a>, which was at the time a fork of the still much-loved and wildly-popular <a href="https://github.com/pimterry/loglevel">loglevel</a>. I forked because at the time I had proposed changes to loglevel that the maintainer couldn’t agree with. (I love open source for that!). loglevelnext was a project created for work and used primarily by colleagues internally on development environments. I leveraged loglevelnext in webpack-log as a dependency. The feature set was apt and it suited the goals I had for webpack-log both in the console and in the browser.</p><p>And so, webpack-log went on to be used in the new webpack-contrib projects I created, webpack modules I maintained, and in several third-party modules, and it sat quietly in the corner.</p><h3>Curiously Copied Code</h3><p>Now, I’m not a whore for download counts, but I do check in on them from time to time out of curiosity and for various other reasons. In September, a month after the copy commit to webpack-log, I noticed a steep drop in loglevelnext downloads, and that webpack-log was no longer a dependent of the module. Naturally; I investigated.</p><p>Following my falling-out with the webpack organization, nearly all of the projects I contributed were marked <em>[DEPCRECATED]</em>, users were notified they were now unmaintained, and code I had contributed was summarily <a href="https://github.com/webpack-contrib/schema-utils/pull/25">erased from git history</a> altogether. In that same month, loglevelnext was <a href="https://github.com/webpack-contrib/webpack-log/commit/b5c2017e45b013a1b4c9e09694fc120afc3a307a">copied wholesale into webpack-log</a>, and removed as a dependency. Weird, but OK.</p><p>But not OK. My license for loglevelnext wasn’t retained. My code was effectively stolen. A curious event given the previously mentioned deprecation and git history rewrites.</p><p>I immediately thought about filing a DCMA. I would have been well within my right to do so, but that would ultimately hurt the users. Instead, I cringed and decided to open an issue.</p><h3>The Issue</h3><p>The <a href="https://github.com/webpack-contrib/webpack-log/issues/11">Github issue</a> started out plainly enough. Surprising, the organization’s own members weren’t even on the same page as to how the license should be attributed, or whether a standard MIT license could be used with the JavaScript Foundation’s Contributor License Agreement. The maintainer behind the copy commit <em>tried</em> to make it right by <a href="https://github.com/webpack-contrib/webpack-log/pull/12">adding my name</a> to the project’s LICENSE file, but bungled the attempt. By adding my name to that license file in the way done, they had granted me (and another individual) copyright over the <em>entire project</em>. One might think that’s no big deal, and in the grand scheme of things it’s probably not — but it isn’t correct licensing. What should have been done instead, would have been to include the LICENSE file from loglevelnext in the directory of the copied code. That would have limited my copyright to only my code. Alternatively, they could have pasted the copyright as a header in the file in question.</p><p>The crux of the situation now is that by copying loglevelnext into the webpack-log project, effectively hard-forking and adopting the project under JSF-owned webpack-contrib, the user <strong>asserted that they could circumvent the JSF adoption process</strong> by copying MIT-licensed code into a project and submitting the code under a CLA.</p><p>To <a href="https://github.com/webpack-contrib/webpack-log/issues/11#issuecomment-423500502">quote</a> a <a href="https://github.com/webpack-contrib/webpack-log/issues/11#issuecomment-423573438">JSF board member</a> in the issue:</p><blockquote>The JS Foundation has <a href="https://github.com/JSFoundation/TAC/blob/master/Project-Lifecycle.md#applying-to-join">a process</a> for adopting projects. Copying the code into a JSF-supported organization while removing the old license (or inserting the JSF license) is definitely not the process. To ensure that we have the legal rights to the software, we need the author(s) to transfer ownership.</blockquote><blockquote>What seems to have happened here is that a large amount of someone else’s code was copied from an outside project to this one without attribution, and without the license specified in their code. So now it de-facto appears to have the JSF license (since it’s in this repo) but is not code licensed to the JSF. You can’t avoid having the JSF adopt someone else’s project by copying the whole project source code into yours.</blockquote><p>And that’s where the MIT license and the JSF CLA get really, really murky. After that the issue gets testy.</p><p>I admit; I was snarky in my final reply before the issue was closed. I should have done better there. I have real trouble abiding false statements about myself, and having someone so completely naive about the situation misrepresenting my intentions. Unfortunately, after that exchange, naming-calling by an organization member ensued and the issue was closed and locked (notably without rebuke). The result of that issue was a ban from webpack and webpack-contrib organization repositories.</p><p>The copyright issue however persists, and the webpack/webpack-contrib organization’s members have not addressed it further.</p><h3>Legal Eagles</h3><p>After being summarily banned by both webpack and webpack-contrib organizations, I took my grievances to the next logical recourse: JavaScript Foundation’s legal department. Since webpack is a JSF project, I thought their legal department should surely be able to remedy this, given that one of their members are in support of a resolution.</p><p>Everyone I conversed with in JSF’s legal department was extremely polite and communication was excellent. That’s pretty much where the positive experience ended. After a month of inaction, I contacted them to let them know of my intention to write this article. Purely as a courtesy and stated as much. A few days later, a new representative for their outside counsel contacted me and stated that some responsibilities had changed hands. They asked for more time and I enthusiastically granted it; I had thought an additional week would be plenty. But after nearly two weeks passed with no visible action, nor resolution, nor statement of position from JSF, I have to consider the interaction with JSF a failure. Unfortunately, <a href="https://twitter.com/scott_gonzalez/status/1048220377934155778">concerns shared</a> about inaction from JSF legal seem to prove true.</p><p>Given that JSF ultimately holds authority over code contributed under the CLA, this should be a cause for some concern about copyright and the enforcement of the CLA and how it, and your contributions under it, will be handled by JSF and projects belonging to it, moving forward.</p><h3>In Closing</h3><p>Be dubious about signing a Contributor License Agreement. Be especially dubious about signing one in which the organization members don’t fully understand their own CLA, and about which the organization who owns the CLA won’t act upon it.</p><p>I’ve since moved most of my personal projects to the copy-left <a href="https://www.mozilla.org/en-US/MPL/2.0/">Mozilla Public License</a>, which should (hopefully) help to prevent this kind of scenario in the future within any project underneath the JavaScript Foundation.</p><p>And finally, if any of my own code or repositories are in violation of copyright or have failed to cite or include license correctly, please <a href="https://github.com/shellscape/meta/issues/new">let me know</a> and it shall be remedied quickly.</p><h3>Cheers!</h3><p><em>Originally published at </em><a href="http://shellscape.org/2018/11/03/webpack-jsf-cla"><em>shellscape.org</em></a><em> on November 3rd, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2a501f9b8cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webpack, Now With Extended Flavor!]]></title>
            <link>https://medium.com/@shellscape/webpack-now-with-extended-flavor-b1e57074de77?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1e57074de77</guid>
            <category><![CDATA[configuration]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[configuration-management]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Tue, 03 Jul 2018 00:47:33 GMT</pubDate>
            <atom:updated>2019-03-18T04:22:03.536Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Update 12/18</strong></p><p>Hello Readers! There’s a new option in town that’s smaller, lighter, and with far less learning curve: <a href="https://npmjs.com/package/webpack-nano">webpack-nano</a> For extending a webpack configuration, we recommend using <a href="https://github.com/survivejs/webpack-merge">webpack-merge</a></p><p><em>The webpack-contrib org unfortunately chose to nuke the webpack-command project when I no longer had the time to maintain it. It’s a shame, but as the update above mentions, there’s a much better option available now. webpack-nano lives outside of that organization, not subject to the same questionable decision making, and is actively maintained by a cabal of passionate developers.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1e57074de77" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Webpack’s New (CLI) Hotness]]></title>
            <link>https://medium.com/@shellscape/webpacks-new-cli-hotness-d6a2063168a8?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6a2063168a8</guid>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Sun, 29 Apr 2018 15:10:19 GMT</pubDate>
            <atom:updated>2019-03-18T04:18:09.751Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Update 12/18</strong></p><p>Hello Readers! There’s a new option in town that’s smaller, lighter, and with far less learning curve: <a href="https://npmjs.com/package/webpack-nano">webpack-nano</a></p><p><em>The webpack-contrib org unfortunately chose to nuke the webpack-command project when I no longer had the time to maintain it. It’s a shame, but as the update above mentions, there’s a much better option available now. webpack-nano lives outside of that organization, not subject to the same questionable decision making, and is actively maintained by a cabal of passionate developers.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a2063168a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[webpack-serve Up a Side of Whoop-Ass]]></title>
            <link>https://medium.com/@shellscape/webpack-serve-up-a-side-of-whoop-ass-42a838b351a2?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/42a838b351a2</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Tue, 13 Feb 2018 03:59:58 GMT</pubDate>
            <atom:updated>2019-03-18T04:27:11.744Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jBjtPXBpfSABU0AUbOxYWA.jpeg" /><figcaption>All aboard the S.S. Shipit. Come, break my things.</figcaption></figure><p><strong>Update 12/18</strong></p><p>Hello Readers! There’s a new option in town that’s far easier to use, smaller, faster, more flexible, and supports more options that webpack-dev-server users will recognize. It’s worth a look: <a href="https://npmjs.com/package/webpack-plugin-serve">webpack-plugin-serve</a></p><p><em>As of March 13, 2019, </em><a href="https://github.com/shellscape/webpack-serve">webpack-serve</a><em> now acts as a CLI for webpack-plugin-serve, and enables non-intrusive use of the plugin in your configs via the command line. The article content that resided here previously covered a prior version of webpack-serve, which the webpack-contrib org attempted to nuke, unsuccessfully. Please see either of the linked packages above for more information.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42a838b351a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Signal to Bug Ratio]]></title>
            <link>https://medium.com/@shellscape/signal-to-bug-ratio-85905e337087?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/85905e337087</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[marketing-technology]]></category>
            <category><![CDATA[signal]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Mon, 24 Apr 2017 16:49:33 GMT</pubDate>
            <atom:updated>2017-04-24T23:24:17.722Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/859/1*H7jgBSbStOImtgKHOJS-pg.jpeg" /><figcaption>Debugging Signal events can be problematic, exacerbated by a lack of tools and resources.</figcaption></figure><p><em>Preface: I work with Signal through my regular job, I’m not promoting the product or service in any way.</em> <a href="https://www.signal.co/">Signal</a> is a platform for implementing and managing tags and data for marketing, tracking, and affiliates. Debugging Signal events can be very problematic, exacerbated by a lack of tools, guidance on best practices, and engineering support.</p><h3>Oodles of Noise</h3><p>Signal events are the de facto method for a client (a web page) to interact with a signal implementation. Typically you bind an event to window and use some JavaScript to trigger an event on window in the client. Sounds easy, yeah? If you happen to work within an environment in which an engineering team doesn’t manage and test data being sent along with these events, debugging that eventData can be far more difficult than it should be. There’s a simple solution to debugging eventData that introduces responsible patterns and ease of use, which go beyond console.log.</p><h3>Knowledge Gap</h3><p>I’d like to say right-off-the-bat that my intentions in this section are not to belittle anyone at Signal, but rather raise the flag about related gaps in knowledge within Signal’s support team.</p><p>If you approach Signal about a tag implementation, an error with a tag, or pretty much any in-product code need, you’ll wind up talking with an “Implementation Consultant.” For most basic questions and implementation needs, these folks do a good job helping out. However, they are not <a href="https://en.wikipedia.org/wiki/Software_engineer">engineers</a>. Rarely do we receive code from them, or review code they’ve added to our Signal implementation, that would pass review in any corner of our <a href="http://tech.gilt.com/">engineering department</a>. Again, this is not to knock their skill level — they aren’t advertised as engineers. But it’s important to understand the distinction, and important to consult engineers for architectural needs and best-practice guidance.</p><h3>The Console.log Conundrum</h3><p>At one point in time, our Signal implementation went from being an engineering-first, engineering-owned product, to a Marketing and Analytics owned product. Those teams did a fine job using Signal to drive the associated sites forward with very little JavaScript experience. However, their guidance was coming from non-engineers as well, and at no fault of their own, <a href="https://sourcemaking.com/antipatterns">many anti-patterns were implemented</a>. One of the more egregious was the overuse of console.log.</p><p>Our Signal managing teams were advised to use console.log wherever they wanted to view the value/content of eventData for each event that came through Signal. That resulted in <em>well over 50 instances</em> of console.log sprinkled throughout just one of five Dashboards. That’s a hell of a lot of console noise for a single page. Imagine engineers for the site trying to figure out where all the noise was originating, having no knowledge of the Signal implementation nor what it was doing. <a href="https://www.youtube.com/watch?v=s8MDNFaGfT4">Bananas</a>!</p><h3>Simple Engineering Save</h3><p>Since our implementation is not (yet!) engineering-owned, we can’t run tests and such on the data in a pre-production environment. Some would argue that Signal has some pre-production ability, but even “Previewing” tags and events still runs live in production. So we needed a method for our Marketing and Analytics teams to be able to debug in a familiar way (which is unfortunately console.log) but in a <em>controlled</em> manner that doesn’t affect the world.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b70eb09b60b166bc91e353cf90926165/href">https://medium.com/media/b70eb09b60b166bc91e353cf90926165/href</a></iframe><p>The idea is dead simple. Sprinkle bananas.signal.debug(...) all over, anywhere, go bananas! It won’t output to the console until explicitly enabled. That can be done in two ways, but adding ?debug=true to the URI and refreshing, or by calling bananas.signal.enable() in the console before executing an action on the page that will trigger a Signal event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mTFMEzWaa_vW7-6X.png" /></figure><p>Only the debugging user will ever see the output. Zero console pollution.</p><h3>Mind Bottling</h3><blockquote>You know when things are so crazy it gets your thoughts all trapped, like in a bottle — <a href="https://www.youtube.com/watch?v=rSfebOXSBOE">Blades of Glory</a></blockquote><p>Signal consultants suggested a few variants on the same theme but over all their solutions were either too similar, or too confusing for the non-engineer custodians of our Signal implementation. It’s surprising that something similar and as simple as this isn’t already part of Signal’s client library and available for folks who are using the product without engineering support.</p><p>Please feel free to use the script above in your implementation. Or, if you have a better solution, please comment!</p><h3>Cheers!</h3><p><em>Originally published at </em><a href="http://shellscape.org/2017/04/24/signal-to-bug-ratio"><em>shellscape.org</em></a><em> on April 24, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85905e337087" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strike a Harmony with Node.js and Harmonica]]></title>
            <link>https://medium.com/dailyjs/strike-a-harmony-with-node-js-and-harmonica-7d4d8662486d?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d4d8662486d</guid>
            <category><![CDATA[v8]]></category>
            <category><![CDATA[harmony]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 03:17:24 GMT</pubDate>
            <atom:updated>2017-04-20T15:12:25.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/489/1*qWoaZqQGfTCP-axzJZhK6Q.jpeg" /><figcaption>Effortlessly use harmony flags with Node.js</figcaption></figure><p>With every new version of Node.js, the platform quietly provides access to experimental features that ship with v8 which may not be quite ready for production use. That doesn’t mean we can’t use those features today, though. And there’s a nearly effortless way to access them.</p><p>For those that may be new to Node.js or those who haven’t yet delved into the inner workings of Node.js — the platform runs atop Google’s JavaScript engine, <a href="https://developers.google.com/v8/">V8</a> by default. V8 is constantly improving and typically ships with features which may not be stable or ready for production environments, that require command-line flags to enable. Those flags are the harmony flags.</p><p>Prior to Node.js v7.6, the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function">asyc/await</a> feature — the feature I’d been most looking forward to — was locked behind the--harmony-async-await flag. There’s a good likelihood that <a href="https://www.chromestatus.com/feature/5365692190687232">ES6 Modules</a> will arrive in much the same way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4877k4Hq9dPdtmvg9hnGFA.jpeg" /></figure><h3>Harmony Flags</h3><p>Determining what harmony flags are supported by a version of Node.js is easy:</p><pre>node --v8-options | grep &quot;in progress&quot;</pre><p>For example, I’m currently on Node.js version 7.8. Running that command, the list of harmony flags shows as follows:</p><pre>→ node --v8-options | grep &quot;in progress&quot;<br>  --harmony_array_prototype_values (enable &quot;harmony Array.prototype.values&quot; (in progress))<br>  --harmony_function_sent (enable &quot;harmony function.sent&quot; (in progress))<br>  --harmony_sharedarraybuffer (enable &quot;harmony sharedarraybuffer&quot; (in progress))<br>  --harmony_simd (enable &quot;harmony simd&quot; (in progress))<br>  --harmony_do_expressions (enable &quot;harmony do-expressions&quot; (in progress))<br>  --harmony_restrictive_generators (enable &quot;harmony restrictions on generator declarations&quot; (in progress))<br>  --harmony_regexp_named_captures (enable &quot;harmony regexp named captures&quot; (in progress))<br>  --harmony_regexp_property (enable &quot;harmony unicode regexp property classes&quot; (in progress))<br>  --harmony_for_in (enable &quot;harmony for-in syntax&quot; (in progress))<br>  --harmony_trailing_commas (enable &quot;harmony trailing commas in function parameter lists&quot; (in progress))<br>  --harmony_class_fields (enable &quot;harmony public fields in class literals&quot; (in progress))</pre><p>To enable a harmony flag, Node.js typically has to be run from the command-line with the flag and the target entry script as such:</p><pre>node index.js --harmony_array_prototype_values</pre><p>Or to enable all harmony flags:</p><pre>node index.js --harmony</pre><p>And that can just get tedious for tooling, cross-team development, etc.</p><h3>An Easy Instrument</h3><p><a href="https://www.npmjs.com/package/harmonica">Harmonica</a> is an NPM Module that allows developers to use --harmony flags programmatically, which means an end to the need for specifying command-line options for experimental harmony features. If you’ve ever wanted to use experimental features within <a href="http://gulpjs.com/">Gulp</a> tasks, or have a need to run an app through wrappers like <a href="https://www.npmjs.com/package/forever">forever</a>, this module takes the command-line headache out of the equation.</p><p>Setting up Harmonica is painless. Within your entry file (index.js, app.js, etc) place a call to harmonica:</p><pre>require(&#39;harmonica&#39;)();</pre><p>That’s the equivalent to node --harmony. Should you need only specific flags, pass an Array of strings representing the flags you want to enable, without the leading hyphens, as the first parameter.</p><pre>require(&#39;harmonica&#39;)([<br>  &#39;harmony_function_sent&#39;,<br>  &#39;harmony_do_expressions&#39;<br>]);</pre><p>And from there, let the module handle initializing the harmony flags you wish to use, with no need to specify them within the terminal or command prompt.</p><h3>Not All Roses and Rainbows</h3><p>It’s really important to note that harmony features are not production ready. And as folks have <a href="https://github.com/koajs/koa-hbs/pull/65">pointed out</a>, some of the experimental / unstable features that are hidden behind harmony flags can come with issues that affect security, performance, etc. It’s never advisable to use harmony features in a production environment unless thoroughly vetted.</p><p>Now get to dabbling with the latest that Node.js has to offer!</p><h4>Cheers!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZrJKJqBsksWd-8uKM9OvgA.png" /></figure><p><em>Originally published at </em><a href="http://shellscape.org/2017/04/05/strike-harmony-nodejs-harmonica"><em>shellscape.org</em></a><em> on April 5, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d4d8662486d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dailyjs/strike-a-harmony-with-node-js-and-harmonica-7d4d8662486d">Strike a Harmony with Node.js and Harmonica</a> was originally published in <a href="https://medium.com/dailyjs">DailyJS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Floaties for Gulp Users]]></title>
            <link>https://medium.com/@shellscape/floaties-for-gulp-users-c3efcf55c6d5?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3efcf55c6d5</guid>
            <category><![CDATA[help]]></category>
            <category><![CDATA[gulp]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[assistive-technology]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Sun, 08 Jan 2017 17:20:20 GMT</pubDate>
            <atom:updated>2017-01-09T21:04:16.858Z</atom:updated>
            <content:encoded><![CDATA[<p>In large or distributed teams, sharing knowledge about tooling can be a challenge. When a toolchain or pipeline gets to be big and contains a lot of code, that challenge grows with the size of the codebase. Providing a solution is as easy as describing your tasks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*CG9ecAOLychwSDBVSqwIxA.png" /><figcaption>Sometimes a good life jacket can make all the difference.</figcaption></figure><h3>gulp-assist</h3><p>I recently put together <a href="https://www.npmjs.com/package/gulp-assist">gulp-assist</a> as a tool to address that issue. An extension of sorts for<a href="https://www.gulpjs.com/">Gulp</a>, gulp-assist displays meaningful information on a tooling setup in a stylish format. How meaningful is completely up to the developer providing it.</p><p>What about the --tasks and --tasks-simple flags that Gulp already has? Those are great if one wants a basic idea of the structure of the tooling, but gives us nothing if we want to know about the individual tasks.</p><h3>Floaties and Lifejackets</h3><p>That all sounds lovely, but what’s this thing look like? <a href="https://www.youtube.com/watch?v=K0nGwZfPLB0">GIMME’DA CASSHHH!</a>. As run in the terminal:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UpynYnNyC--iKlls." /></figure><p>And for each individual task including flags, and their descriptions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mNElPfggmEUeaSmV." /></figure><p>Is purty no?</p><h3>To Inflate, Pull Down On The Tab</h3><p>This thing really is <a href="https://www.youtube.com/watch?v=HWrjBBXjjhM&amp;t=1m3s">easy to use</a>, and the few extra keystrokes it costs will undoubtedly save time down the road.</p><pre>const gulp = require(&#39;gulp&#39;);</pre><pre>// initialize the module<br>require(&#39;gulp-assist&#39;)();</pre><pre>gulp.task(&#39;lint&#39;, () =&gt;<br>	// ...<br>);</pre><pre>gulp.assist(&#39;lint&#39;, {<br>  desc: &#39;Analyzes code for errors and convention violations.&#39;,<br>  flags: {<br>    src: &#39;Specifies a directory / module to inspect, within the `src` directory.&#39;<br>  }<br>});</pre><p>Define your tasks as per usual, then register the task with gulp-assist. It’s <strong>important to note</strong> that gulp-assist needs the task defined with Gulp before it can be registered with gulp-assist. That’s an intentional design decision, but I’m always <a href="https://github.com/shellscape/gulp-assist/issues">open to suggestions</a>.</p><h3>Alternatives</h3><p>The great thing about Gulp is that there’s a slew of alternatives for any one thing you might want to get done. With that, you might enjoy <a href="https://www.npmjs.com/package/gulp-help">gulp-help</a> more so than my extension. It hooks the gulp.task method to allow for additional parameters that describe a task.</p><p>I didn’t care for this approach as I prefer separation of concerns and dislike modifying established API. I also prefer the output of gulp-assist (but I’m obviously biased).</p><h3>Cheers!</h3><p><em>Originally published at </em><a href="http://shellscape.org/2017/01/08/floaties-for-gulp-users"><em>shellscape.org</em></a><em> on January 8th, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3efcf55c6d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pants Optional: Working Remotely]]></title>
            <link>https://medium.com/@shellscape/pants-optional-working-remotely-68468286b286?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/68468286b286</guid>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[remote-work]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Tue, 29 Nov 2016 04:52:51 GMT</pubDate>
            <atom:updated>2016-11-29T04:52:51.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*AB22rKUW1zLMPOy1pgWVMw.jpeg" /><figcaption>Working from home has its perks, if you can manage it.</figcaption></figure><p>I’ve been working remotely for nearly 7 years now, and I couldn’t imagine ever going into an office on a daily basis again. It’s a magical setup that affords incredible freedom, and far more responsibility. I love working remotely, and I’m going to share with you my strategy for working in my own, pants-optional office.</p><blockquote><em>I could never work from home, I’d never get anything done.</em></blockquote><p>That’s the response I typically get from anyone I’ve ever told about my setup. I’ve come to acquire several key lessons and skills that make working remotely a joy, so much so that I doubt I’ll ever again take employment where reporting to an office is a requirement, if I can at all help it.</p><h3>Never Say Never</h3><p>The “I could never do it” response from folks isn’t surprising. The last thing most of us want to do at home is think about work. In fact, <a href="https://hbr.org/2016/07/dont-take-work-stress-home-with-you">many smart types will tell you</a> that it’s an unhealthy thing to do. And for those who work the typical <em>9 to 5</em> routine, I’d probably agree. But I live the software developer life, and I’ve come to find a method that makes it very easy to be successful remotely.</p><h3>When Work Isn’t Work</h3><p>If work is work, you shouldn’t be doing it from home. I’m lucky enough to do something that I’m fairly decent at, and that which I really enjoy. That’s really key. Enjoying the work lets you turn on and off at will without contaminating your home with “the office”. You’ll be able to let ideas flow throughout the day and night. The official hours of your physical office will become more guidelines, whereby you need to stay available, but that which you’re not constrained by.</p><h3>Pants Are Actually Optional</h3><p>Just don’t forget them if you’re planning on taking video conference meetings. You don’t want to be that person that has to get up to shut the window and inadvertently shows off those new adventurous undies.</p><p>But in all seriousness, get comfortable. Choose a workspace that works best for you. Remember that you’re not in an office! I personally choose to work from my dining table with lots of light and fresh Florida air. Some of my peers prefer a cordoned off basement office. Your workspace should be what keeps you the most comfortable throughout the day.</p><p>Part of a great workspace is surrounding yourself with things you love. My kitchen is about 20 feet from my laptop — my inner fat kid loves that. That also means that I have water and <a href="https://www.youtube.com/watch?v=A14qyN0rVGA">other beverages</a> readily accessible. I’ve also got a solid TV on the wall and typically have Netflix going all day long. For me, some kind of white noise and the occasional mental break in close proximity keeps me sane throughout the day.</p><h3>Creature Feature</h3><p>Get a pet! They’re an incredible stress reliever and amazing outlet for problem solving. Don’t be afraid to be that crazy person who talks to their animals. <a href="https://scontent-atl3-1.cdninstagram.com/t51.2885-15/e35/14723445_1810525985861202_6702972046583791616_n.jpg">Leelu</a> frequently helps me out in a mental bind.</p><h3>Communicate, Silly</h3><p>Communication. Communication. Communication. You must go out of your way to communicate with your peers, your supervisors, even the person working at the reception desk in the office. There are reasons, of course:</p><h3>Communication Builds Trust</h3><p>Trust in you from your peers is key, and while it would be grand if we were all judged by our merits, many people can’t trust until there’s a base of communication that’s usual and comfortable.</p><h3>Communication Builds Rapport</h3><p>Until you’re in the office and have the chance at in-person face time with everyone you work with, you’re the faceless (or single faced avatar) internet person who apparently gets paid by the same company bi-weekly. You may be fortunate and work for a company that has access to video conferencing, but even then you’re still a floating head in a window. Great communication builds a familiarity with your peers that will ultimately aid in collaboration.</p><h3>Frequent Communication Creates Value</h3><p>Frequent communication is paramount. Vanishing for extended stretches of time has a negative effect. Remember that you’re not in the office and people can’t see what you’re up to. For all they know you’re out at the pool floating on a giant inflatable swan. When you reach out throughout the day, you’re reminding people that you’re there. When you share what you’re working on frequently, you’re reminding people of the work you’re doing.</p><h3>Hellooooooo</h3><p>Working remotely can sometimes <a href="https://www.youtube.com/watch?v=eCdRFMp8Xwo">feel like a scene</a> out of <em>28 Days Later</em>. The feeling of isolation is something every remote worker needs to combat on a daily basis. Sometimes it’s a slow day in the office, and others it’s that the physical office is too busy. It’s easy in that frequent situation to get discouraged, frustrated, or just plain bummed out. That’s a good opportunity to step away and right your ship.</p><p>Since us remotes are also neglected socializing throughout the day, make up for that deficit when work is done for the day. I’m a social guy and staying in or isolated for too long gets me stir-crazy. I make a concerted effort to socialize after-hours. Befriend some bartenders or others that work outside the 9-to-5 cycle. If you’ve a family, visit with some neighbors or take the kiddies out for something fun around other people.</p><h3>Halt, and Catch Fire</h3><p>Take breaks. Take lunches. Take naps. Decline meetings. Run errands. Play with the dog. Go for a walk. Go for a run. Get a hobby and indulge it. Watch an episode of <em>The Walking Dead</em>. Have an adult beverage if you feel the urge. I personally never like to work for more than two hours straight. Halting keeps me fresh and keeps me sane.</p><p>Stopping and taking a breath is one of my keys to the gig. Those incredible freedoms I mentioned earlier come into play here. Of course this depends on the company you work for and the folks above or around you in the hierarchy, but take advantage of the ability to do throughout the day what those in an office aren’t able to. Just bear in mind that your responsibility to the work doesn’t end. If you’re going to play a little hookey, remember to make time later to cover your deliverables.</p><h3>Expand Your Organizational Skills</h3><p>When no one’s available to chat, you don’t always have the luxury of stopping work and waiting. You’ll have to develop solid organizational skills that will allow you to revisit things that need discussing, or to resume tasks that you’re blocked on down the line. A great degree of self-management is necessary regardless of the kind of management structure you’re working in. A cautious level of independence will go a long way. You won’t always have the time or the opportunity to discuss choices, problems, or solutions with your peers. Which brings us to…</p><h3>Peer Dependencies</h3><p>(That’s an NPM pun, for the nerds reading this)</p><p>Your peers are going to mean success or failure in a remote gig. When interviewing, make sure you’re asking questions as well. You’ll want to interview the folks doing the interviewing to make sure they know how to work with remote developers. Some companies are freshly wading into hiring remotes, others are seasoned, and yet others have no idea what they’re getting into. Management should be on board with and see value in remote employees. It also helps to jump into a gig with peers that have experience working with remotes. Talk to the folks that will be managing you and your projects to get a feel for how they expect to work with you. Never be afraid to share your ideas early on.</p><h3>Time For a Whisky</h3><p>I hope that the lessons I’ve learned can give others in or considering remote work something to think about and help out if needed.</p><p>If you’ve been thinking about remote work, there are a plethora of resources that can help:</p><p><a href="https://twitter.com/RemoteTeams">@RemoteTeams</a><br><a href="https://cultivatenow.com/">CultivateNow</a><br><a href="https://github.com/lukasz-madon/awesome-remote-job">Awesome Remote Jobs</a><br><a href="https://github.com/jessicard/remote-jobs">Remote-friendly companies</a><br><a href="https://weworkremotely.com/">WeWorkRemotely</a><br><a href="https://remoteok.io/">Remote OK</a><br><a href="https://jobspresso.co/">Jobspresso</a><br><a href="http://www.workingnomads.co/jobs">Working Nomads</a></p><p>And those are just a few. Good luck!</p><h3>Cheers!</h3><p><em>Originally published at </em><a href="http://shellscape.org/2016/11/28/pants-optional-working-remotely"><em>shellscape.org</em></a><em> on November 28, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68468286b286" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rebuilding a Personal Brand]]></title>
            <link>https://medium.com/42hire-don-t-panic-just-hire/rebuilding-a-personal-brand-7e0317fc42f6?source=rss-a90ccd0747d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e0317fc42f6</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[personal-branding]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Andrew]]></dc:creator>
            <pubDate>Thu, 17 Nov 2016 19:15:24 GMT</pubDate>
            <atom:updated>2016-11-17T19:15:24.585Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NBoEo5imWuOsSIRhqLqRjA.jpeg" /></figure><p>Complacency. It’s the worst. Grab a coffee, we’re about to board the <a href="https://i.chzbgr.com/full/1324739328/hC8866755/">failboat</a>. We all know that company brands are of paramount importance. But personal brands are often overlooked. They speak to your abilities, they’re a realtime, interactive, functional resume. And your brand speaks volumes about who you are. What happens when a personal brand falls by the wayside? I learned the hard way.</p><blockquote><em>It’s never crowded along the extra mile. — Wayne Dyer</em></blockquote><p>My personal brand peaked in 2012. I was working with/on the <a href="https://jqueryui.com/">jQuery UI</a> project, I was attending events (thanks much in part to my employers at the time), I was doing some occasional speaking, and my online presence was never more prolific. And then it all went to shit.</p><h3>Ground Up</h3><p>I started getting a modicum of notoriety in the Freeware space in the early 2000s with some Windows apps I had written, and it’s what landed me my first job out of college. I built shellscape.org around that, and used it as a landing for all of my projects. As I added more projects, I added a small blog to the site.</p><p>It was really <em>“the jQuery Company”</em> that helped build my brand the most. I was one of <em>those people</em> who thought that Twitter was a passing fad and that the concept was silly. But the company asked assertively that I sign up and be active promoting the company’s work, and my own. They pushed me to speak at small gatherings and they got me going to conferences and talking to heavy hitters in the front end development space.</p><p>I had solid Twitter followers. I had enough traffic to my site to pull in $200 a month in AdWords.</p><h3>I’ve Made a Terrible Mistake</h3><p>At the crux of it, I became complacent. I moved on from the afore mentioned conference-enabling-employer to a really interesting startup, riding on the success of my previous position and my personal brand out in the open. It was a big pay raise and I was doing exactly the work I wanted to do. I was pumped.</p><p>It was during the 9 month stint with the startup that I began to let my brand slip. I wasn’t writing blog posts, I wasn’t really contributing to any notable open source projects, I stopped working with jQuery UI. I stopped participating on Twitter in my field. I was happy with my job and my pay, and bought a tear-down investment home that sucked up every minute of my spare time. I was adulting, but I was neglecting the thing that got my career to where it was.</p><p>Unfortunately the startup folded on a random Wednesday. I was not prepared for it. Fortunately, and <strong><em>due in large part </em></strong>to my visibility to peers in tech, I was quickly scooped up by a Twitter follower I had never spoken to prior. After a few weeks of interviews, and several competing offers, I started working at Gilt.</p><p>I was again awarded an increase in benefits and I was doing insanely cool work. I mean the stuff that makes you want to skip sleep for a week, that makes eating seem like an inconvenience. And there again, I slipped into deeper complacency with regard to my brand.</p><h3>The Sky is Falling</h3><p>Gilt was always a tumultuous business; it’s well-documented on a myriad of business websites and blogs. In late 2015 the company underwent significant layoffs. <strong><em>PANIC MODE</em></strong>. Then in early 2016 it Gilt was purchased by a larger corporation. Without going into detail — lots of people where <em>very</em> unhappy.</p><p>After sticking it out for the first quarter, I decided it was prudent to start looking at what was out there. I was really excited; there were great companies hiring at competitive salaries and even though the field for remote work was narrow (I’ve been working remotely since 2009) it looked like I was in good shape. Fast-forward two months and I was still looking. I’d been passed up by numerous companies. Some passed straight up, and for some I didn’t shine bright enough over other local candidates to warrant a hire. Let alone that I’d fallen into a maintenance culture with day-to-day work, which left me at a slight disadvantage as I wasn’t up and up with the latest tech. But I’d always been able to convince folks that I could pick up easily what I didn’t know (and I could/still can).</p><p>There was a deficit somewhere, and I had to identify it.</p><h3>Mirror Mirror</h3><p>After a significant amount of reflection and speaking with peers, I zeroed in on three conditions that were affecting my hiring process:</p><ol><li>I was way behind on the latest tech.</li><li>I had become awful at interviewing.</li><li>My personal brand was non-existent.</li></ol><p>Now see, I hadn’t had to give a work example or perform a test project for evaluation — ever. Not a single time in my entire career before recently. Sure, I’ve done some live coding but that’s never been a big deal. All of a sudden companies are asking me to build projects for interviews. Only a few took the time to look through my Github account and the work there. I had lost my brand, I had lost the wow factor. Another odd anomaly was that I hadn’t received a single referral. Movement throughout my entire career had been through referrals.</p><p>I wasn’t an attractive candidate. Nothing was making me stand out from the crowd. I didn’t seem like an authority on what companies wanted, because I’d become an authority only on proprietary tech within my current position. I lost the edge.</p><p>And as such, I was cold-calling folks for interviews who had never heard of me, and who’s recruiting gatekeepers weren’t fluent in the work that I had been doing. Hell, some of them didn’t even know what a “remote employee” was.</p><h3>The Lessons, They Have Me</h3><p>I quit looking for new opportunities. I decided instead to use the time I usually reserved for movies or heading to the bar to instead create a foundation for rebuilding what I had lost. And so I spent a few weeks recreating this website. I realigned to treat it as a weekly priority. I talked to a ton of successful bloggers in a range of niches and got solid advice. I spoke with some creative types on how to create a unique feel for the site.</p><p>I started publishing again. I started open sourcing and creating projects around segments of the work I was doing daily, and most importantly: whatever I was tinkering with on the side. I started posting to Twitter, LinkedIn, Medium, and Facebook. I got my ass into gear.</p><h3>Important Things are Important</h3><p>A personal brand in tech is so damned important. It’s a window into who you are and what you’re doing. It’s a launchpad for anyone who wants to get to know you, before you know, actually speaking to you first. It’s only been a few months and I’m already amazed how my work is making the rounds. It’s a small audience, but it’s an audience and I’m only going to continue to work to increase that.</p><p>Don’t <a href="https://www.youtube.com/watch?v=wl2uDi6Zju8">be me with cable tv</a>, don’t be this me. <strong><em>If you don’t have an established brand, create one</em></strong><em>.</em> If you have one, maintain it!</p><h3>Cheers!</h3><p><em>Originally published at </em><a href="http://shellscape.org/2016/11/18/rebuilding-a-personal-brand"><em>shellscape.org</em></a><em> on November 16, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e0317fc42f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/42hire-don-t-panic-just-hire/rebuilding-a-personal-brand-7e0317fc42f6">Rebuilding a Personal Brand</a> was originally published in <a href="https://medium.com/42hire-don-t-panic-just-hire">Don&#39;t Panic, Just Hire</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>