<?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 Kyle Warneck on Medium]]></title>
        <description><![CDATA[Stories by Kyle Warneck on Medium]]></description>
        <link>https://medium.com/@kylewarneck?source=rss-dadc18750d28------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TqMId0Mdzdf4txPSPyeoCA.jpeg</url>
            <title>Stories by Kyle Warneck on Medium</title>
            <link>https://medium.com/@kylewarneck?source=rss-dadc18750d28------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:59:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kylewarneck/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What’s wrong with Silicon Valley?]]></title>
            <link>https://medium.com/@kylewarneck/whats-wrong-with-silicon-valley-b858c4707272?source=rss-dadc18750d28------2</link>
            <guid isPermaLink="false">https://medium.com/p/b858c4707272</guid>
            <dc:creator><![CDATA[Kyle Warneck]]></dc:creator>
            <pubDate>Wed, 26 Feb 2014 17:35:13 GMT</pubDate>
            <atom:updated>2014-02-26T17:48:58.412Z</atom:updated>
            <content:encoded><![CDATA[<p>Bill Wasik wrote <a href="http://www.wired.com/opinion/2014/02/silicon-valley-backlash/">a great essay</a> on what’s wrong with Silicon Valley in this month’s Wired. I thought he got a lot of things right and shared it on Facebook. . . <a href="https://www.facebook.com/kyle.warneck/posts/10100221091757274?comment_id=4114122&amp;offset=0&amp;total_comments=10&amp;notif_t=share_comment">And then my Facebook feed went crazy</a>.</p><p>I’m moving my comments here to add my two cents to the conversation.</p><p>I think there’s two things that are happening in Silicon Valley that are real.</p><p>Silicon Valley at its finest at its “Geeks in the Garage” moments. Where folks who like tinkering with stuff tinkered their way to something awesome. Those moments are about curiousity and the joy of building something cool. But the revolution has been comodified. Now every bit of tinkering is a Kickstarter project or a vc pitch away from being the next billion dollar acquisition. That’s always been there, but it feels like lately the ratio of garages to vc board rooms is out of whack.</p><p>The same thing happened to punk music and pop art. Silicon Valley has to figure out how to keep its success from killing what made it successful. Not only will we all make a lot more money that way, but it will be a lot more fun.</p><p>The second trend is the expansion of the cultural bubble that is Silicon Valley. There are conferences, parties, hackathons, meetups and events going on every night in San Francisco. A young programmer could live for years wandering only between their startup incubator to these events to their hacker house and back. It’s a land where everyone gets your JavaScript jokes and the t-shirts and the beer are always free. It’s not a bad life, but it means you’re living in an exciting and diverse place and walling yourself off from all that diversity. And that cultural bubble cultivates some pretty unhealthy world views (I’m looking at you Tom Perkins). Not everyone who writes code for a living is seduced (or even invited) into the cultural bubble. But there’s enough folks who live in that world and have enough power and money to make decisions that we should be concerned.</p><p>The challenge is to make tech more diverse, open and inclusive. It has to become a situation where when tech wins, everyone in the community wins. Because otherwise, all those Bud Light drinking, Internet Explorer users that don’t get invited to your meetups are going to smash the windows on your luxury bus.</p><p>It reminds me of one of my favorite Lemony Snicket pieces — <a href="http://occupywriters.com/works/by-lemony-snicket">http://occupywriters.com/works/by-lemony-snicket</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b858c4707272" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Learning to love “==”]]></title>
            <link>https://medium.com/@kylewarneck/learning-to-love-6275dbc8bd7a?source=rss-dadc18750d28------2</link>
            <guid isPermaLink="false">https://medium.com/p/6275dbc8bd7a</guid>
            <dc:creator><![CDATA[Kyle Warneck]]></dc:creator>
            <pubDate>Fri, 07 Feb 2014 03:08:05 GMT</pubDate>
            <atom:updated>2014-02-08T04:21:50.760Z</atom:updated>
            <content:encoded><![CDATA[<h4>the myth of avoiding type coercion in JavaScript</h4><p>Many JavaScript developers and a lot of style guides will tell you to avoid “==” in your code. And there’s good reason for that advice. “==” can lead to some crazy and unpredictable results.</p><p>For example:</p><p>0 == “0&quot; // returns true</p><p>0 == [ ] // returns true</p><p>“0&quot; == [ ] // returns false ??? wtf??</p><p>For a through look at JavaScript quirks see <a href="http://wtfjs.com/">wtfJS</a>.</p><p>The reason for this craziness is type coercion. Unlike “===”’ insistence on strict equality, “==” will try to convert the things on each side of the operator to be the same type. The rules for type coercion can be a little bit tricky and unless you know them well you may run into edge cases like the ones above. So, the common advice goes, avoid “==” and its type coercing ways at all costs.</p><p>But it turns out that running away from “==” doesn’t solve your problem. Double equals is just one of many many places in JavaScript where type coercion occurs.</p><p>For example:</p><p>“a”+ 5 // Returns “a5” because 5 is coerced into a string</p><p>or</p><p>var x;</p><p>if (x) { doSomething( );} // runs the doSomething function because x gets coerced into true or false.</p><p>There is a long list of JavaScript functions that use type coercion including most basic math operators and truth tests and really almost any method that exists for two types of objects (e.g. concat works with both arrays and strings).</p><p>Not only is this behavior pervasive in JavaScript, it’s well supported. Every browser supports type coercion going back many generations. And the spec for <a href="http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-262.pdf">ECMAScript 5</a> actually expanded type coercion rather. It’s clearly not going away.</p><p>So if we can’t avoid type coercion, we have no choice but to embrace it. As a community of JavaScript developers, we should review the rules and learn to love them. An excellent summary of the mechanics of type coercion can be found <a href="http://webreflection.blogspot.com/2010/10/javascript-coercion-demystified.html">here</a>.</p><p>A final type coercion fun fact- there is a slight performance hit on any function which has type coercion since at the very least it adds an additional type check to the function. That means that 5 == 5 is slightly slower than 5 === 5.</p><p>Craziness.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6275dbc8bd7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>