<?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 Formidable on Medium]]></title>
        <description><![CDATA[Stories by Formidable on Medium]]></description>
        <link>https://medium.com/@Formidable?source=rss-900ee8ad3db9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*toKgV-6mH27v1it4kB8rMQ.png</url>
            <title>Stories by Formidable on Medium</title>
            <link>https://medium.com/@Formidable?source=rss-900ee8ad3db9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:30:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Formidable/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[Being Formidable:]]></title>
            <link>https://medium.com/@Formidable/being-formidable-4849ef7f6c13?source=rss-900ee8ad3db9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4849ef7f6c13</guid>
            <dc:creator><![CDATA[Formidable]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 15:01:01 GMT</pubDate>
            <atom:updated>2016-03-22T18:43:25.475Z</atom:updated>
            <content:encoded><![CDATA[<h4>Talks and presentations that inspire the work of Formidables.</h4><p>Inside Formidable, we encourage collaboration and bold, well-researched ideas. Some ideas stick with you longer than others, and continue to inform you work, either directly or indirectly. Here are some that keep the creative fire burning for members of our team:</p><p><strong>kevin.kerr:</strong></p><p><a href="http://www.npr.org/programs/ted-radio-hour/449179937/open-source-world">Open Source World</a></p><p>“The idea that creating things freely and in the open, sometimes leads to things you never thought possible”.</p><p>I learned development via open source but got lost in proprietary systems somewhere along the way. This reminded me of it’s importance.</p><p><strong>ken.wheeler:</strong></p><p><a href="http://www.infoq.com/presentations/Simple-Made-Easy">Simple Made Easy</a></p><p>Rich Hickey emphasizes simplicity’s virtues over easiness’, showing that while many choose easiness they may end up with complexity, and the better way is to choose easiness along the simplicity path.</p><p>This presentation is beautifully articulated and really inspires thought around architecture. He explains some very technical concepts in a relatively casual nontechnical way</p><p><strong>paula.lavalle:</strong></p><p>[John Cleese on Creativity]</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FQby0ed4aVpo%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DQby0ed4aVpo%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FQby0ed4aVpo%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/45db80acbd9321e7bee4e31b082e5742/href">https://medium.com/media/45db80acbd9321e7bee4e31b082e5742/href</a></iframe><p>I highly recommend watching John Cleese’s lecture on creativity in its entirety; it is an insightful, engaging talk from one of your favorite professors.</p><p>​Learning the high value of play and humor came as a much-needed insight during a time I was considering my predisposition to extract playfulness from my colleagues to be, at best, a distraction; a reduction in the quality of their thinking and problem solving. To arrange for a space where creative ideas are more likely to sprout, it turns out playfulness and humor is exactly the sort of behavior that encourages a relaxed, expansive, contemplative mode.</p><p>“​Creativity is not a talent. It is a way of operating.</p><p>MacKinnon [a researcher on creativity] show that the most creative had simply acquired a facility for getting themselves into a particular mood (<strong>**a way of operating**</strong>), which allowed their natural creativity to function. MacKinnon described this particular facility as, “an ability to play.” He described the “most creative” when in this mood as being “child-like.” For they were able to play with ideas, explore them, not for any immediate practical purpose, but just for enjoyment. Play for its own sake. “</p><p><strong>eric.baer:</strong></p><p>[Let’s be mainstream! User focused design in Elm — Evan Czaplicki]</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FoYk8CKH7OhE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DoYk8CKH7OhE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FoYk8CKH7OhE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0ac45c0f8b36352da6b87fb67a177b1f/href">https://medium.com/media/0ac45c0f8b36352da6b87fb67a177b1f/href</a></iframe><p>Functional programming has been around for a very long time and there are dozens of papers and opinions pieces extolling it’s benefits. If functional programming is so great, then why aren’t we all using it? In this talk Evan Cazplicki, the creator of the Elm programming language talks about the disconnect between programming professionals and the academic community how we, and perhaps Elm in particular can bridge the gap and usher in the next era of programming. (edited)</p><p>I love this video in part because it’s not just pandering to an audience that already agrees with him. He explains how we might one day soon have something so much better and does so in a very pragmatic and lucid way.</p><p><strong>dale.bustad:</strong></p><p>[Package managers, graphs, and one million vertices — Andrei Kashcha]</p><p>(from last year’s CascadiaJS)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FvZ6Yhlxv7Os%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DvZ6Yhlxv7Os&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FvZ6Yhlxv7Os%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/32942d2b0dd799a49c7f0bd00e664790/href">https://medium.com/media/32942d2b0dd799a49c7f0bd00e664790/href</a></iframe><p>Lots of talks will show you something new, but this was the first in awhile that left me surprised and delighted with what is possible.</p><p>Thoroughly enjoyable, and made me want to build something :)</p><p><strong>ryan.ray:</strong></p><p>[ The best stats you’ve ever seen — Hans Rosling]</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fembed.ted.com%2Ftalks%2Fhans_rosling_shows_the_best_stats_you_ve_ever_seen&amp;url=https%3A%2F%2Fwww.ted.com%2Ftalks%2Fhans_rosling_shows_the_best_stats_you_ve_ever_seen&amp;image=https%3A%2F%2Fpi.tedcdn.com%2Fr%2Ftalkstar-photos.s3.amazonaws.com%2Fuploads%2F91206e56-87be-4387-830b-c38f37d02d78%2FHansRosling_2006-embed.jpg%3Fh%3D421%26w%3D560&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=ted" width="560" height="421" frameborder="0" scrolling="no"><a href="https://medium.com/media/97ac6a2941ae6b2f76981e48bbb5d52a/href">https://medium.com/media/97ac6a2941ae6b2f76981e48bbb5d52a/href</a></iframe><p>You’ve never seen data presented like this. With the drama and urgency of a sportscaster, statistics guru Hans Rosling debunks myths about the so-called “developing world.”</p><p>This piece is a collaboration of team members at <a href="http://www.formidable.com/">Formidable</a>.</p><p><strong>We Are </strong>a privately-held, bootstrapped firm based in Seattle, WA. Developing complete web apps, embedding experts in clients’ teams, leading technology-specific training — we tailor our offerings to our customers’ needs, be they startups or Fortune 500s. We’re pushing the bleeding edge of the modern web by advancing the open-source software we use, teaching and learning new technologies, and pursuing opportunities and growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4849ef7f6c13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Inline Styles and the Future of CSS]]></title>
            <link>https://medium.com/@Formidable/react-inline-styles-and-the-future-of-css-cbc85e74bc42?source=rss-900ee8ad3db9------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbc85e74bc42</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Formidable]]></dc:creator>
            <pubDate>Mon, 29 Feb 2016 18:04:05 GMT</pubDate>
            <atom:updated>2016-03-21T19:52:15.128Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>by Alex Lande, Front-end Engineer at </em><a href="http://www.formidable.com/"><em>Formidable</em></a></h4><p>Writing and maintaining CSS for large applications (and large teams) can be challenging. Teams often have trouble with brittle selectors, naming collisions, specificity, and pile-ups of dead code.</p><p>After seeing these issues first-hand on large projects, we built Radium: a JavaScript library for styling React applications with inline styles. In the context of a React application, inline styling elegantly solves many of the issues with large-scale CSS. It also gives you the benefits of a CSS preprocessor like Sass, with extra power for expressive styling.</p><p>In the screencast below, I compare the benefits of approaches like Radium to some upcoming and proposed additions to the CSS specification that will help make scalable CSS easy in the future, whether you’re using React or not. I’ll also cover:</p><ul><li>CSS Modules</li><li>Shadow DOM</li><li>CSS Variables and Custom Media Queries</li><li>Native CSS Extends</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fk3OF4A30jSQ%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dk3OF4A30jSQ%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fk3OF4A30jSQ%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6ab02071e161690e9171abc8eb9fb01/href">https://medium.com/media/d6ab02071e161690e9171abc8eb9fb01/href</a></iframe><p>Read the docs: <a href="http://stack.formidable.com/radium/">http://stack.formidable.com/radium/</a></p><p>Find the code: <a href="https://github.com/FormidableLabs/radium">https://github.com/FormidableLabs/radium</a></p><p>*This open source project was conceived and built at <a href="http://www.formidable.com/"><strong>Formidable</strong></a>.</p><p><strong>We Are </strong>a privately-held, bootstrapped firm based in Seattle, WA. Developing complete web apps, embedding experts in clients’ teams, leading technology-specific training — we tailor our offerings to our customers’ needs, be they startups or Fortune 500s. We’re pushing the bleeding edge of the modern web by advancing the open-source software we use, teaching and learning new technologies, and pursuing opportunities and growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbc85e74bc42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Victory.js]]></title>
            <link>https://medium.com/@Formidable/victory-js-3ad318862984?source=rss-900ee8ad3db9------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ad318862984</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Formidable]]></dc:creator>
            <pubDate>Mon, 15 Feb 2016 16:04:32 GMT</pubDate>
            <atom:updated>2016-02-16T19:45:36.806Z</atom:updated>
            <content:encoded><![CDATA[<h4>Data viz for regular horses.</h4><p><em>by @boygirl, lead engineer on Victory</em></p><p>I’m not a designer. I’m a JavaScript developer. When I write CSS it takes me longer than it should, and often ends with someone more talented indulgently explaining how I could have avoided making such a mess of things. So, while I can literally do the thing, I can’t claim to have design chops. I’m sure there are designers reading this post who feel similarly about writing JS. Of course there are those scarce and sought after few who feel equally comfortable with design and code, but most of us are not unicorns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCU_RFCXN0W770lQyAdWfw.png" /><figcaption>Victory.js</figcaption></figure><p>Most of us are just regular horses, and that’s mostly just fine. We specialize, we collaborate with people whose skills compliment our own, and everything runs smoothly. Until we try to write some data viz. Visualizing data effectively requires an extremely precise and dynamic relationship between data and visual representation.</p><p>When logic and styling don’t work together seamlessly, the resulting visualization are often ugly or worse- misleading! This tight coupling of concerns can make collaboration problematic. Until recently, my data viz projects almost always involved <a href="https://d3js.org/">d3</a>. The resulting workflow had me context switching between JS, CSS, and d3’s terse api, and slowed me down quite a bit. Whenever I had to make changes to some visualization I’d worked on, I needed to load all that context back into my brain. That meant reminding myself of d3’s oddities, and getting back into my shallow, somewhat bumbling CSS groove.</p><p>Then all of my colleagues started using React, and JSX, and inline styles, and I got to load up a bunch of new context! I won’t pretend like getting started with a whole new set of tools wasn’t difficult and a little demoralizing, but as I got more comfortable, I found I really liked it. Since I was writing in JSX, and using <a href="http://stack.formidable.com/radium/">Radium</a> for inline styles, I no longer had to switch between several files to work on a single feature. Instead, I could write a feature as an independent, self-contained component, with all the logic and style information it needed, and nothing more. This pattern was great for my everyday workflow, and it sounded ideal for data viz projects.</p><p>Unfortunately, using d3 and React together turned out to be… less than ideal. The two technologies interact with the DOM in wildly different, and incompatible ways. There are several clever hacks to make the two play nicely together, but knowing when, and how to employ these tricks is not a trivial task. After trying to fit square pegs into round holes for a while, we decided to write our own data viz components especially for React. Once we got started, we realized we wanted to do a lot more than just wrap d3. So we started writing a library called Victory.</p><p>Victory is an ecosystem of composable data viz components for React. It relies on d3 for its powerful underlying math, Radium for inline style management, and React for most everything else. We thought a lot about how to create an intuitive, flexible API, and I’d like to think it really shows. If you don’t want to take my word for it (and you shouldn’t, I’m incredibly biased), you can play with Victory components here in our <a href="http://victory.formidable.com/">interactive docs</a>.</p><p>Or check out this video where I explain in more detail how the pain points in our old workflow motivated us to build Victory, and show off some examples of Victory in action.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyuAdvxnK4IY%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyuAdvxnK4IY%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyuAdvxnK4IY%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/715ee59ace4f614c78190e0411cac46f/href">https://medium.com/media/715ee59ace4f614c78190e0411cac46f/href</a></iframe><p><a href="https://github.com/FormidableLabs/victory">FormidableLabs/victory</a></p><p>Made with ❤ by <a href="http://formidable.com/">Formidable</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ad318862984" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Only Correct Script Loader Ever Made]]></title>
            <link>https://medium.com/@Formidable/the-only-correct-script-loader-ever-made-de507420e2b8?source=rss-900ee8ad3db9------2</link>
            <guid isPermaLink="false">https://medium.com/p/de507420e2b8</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Formidable]]></dc:creator>
            <pubDate>Thu, 07 Jan 2016 16:11:39 GMT</pubDate>
            <atom:updated>2016-01-07T16:11:39.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NUr1sQqkxQ8mdAcrWWLvjg.png" /></figure><p>A team here at Formidable was recently tasked with choosing a JavaScript loader in order to dynamically load scripts in the browser. After exhaustively testing every script loader we could think of, we found them all to fail in at least one way. With a complete test suite in hand, we set out to build the first correct script loader ever made.</p><p>Today we’d like to introduce <a href="https://github.com/walmartlabs/little-loader">little-loader</a>; clocking in at only ~865 bytes (minified) and no dependencies!</p><p>For a more detailed overview you can watch our very own <a href="https://medium.com/u/2faba0eb37">Brian Beck</a> talk about some of the things that went in to creating little-loader including the comprehensive script loader test suite (script-atomic-onload) and a fancy SVG badge creator (badge-matrix).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FF080X3Tp6_8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DF080X3Tp6_8&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FF080X3Tp6_8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/35372359941c5689b8349ac5aff091f9/href">https://medium.com/media/35372359941c5689b8349ac5aff091f9/href</a></iframe><p>little-loader: <a href="https://github.com/walmartlabs/little-loader">https://github.com/walmartlabs/little-loader</a><br>Testing suite: <a href="https://github.com/exogen/script-atomic-onload">https://github.com/exogen/script-atomic-onload</a><br>Badge creator: <a href="https://github.com/exogen/badge-matrix">https://github.com/exogen/badge-matrix</a></p><p>Made with ❤ at <a href="http://formidable.com/">Formidable</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de507420e2b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>