<?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 •?((¯°·._.• вкαя∂εℓℓ on Medium]]></title>
        <description><![CDATA[Stories by •?((¯°·._.• вкαя∂εℓℓ on Medium]]></description>
        <link>https://medium.com/@briankardell?source=rss-4b7e77c1355a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OcLFeK_-haVrrQfD.jpg</url>
            <title>Stories by •?((¯°·._.• вкαя∂εℓℓ on Medium</title>
            <link>https://medium.com/@briankardell?source=rss-4b7e77c1355a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 21:35:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@briankardell/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[Tony Stark’s Web Browser…]]></title>
            <link>https://medium.com/@briankardell/tony-starks-web-browser-ec7616324e6d?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec7616324e6d</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[voice-recognition]]></category>
            <category><![CDATA[standards]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Fri, 22 Sep 2017 16:52:21 GMT</pubDate>
            <atom:updated>2017-09-22T16:52:21.719Z</atom:updated>
            <content:encoded><![CDATA[<p>Hey… Did you know that there are APIs in the browser you’re using right now that can allow it to <em>talk</em> to you? I mean, I’m not 100% positive about that, but if you’re using a modern browser it’s almost certainly true. In terms of browser support, it’s more widely supported than a whole bunch of stuff we’re all using already — and, actually, has had support for longer than probably anything you’re excited about today. It’s not standard in the sense that there isn’t an “official standard” but it is pretty nearly so in the <em>de facto</em> sense (lots of stuff started out like this way back). Further, part of the same proposal deals with allowing you to talk <em>to your browser.</em> Holy shit. That bit is less widely implemented, but it is available in the releases of Chrome and derivatives so it’s still available for you to play around with for a shit ton of people.</p><p>Over the past few months I’ve been toying around with this a lot in my spare time, and I have written several pieces on my own blog. You might have seen a few weeks back on Smashing Magazine, <a href="https://medium.com/u/a0b0677819e4">Tomomi Imura</a> also beat me to the punch and posted <a href="https://www.smashingmagazine.com/2017/08/ai-chatbot-web-speech-api-node-js/">a very nice piece on how you can basically start building your very own Jarvis </a>(or Friday if you prefer) and it was so good that it caused me to go back and rethink what I was going to post to avoid overlap… So here are my pieces:</p><p><a href="https://bkardell.com/blog/The-History-Of-Speech.html">The History and State of Speech</a> introduces a brief history of us trying to make machines that speak and listen and explains the efforts to bring these abilities into the browser <em>starting in 1997!</em></p><p><a href="https://bkardell.com/blog/Greetings-Professor-Falken.html">Greetings, Professor Falken</a> introduces and walks you through the Text-To-Speech bits of the APIs and all of their wrinkles and warts.<em> It’s full of fun code samples and runnable demos.</em></p><p><a href="https://bkardell.com/blog/Basic-Voice-Speaker.html">You Don’t Say</a> discusses what I see as design problems with the existing APIs. It’s about how I’m papering over them myself and why as I attempt to figure out how I think this really <em>should </em>be explained in Extensible Web form. <em>It also has some fun code samples and demos to illustrate.</em></p><p><a href="https://bkardell.com/blog/Listen-Up.html">Listen Up</a> introduces and walks you through the Voice Recognition bits and also discusses its warts. It’s a little harder to demo, but there’s a number of code samples explaining.</p><p><a href="https://bkardell.com/blog/Voice-Recognition-Thoughts.html">Thoughts on Voice Recognition</a> discusses the design problems in those APIs in similar fashion to the one about TTS. It has lots of hypothetical code examples I’d like to see us make work and explains why.</p><p>If you’re not into all that reading but you still find this interesting, I gave two talks and led some town hall style discussion/Q&amp;A in which I attempt to be moderately entertaining/engaging. You can check those out and let me know: There’s <a href="https://www.youtube.com/watch?v=gJ0gYki6F9k">video of the one on TTS</a> and <a href="http://bkardell.com/presentations/chapters-web-speech.html">my slides</a> as well as <a href="https://www.youtube.com/watch?v=cxDMhqsMPds">video of the one on Voice Recognition</a> and <a href="https://bkardell.com/presentations/chapters-web-speechii.html">my slides for that as well</a> (this one includes many beautiful pictures of world famous fashion model/trend-setter Bruce Lawson).</p><p>For the next few weeks we’re going to try to make an effort to get together virtually via <a href="https://codeandsupply.co/chat">Code &amp; Supply’s Slack </a>on the #chapters channel between 6pm-8pm EST and try to build some things, play with the APIs and talk about problems and challenges if you’d like to join us there.</p><p>I’d like to talk about restarting some standards efforts on this with feedback from developers, wdyt? Interesting?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec7616324e6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Glory Days of the Web]]></title>
            <link>https://medium.com/@briankardell/the-glory-days-of-the-web-418d41c6d9df?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/418d41c6d9df</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Wed, 05 Oct 2016 20:33:28 GMT</pubDate>
            <atom:updated>2016-10-05T20:33:28.170Z</atom:updated>
            <content:encoded><![CDATA[<p>For the past couple of years, there have been a number of pieces lamenting the current state of Web development: It’s gotten pretty complicated. Very recently a <a href="https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f#.m50p34qi8">satirical piece on this subject</a> really struck a chord and got a lot of attention. Dion Almaer <a href="https://medium.com/ben-and-dion/i-want-to-go-back-to-the-1950s-of-web-development-fa69d7fe357a#.bqj5a5ug1">wrote a piece in reply </a>in which he introduced what I thought was a really good analogy — the rose colored glasses that we often see the past through…</p><blockquote>…it reminds me of folk who talk about the golden era of the 1950s in the US. It isn’t hard to look at the current political climate and long for another time. Remember the white picket fences? Life was so good! Those glasses sure are rosy though, and when you take them off you see a society that had huge problems…</blockquote><p>“Huge Problems” is an understatement at the level of “the surface of the sun is warm”. In many ways, if most of us were placed in 1950’s America we would characterize it as xenophobic, sexist and racist — but also not exactly afraid of taxes or the idea that the government had a big role to play. Today we squabble like it is an all-life-on-earth-ending decision to make what are historically very minor tax tweaks — we just know that the past was somehow better… They were the “glory days” and we don’t seem to give a lot of thought to why.</p><p>We seem to do this with everything — it’s kind of human nature I think. Ask a 50 year old about their teenage years and they’ll likely regale you with stories that make it seem pretty good. Now ask a teen how they feel you’ll likely get a very different perspective. Things seem to get simplified, polished and a little more rosy with time. Somewhere in between these is probably a fairly objective ‘reality’.</p><p><strong>The Web’s Glory Days that I don’t actually recall…</strong><br>Like Dion, I feel like we’re doing that a little with our perspective of writing for the Web. If what you remember (or the story that you’ve heard) is that “once upon a time we just wrote HTML (and maybe CSS) — there weren’t so many frameworks and programming to learn and life was good”— then we have very different recollections.</p><p>If you were writing only HTML and CSS before, for example, and you’re not anymore then you’re comparing apples and oranges. If you could before, you still can. However, in reality, most sites were not that, even “static” ones.</p><p>Did you manually copy, paste, edit things like your header and footer? If you did, you were one of a small few because these were problems that were obvious even in the mid-90s and answers were provided by even the earliest servers and many popular “IDEs” of the time or tools made it possible to do this as a ‘build time’ process.</p><p>Also obvious, even in the mid-90’s, was that no-one would sit and write HTML all day, every day. HTML was, by design, intended to be the lingua-franca for common understanding. It was the thinking that <em>most </em>of it perhaps would be <em>generated by a program, </em>not authored by hand. In fact, the very first significant use, even at CERN, involved writing programs that wrote HTML and TimBL’s original browser effectively hid the HTML from you.</p><p>To generate HTML from bits, to query a database or services and so on, to hide things under non-standard abstractions — you need a programming language. Enter the complexity and the variance.</p><p>Over the years I have watched as people built sites using tons of server-side and build tech in order to do precisely this. These involved choosing a server. Once you have a server, frequently there are N choices of languages you can use. Given a language there are frequently N templating languages and N possible frameworks you can use to express how those things pinned together. Some of them required compilation, many had a concept of ‘build time’ work. All of them also had to deal with server configuration that dealt with how you deal with things like threading, connection pooling, caching, etc. All of them dealt with databases, and so on. Did you use cgi/bin and Perl? Did you use .asp and COM? Did you use Java? If you did, did you use JSPs, FreeMarker, ECS, Velocity, JSF or Ice Faces? Did you use Struts, Spring MVC, Spark, Dropwizard? Did you transpile with something like GWT? Did you ever try thinking about portlets? Or did you prefer Ruby on Rails? Or PHP? If it sounds like I am reaching for examples, I can assure you this is an <em>exceptionally</em> abbreviated list of actually popular approaches that I have encountered. People who dealt with those all had similar complaints to the ones I hear now.</p><p>Building this stuff — especially building it well, has never, to the best of my knowledge, or in my experience, been simple.</p><p>It’s never <em>not</em> involved a lot of variety of choice or strong opinions about “the right way” or what is “good enough” or tough/interesting challenges regarding how to fit into existing ecosystems. Instead, primarily what seems to have changed is where it’s possible to build what.</p><p>Today it is possible to build rich, engaging UI that happens on the client that wasn’t really possible before JavaScript — but it’s also not exactly new — merely the level at which we aspire to do it is. By the mid-2000’s sites were getting pretty rich. The reason we have HTML5 is that JavaScript allowed us to not stand still and wait for something better to come along.</p><p>Was this the simpler time? Not for me it wasn’t — in addition to all of the server frameworks, every week there was a new library. Prototype, Scriptaculous, MooTools, Dojo, qooxdoo, Bindows, YUI, ext.js and many more, until finally jQuery. But jQuery itself was pretty low level and stopped there as opposed to something like ext.js which came complete with a UI toolkit. This is where a lot of frameworks come in today — it’s not <em>necessary</em> maybe to have a ‘client approach’ and a ‘server approach’ be quite so far apart — maybe that’s good.</p><p><strong>An added bit of non-technical complexity</strong></p><p>Somewhere along the way, we seem to have had a split. In some orgs that I worked for, this was all considered “equal”. I was a “full stack” developer and the whole stack was equally important. In other orgs, there were “front-end” developers and the front-end was an important discipline on it’s own, but it was separate from “design”. Design was more of a static deliverable of HTML and CSS and maybe some “demo-y” JavaScript that we probably wouldn’t really use. Some people saw that as lesser, some people just thought of it as different. In still others all of this was somehow viewed as “lesser” and “not real programming” and so many “real programmers” avoided it and handed it to people who were actually primarily interested in designs and didn’t have experience with “real programming languages”. In the meantime, a lot of people strode weird middle grounds.</p><p><strong>So… suck it up?</strong></p><p>No, none of this is to say “suck it up folks, that’s just how it is”. I too feel like it’s gotten a little overwhelming. But I’m more overwhelmed by simpler things. It was a really nice quality of jQuery, for example, that you can simply grab a release off a CDN, include it however you like, and go. Frequently, a simple &lt;script&gt; include was “good enough” and you were off to the races. Today, a lot of projects lack that level of friendliness. You need to have node installed. And NPM. And probably a certain build tool. And maybe something like TypeScript — just in order to get a single file. And it might be that that file really wants to work with a package manager that you don’t know about so you have to get that — and so on. It’s hard to not feel overwhelmed by that alone. We should really work on that.</p><p>But I’m also fairly realistic about what we can/should do about it I guess and why I think it is that way. History shows that eventually we do shake the good bits out into standards — and it’s slow, kind of painful and more than a little overwhelming at times along the way. But I find hope in knowing that we’re all working on making that process a <em>lot </em>better by reconsidering how we approach standards (see also <a href="https://extensiblewebmanifesto.org/">The Extensible Web Manifesto</a>, <a href="https://wicg.io/">The W3C Incubator CG</a> and <a href="https://chapters.io/">Chapters</a>). If we can make this lifecycle better, that could be pretty dramatic. The best thing about standardizing things on the client, in my opinion, is that there’s only one. JavaScript isn’t really in competition with 17 other languages and there is ultimate only the DOM. That’s at least something promising.</p><p>But let’s also try to remain realistic in how we compare the present to the Glory Days.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=418d41c6d9df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developers Are the New Superpower]]></title>
            <link>https://medium.com/@briankardell/developers-are-the-new-superpower-7c67d3ac645?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c67d3ac645</guid>
            <category><![CDATA[standards]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Sun, 03 Jan 2016 23:41:43 GMT</pubDate>
            <atom:updated>2016-01-04T17:21:50.364Z</atom:updated>
            <content:encoded><![CDATA[<h3>Developers Are the New Superpower: Matter.</h3><p>Chances are pretty good that you don’t write standards, a vanishingly small number of people do. For many of us, it might almost seem that they’re handed down to us from the gods of Mt. Standard. Sometimes, if we’re lucky, we’re thankful to them for our simple gifts. More often, it seems, we spend an inordinate amount of time praying for the wisdom to understand them. Frequently we question them, and occasionally we even curse them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*cA9xLwNZ0f070kGEId0g4A.jpeg" /><figcaption>The Gods of Mt Standards as depicted by Giulio Romano in The Chamber of the Giants, 1532–1534, fresco. Palazzo Te, Mantua</figcaption></figure><h4>The Historical Power Structure</h4><p>As a concept, standards themselves are a relatively modern human invention that came along with industrialization and trying to operate at scales we’d not previously imagined. For the first 50 years or so standards dealt with physical resources: Trains, electrical devices, metallurgy, automobiles, construction, etc. In this world, standards were effectively an exercise in getting very wealthy and powerful players to agree on what they’d provide to the masses. For a long time, businesses even fought standardization, but it turns out that really the only way to operate at very large scales is through increased common understanding and agreement. The more standard something is, the cheaper and more reliable it gets. In this era, the wealthy makers of iron, steel and silicon were the indeed the superpowers. If there ever was a thing like “Mt Standards” it was then.</p><h4>Stolen Fire</h4><p>But — if you do anything involved with the creation of something for the Web — whether that is design, writing HTML, designing service APIs, making games, a CMS or <em>anything else</em> there’s something you should know:</p><blockquote>We matter more in this equation than many of us realize.</blockquote><p>Software, especially open-source software, changed the game radically. Bits, unlike raw materials and heavy manufacturing, are cheap. All you need in order to innovate something interesting is a decent computer.</p><blockquote>The Web and indeed, the Internet itself are living reminders of the fact that we matter.</blockquote><p>While many people might not realize it, HTML was an upstart that competed with long-standing ISO standards like SGML. The TCP/IP we call the Internet today was an upstart that went up against the OSI “Seven Layer Model” which had been brewing in ISO for almost a decade. What happened? In a word: We chose them and rejected others.</p><blockquote>While a standards body approved solution is appealing, it wasn’t all that mattered at the end of the day. So what did?</blockquote><p>The <em>reasons</em> we chose them are complex and multi-layered to be sure. Volumes could be (and have been) written about it. It’s not simple. Both HTML and TCP/IP were simple compared with their counterparts. Discussion was also more open early on and they followed the IETF model of “rough consensus and running code” not process, that meant more early adopters. In the case of HTML, it inspired the right people at the right times to make browsers, and to make content, and at some point this became a feedback loop that led to exponential growth.</p><blockquote>Whatever the reasons many reasons, however, the fact is simple: We developers chose to make one of them a success and not the others by selecting them. We learned them. We tried them. We advocated that they were worthwhile to business, which, in turn, built systems with more demand for those skills.</blockquote><h4>The Value of Standards</h4><p>But — as importantly, when things started to look inevitable, <em>then </em>we standardized them. Why? Because useful and widely adopted is just that, it’s still not standard. There are benefits at all levels to eventual collaboration at massive scale with powerful players, from performance to stability to interoperability guarantees and legal protections. Groups like the W3C address a lot of this.</p><blockquote>In short — there’s real value to crossing the standards finish line and that’s the one thing that standards bodies are historically really good at: Crossing the finish line. Crossing that line provides another major boost.</blockquote><p><em>Innovation</em> from within a standards process has a much poorer track record — and this creates a hard situation.</p><h4>Developers: The new superpower.</h4><p>So, a few decades in, we’re still trying to figure out how to do it really well. You matter, but the way in which you matter is historically messed up. The economics of developer participation has historically been broken. In practice, we’re frequently left to the tail-end of a very slow process. A wrong turn by a standards body can cost many years while walled-garden competitors run forward. So how do we do better?</p><p>Well, there’s not a simple silver bullet that will solve all our problems with a single shot but a lot of us have been hard at work on reforming things so that you can <em>matter more effectively. </em>Ideas like <a href="https://chapters.io/">Chapters</a> provide an outlet for groups to discuss provide feedback into developing standards in deep ways. The <a href="http://wicg.io/">W3C Incubator Community Group</a> provides a kind of ‘pre-standards’ process which lets things enter the pipeline, be discussed more openly and less overwhelming ways and helps good ideas from anywhere find traction, supporters and champions to navigate the subsequent process. Working groups themselves are making more efforts to be connected and open, and as a policy, we’re fighting to make this the norm.</p><h4>One Simple Trick to matter more</h4><p>It seems then that the core of the challenge is to find better ways to connect developers just like you to a better standards process: To tighten the feedback loop between standards and developers, avoid wasted time, allow ideas with the hope of adoption to rise and those without to fall more efficiently. Here’s one thing you can do with a seriously low barrier to entry: Can you tweet or share an opinion? If so, you’re capable.</p><p>The W3C has an elected body called the Technical Architecture Group, or TAG. It’s a kind of steering committee for the long term vision of the Web and it is chaired by the Director of W3C/creator of the Web Tim Berners-Lee. In 2013, with support of developers like you, we convinced electors to vote in a new breed of folk who understand this and can help steer the W3C back on track. In 3 years, we’ve managed to keep this up and I think we’ve seen a number of positive developments — those I mentioned above, unprecedented cooperation with other groups like IETF and ECMA, co-authorship of and efforts to help drive the ideas of <a href="http://extensiblewebmanifesto.org/">The Extensible Web Manifesto</a>.</p><blockquote>Perhaps most importantly in my mind, however: In this time, members of the TAG have made substantial efforts to bring developers into the discussion and stay connected to reality. They’ve helped organize a number of free events that allow developers of all sorts to town-hall-like discussions. It’s much easier to rally support or correct course if we’re actually part of the discussion.</blockquote><h4>If this seems positive to you</h4><p>There’s an election for TAG underway right now — it closes on January 8th, 2016 at midnight EST. It seems to me that one candidate has an exceptional strength that the TAG could really use. If you think that it’s important for the W3C to engage developers then Andrew Betts seems like a really solid asset. First off, he works most directly with developers. He isn’t from a browser vendor but he works regularly to bring them together with developers just like you. He organizes some of the best events in the industry like <a href="https://edgeconf.com/2015-london">EdgeConf</a> which doesn’t have speakers and lone talks but panels made up of all sorts of interests that get together and discuss with the wider audience and unconference activities for deeper discussion. By and large, he’s from “outside the process” in the same way that most of us are but widely respected by those on both ends of the equation. Andrew could be a great add.</p><p>However, the fact that people are generally happy with TAG and this being a small election with a number of good candidates means that there is a certain amount of apathy. In this situation, few will even vote and those who do are more likely to just vote based on simple name recognition of someone they respect. We’re lucky that in this case that’s still likely someone good: David Barron and Sangwhan Moon are excellent candidates with this advantage.</p><p>But if, like me, you think that Andrew’s qualities are something we want: We need to prod the system.</p><p>Either way — we should prod the system. All it takes is a simple tweet of support, a short encouraging email to a W3C member if you know one, a share on social media. Whether you agree or disagree, I’d like to encourage real developers to speak up. I’ve made my case, feel free to make another. It matters. Believe it or not, you probably have some connection to at least one of the roughly 400 W3C member organization who can cast a vote. It’s worked before, organizations <em>will </em>listen to developers if we speak up.</p><h4>So this is it…</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*VUJoLexwNtC-lT_ZkKvH6w.jpeg" /><figcaption>Lee Oscar Lawrie’s statue of Atlas in in Rockefeller Center, NY</figcaption></figure><p>Developers are the new super powers — we hold up the standards world: The future is ours to shape. The only thing I can say for sure is that you’ll never convince anyone if you don’t try.</p><p>I’d like to see Andrew get one of those seats and the other to go to David or Sangwhan. What do you think?</p><p>If you want to be part of the conversation — speak up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c67d3ac645" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reflections on Engineering]]></title>
            <link>https://medium.com/@briankardell/reflections-on-engineering-db2c52d72113?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/db2c52d72113</guid>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Sat, 20 Jun 2015 21:01:19 GMT</pubDate>
            <atom:updated>2016-10-14T14:58:55.793Z</atom:updated>
            <content:encoded><![CDATA[<h2>Reflections</h2><p>Very early in my career, I was lucky enough to stumble on Web development before it really became a “thing” and landed an apprenticeship (and later job) in a new, small experimental arm of an established consulting firm which primarily worked on embedded systems. I was employee #2 of this new effort and we worked in an attic loft. Nearly all of my experience before this was from books and pure experimentation/willpower to accomplish something. I worked there for about a year, mostly by myself churning out code in somewhat typical fashion: Someone said “make it look like this picture” or “this stuff needs to come from a database” and that was pretty much it. I worked too hard, I was usually scared to death I&#39;d never be able to figure out that one new technology that each project introduced me to and quite often it was just struggle to finish and make something work.</p><p>I was learning a lot about APIs and the languages I was working with, but very little about how to do my job. If this sounds confusing to you, you&#39;re not alone: I&#39;ve been writing software professionally for about 20 years and I&#39;ve worked on a lot of teams with a wide array of people and initially nearly all of them hold the position that that <em>is</em> my whole job. So, let me explain the counterpoint and how I came to hold this idea about what my job really is.</p><h3>My First Lesson…</h3><p>About a year into my first job, an opportunity came up for a project that the boss didn&#39;t want to pass up: A former client with a startup who had gotten into some trouble with a deadline had heard we were doing this sort of thing now. Success would likely mean more work — but it was considerably over our heads. It dealt with some ideas for which there were only two books we could find and it seemed at the time like pretty high-end nerd stuff. We&#39;d be working with the author of those books directly. The deadlines looked clearly impossible even if it were something we&#39;d understood well. Still, the boss signed the contract on faith and almost immediately we lost the only other employee we had — it was just me.</p><p>So the boss negotiated with an old partner who had left the company to come back and help out. His name was George and, actually, he was the one that recommended me for the position in the first place. He was friendly and quiet — a lanky guy with beard and glasses, a seasoned engineer who was great with C but he knew nothing about the Web. He came back on one condition: He was running the team — no questions or pressure or status inquiries from the boss. It seemed strange to me coming from this quiet and very amiable guy.</p><p>On the first day, we had a meeting. I brought a thick printout of 4 .asp pages — each tens of thousands of lines of vbscript that represented 4 pages in their application that they had nearly completed. They said “use these as a guide and do these other 6 pages in the next 2 months — we&#39;ll do the rest”. They had a virtual army of people banging away on keyboards because in 2 months they had to ship something like 40 “pages” (their application) and in the past 3 months they had completed just the 4.</p><p>“Let’s go over these and I can explain what I&#39;ve already figured out…” I said.</p><p>“No, tell me how a Web page works” he replied. I gave some quick explanation of HTML documents and elements and tried to move on.</p><p>“No, but tell me how it <em>works.” </em>After much back and forth for a couple of hours I said “ok, are you ready to get started?” He cocked his head to the side, “What do you mean? We are started.”</p><p>Literally all day long we drew diagrams on the board and discussed urls, query strings, HTTP methods, their relation to pages and state and HTML elements, frames, JavaScript, .asp and on and on.</p><p>That night I didn’t sleep. I pondered over those printouts, I made notes. I edited code and tested my understanding of it (usually to ill effect). I did math involving the number of people typing, the lines of code, the work cut out for us and how much it cost us to have lost an entire day talking.</p><p>The next day I felt a little better: All I needed was some progress then surely I’d settle down. But that day too, we talked — we talked about OLAP and SQL and COM and how you&#39;d use them with .asp and IIS and HTTP. How the server was communicating and what we painting on the screen. Where was the state and so on. Every so often the boss would peek in and look worried and George would quickly dismiss him.</p><p>On day 4 I had something of a meltdown: “This is killing my career,” I thought. I confronted him “George, I don&#39;t know what’s going on here. Maybe you can afford to do this, but I have to pay my rent — I work here day in and day out. That guy pays my salary and this contract will pay us both and give us more work. We&#39;ve nothing to show and we&#39;re closing in on a significant fraction of the time we have which was already too short. By the end of next week, we have to have one of these done. The boss wants to see progress. The client wants to see progress. My job is to write this code, not to help you feel like you&#39;re learning or have interesting conversations. I don&#39;t know what happened between the two of you, but you need to get past it — I can&#39;t let some power trip or revenge take me down like this.”</p><p>George was quiet. He took a deep breath through his nose and looked thoughtful about my comments. He reached out to the table and slowly opened a box of chocolate covered cherries that was sitting there, unwrapped it and popped it into his mouth and shook his head. He didn&#39;t look angry. He didn&#39;t look frustrated or guilty. He looked more the way a grandfather might look just before he passed down some sage wisdom — just trying to figure out how to explain. I’ll try to summarize some of the wisest words that ultimately came…</p><blockquote>“Any monkey can write code,” he said, “it doesn&#39;t always turn out well. Why do you think I am here? I’m not the only engineer in town — you have others right here. Your boss is a skilled engineer and just next door you could get two guys at half the price. I&#39;ll tell you why: I&#39;m here because this project is in trouble. Coding as fast as you can won’t work, and your boss knows that I won’t do that. Imagine we did. Even if we didn&#39;t encounter problem after problem with code we didn&#39;t fully understand — working 15 hours a day odds are still about 99% that we&#39;d fail. Who would that serve? We&#39;d be battered and broken — not us. Would it make your boss happy that you came up short? Not likely. Would it make his client happy that he failed to ship? Would you get follow-on work? Not a chance. That’s our job Brian — successfully shipping something that actually meets their needs. It involves programming — hopefully good programming — but the programming and the lines of code isn&#39;t what the client wants, it’s the end result. They have to ship. This is make or break for them. You think I&#39;m somehow not taking it seriously but I am: I want them to succeed, that’s all I want. That’s what your boss understands, and why he had the faith to bring me on. So I&#39;m asking you to trust me — we&#39;re going to get this done and give them what they really want — the thing they really need to be done. Trust me, the rest will take care of itself.</blockquote><p>Over the course of the next 2 weeks it was slow — we completed one page. It was a tiny fraction of the amount of code it had taken them. It seemed like a minor win, but I was still full of dread: We were behind. It took a week and a half to complete the next one, a lot of that was readjusting some earlier assumptions that turned out to be wrong, but the code actually got smaller. The last 4 fell like dominoes in just a few days and we were done — early. Each one was really easy to craft and hardly took any code at all.</p><p>When we synced up with the main team they confessed that they were way behind. They were impressed — despite having all of those people they&#39;d completed only 10 and they were more than a little worried about their quality. Could we do a few more? In the end, in fact, the lion’s share of the total work was done by our team (mostly George too because as it turned out, I had planned a vacation thinking we were done) in an amazingly short time.</p><p>Everyone was happy. I learned an incredible amount of engineering which has continued to help me throughout the years. George was a great teacher. But the real value I took away was much bigger and more abstract than this.</p><blockquote>The end goal is to help the client be successful.</blockquote><p>George wasn&#39;t religiously following engineering practices because some study had shown that over time it would lower maintenance cost or something abstract. Of course, he employed good principles which helped with that, but — he wanted to ship. That’s what everyone wanted. He was simply using whatever powers he had at his disposal to solve the <em>right</em> problems rather than the wrong ones.</p><p>I, my boss, and even the client mistakenly understood the problem to be “how do we measure and knock down units of work to do variants of what someone clumsily hacked together before they really understood the problem” . George was able to see the greater issue. Originally, their product shipped on time with two completely different approaches inside — that’s not great engineering, in fact, it’s terrible. George never tried to tell them they should do otherwise — he simply showed them a better way, he delivered and optimized everyone’s happiness. If they had any sense, they went back and learned the right lessons.</p><h3>On my own…</h3><p>Over the years I&#39;ve frequently been in situations where I&#39;ve had to apply these lessons. It’s not always easy and sometimes the hardest part is the fact that under a lot of pressure, no one can see the forest for the trees. No one wants to hear you — you can frequently be misunderstood as shooting for unaffordable perfection or just “difficult” even if that is pretty clearly not the case. But let me share just one of many stories about how this matters in a very real way — and why it’s worth caring and having the integrity to focus on the non-programming bits.</p><p>Several years ago I was contracted by a large company for 6 months to complete a simple task: They had a number of systems which were written in Java or .NET. After years of discussion and planning they had timetables and budgets and a directive to convert all of their existing .NET applications to Java. I was hired to do one. They practiced a waterfall methodology and had already spent tons in codifying the requirements and analysis of the existing system and so on. More or less a straight port. They wanted me to potentially suggest a few minor UI tweaks since I was pretty good with JavaScript and CSS, but otherwise straightforward. I spent my first two weeks reading requirements, looking at code, trying to get set up and run through the existing system and so on. At the end of all of this, I had a nagging problem: I still had no idea what this system was actually <em>for </em>and I couldn&#39;t even get it to do simple things without crashing — even the one in production.</p><p>At beginning of the third week I was really torn. I just didn&#39;t feel like I understood the problem. I could very easily “port” the NET code to Java more or less class for class, but how could I be sure I was doing it right — how could I test it? How could I suggest UI enhancements if I didn&#39;t understand what I was enhancing? I honestly couldn&#39;t afford to lose this job by pissing someone off, I&#39;d just bought a house and my car died — things were going badly and I was stretched far beyond my limits. Part of me wanted to come to work, do the conversion and take the paycheck and hope. The other part of me won that day though as I remembered George’s words and I walked into my boss’ office and asked him for a moment of his time. I explained all this and asked if perhaps he could point me to some actual users of the system who could just let me observe how they used it for an hour or so so that I could actually understand the job I was trying to accomplish — not the programming, the actual <em>thing</em> the program was supposed to do: The intent. After a while, to his credit, he agreed and he sent a few of us, not just me.</p><p>Afterward, we met again to compare notes and, without fail the experience was universal: <em>They don’t use it.</em></p><p>What?</p><p>Why?</p><p>It’s pretty simple actually: It doesn&#39;t work for what it is designed for — and it wasn&#39;t designed to do what they actually need. So instead, they do all these other crazy things with other systems… They each do it their own way — but they&#39;re all just solving the same problems on their own. What’s more, it’s not that involved — just clumsy.</p><p>So, in the end — the budget to convert a useless system from one language to another was applied toward the valuable task of just writing the (much, much simpler) system that they <em>actually</em> needed in the ‘right’ language in the first place. I&#39;d helped them not just to be successful but to understand what success meant in the first place: The real problem wasn&#39;t just “we have an application written in a language we don&#39;t want to maintain anymore” it was “we have a useless application and we never actually solved the problems that needed solving in the first place”.</p><h3>In short…</h3><p>Many of us, and those we work with would frequently like to imagine that our job is just programming. It’s easy to forget that, and while yes, you have that rare skill — your real job is in making the project successful. It’s that same quality of solving problems that occasionally gives you an insight that others can’t have. What someone is asking you for is frequently abstract, it often lacks an understanding of the medium and that means various choices incur significantly more cost than others. It’s quite possible (at least in my experience) that with just a little cooperation and effort you can adjust expectations, correct problems with deadlines and budgets and just generally increase the overall happiness of everyone. It doesn&#39;t always work — sometimes people will misunderstand your position or even be frustrated by it. But, after ~20 years of doing this, I can honestly say that in the end my results have been overwhelmingly positive. In the end, people tend to come around and frequently those who most misunderstood initially have later come to be some of the best partners.</p><p>I think my friend Mark Nottingham summed it up well recently on Twitter. I’m not sure he meant precisely this, maybe I just see this as a nice summary because it’s on my mind, but I like it regardless…</p><h3>Mark Nottingham on Twitter</h3><p>Eventually, you figure out that the code itself doesn&#39;t matter for shit; its effect on the world around you is what matters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db2c52d72113" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Betts Choice: Because you can help shape the Web]]></title>
            <link>https://medium.com/@briankardell/the-betts-choice-because-you-can-help-shape-the-web-c36769a73d51?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c36769a73d51</guid>
            <category><![CDATA[standards]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Fri, 24 Apr 2015 02:24:41 GMT</pubDate>
            <atom:updated>2015-04-24T02:24:41.539Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Betts Choice: Help shape the future of the Web</h3><p><em>The Web is something I really care about. It’s not just because it’s my livelihood or because we can use it to do really cool stuff, but because it has absolutely changed the world. I think about it a lot. There are a lot of potential futures, which will we choose? How will we make the future that we want a reality? Of course, it’s all debatable, but I want to tell you about something really simple that you can do and explain why it just might matter a whole lot over time.</em></p><p>A few years ago, the future of the Web was starting to seem a little bleak: Standards were perennially stalled and their development closed to developers. Microsoft had kind of given up and tried to move on. The brief thrill when work began on HTML5 soon showed new challenges: It still took too long, things didn’t always pan out after a lot of effort, there was a deep schism. While better in many ways — it still wasn&#39;t good. It’s easy to throw up our collective hands and give up — but some people didn’t.</p><p>The net result is that we&#39;ve seen a slow move of standards bodies over the past 3 years to adapt and change. Every couple of months, if you&#39;re watching carefully, you can see positive new signals.</p><p><em>Progress that seems small can have outsized impacts as they build over time, and, in fact, it’s the only way that change at this scale really happens.</em></p><p>The <a href="https://extensiblewebmanifesto.org/">Extensible Web Manifesto</a> wasn&#39;t alone in orchestrating all of this, but it has certainly inspired a lot of positive conversation and fostered much adaptation by getting people to agree and articulating some of the major problems and potential solutions and get people talking…</p><p><em>And in a way, you can thank folks just like you for making it possible..</em></p><p>One can certainly argue (and do) that there are many variables, in my mind the <a href="http://www.w3.org/2001/tag/">W3C TAG</a> (Technical Architecture Group) has been important in beginning to address them. If you’ve never heard of the TAG, it is a small, partially elected body within the W3C which is in part a steering committee looking out for the future of the Web itself and keeping/driving a sane architecture. If you&#39;re wondering why or how you could have never heard of it it’s because until that election, this was a seriously “inside the beltway” kind of committee and they mostly didn’t discuss things that average developers cared much about. That is, until a few years ago when we decided to change all that when a slate of reform-minded candidates ran public campaigns.</p><p><em>Importantly: People just like you helped those people get elected by sharing their support publicly via social media and emails to W3C members. Without those efforts, it’s very possible we’d be in quite a different place right now.</em></p><p>Having a public election and much support from the public has allowed TAG to give voice to the technical <em>importance</em> of solving many of these problems.The Manifesto itself was in part written/driven by then newly elected members seeking reform, and the TAG has played a big role in outreach.</p><p><em>But making it public grants it a unique bully pulpit as a statement of our collective desires and I think that’s had a positive impact — in effect, using the existing system and mechanisms to help it reform itself.</em></p><p>If you&#39;ve read Jory Burson’s <a href="http://alistapart.com/article/standardization-and-the-open-web">recent piece about standardization</a> on A List Apart, you can probably appreciate the value of understanding existing systems and knowing how to work within them, so here are the more boring details: Five of the nine seats on the TAG are elected, in staggering terms such that we should have one election per year. In some cases, however, an elected member has to step down and we have a special election. In this case, Mozilla’s Dave Herman is stepping down a year early because of other commitment pressures and now there’s a choice to make about our possible futures. In this case, whomever is elected will serve out the rest of his term until the next regular election and there are 4 candidates.</p><h3>Let’s shape history…</h3><p>Very simply, by throwing our support behind a candidate, we can help shape the long future — small events can have big ripples. Here’s why I am supporting, and why I&#39;d like to see other public support for Andrew Betts.</p><p>Candidates for these positions are always tricky: Virtually all of them are imminently qualified, technically speaking and what it often comes down to is a question of who will add the right value in the overall composition of the current group at this point in time. Sometimes, as is the case here, it can be a struggle. Of the four candidates, Mozilla’s David Barron and FT Labs’ Andrew Betts stand way out to me as <em>really</em> superb options. We’ll be lucky to have either one of them serve to be honest. At the end of the day though, we have to pick one. While I hate lose a voice from Mozilla at the table (especially one as good as David Barron) we can rest a little easy knowing that this is a one year seat — we&#39;ll have a chance to place them back soon if we want — and Andrew Betts brings unique qualities that I think can provide the right kinds of ripples at the right time.</p><p>First off, two of the major things that TAG does which are really valuable surround getting the right people together and talking or communicating a coherent message. At this, Andrew basically has no equal. The events he helps organize and shape, like EdgeConf are generally thought of as monumentally successful examples of good communication around technology. What his experience would bring to efforts like Meet the TAG and the Extensible Web Summit or even just TAG meetings with invited experts will undoubtedly transfer value to the whole system way beyond the duration of his service. Secondly, because he <em>is</em> a developer — he’s involved in standards at both ends interacting with standards organizations, other experts within the community, and regular developers runs <a href="https://cdn.polyfill.io/v1/docs/">polyfills as a service </a>helping across a wide range of Web disciplines within a professional, standards loving non-browser making organization. He was involved in jump-starting Service Workers and getting that off the ground. In short: He has a unique record and a good pulse on things in a way that we&#39;ve not seen in a while.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/230/1*1MbdJADIsnc2RfoIGQNYxA.jpeg" /><figcaption>That’s why this time around, I support this guy for W3C TAG.</figcaption></figure><p>So what do you think public? If work for a member org, ask them to cast their vote for Andrew Betts— if not, speak up wherever you can.<em> Don&#39;t underestimate the collective power of developers sharing their support on Twitter, Facebook or G+ — your voice could help set in motion big changes, so whether you agree with me or disagree — let’s hear it: The future is what we make it.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c36769a73d51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Extensible Web Avengers, Assemble!]]></title>
            <link>https://medium.com/@briankardell/extensible-web-avengers-assemble-3eb7788c2144?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eb7788c2144</guid>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Tue, 23 Dec 2014 17:03:26 GMT</pubDate>
            <atom:updated>2014-12-24T17:58:54.300Z</atom:updated>
            <content:encoded><![CDATA[<p><em>In 2012, two things happened: First, a group of some of the world’s mightiest heroes came together on screen to save the world — The Avengers. Second, a group of some of the Web’s mightiest ran for the W3C Technical Architecture Group (TAG) on a slate to reform Web standards, explain Platform and save the Web. Coincidence? I think not…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yyY9jLB3EDNgccYwJ6aFUg.jpeg" /><figcaption>Marvel’s Avengers Assemble 2012 Logo in which lies a coded message about the Web…</figcaption></figure><p>If you&#39;re not familiar with it: In 2001, the W3C formed “The Technical Architecture Group” or TAG — a sort of steering committee elected by membership to oversee the larger architecture of the Web Platform. Initially, it played a visible and important role, but for a long time it was effectively “lost” and we entered a dark age, in which it became relatively uninteresting and unknown. Development of HTML broke off into the WHATWG and for a while, W3C efforts and the larger organization itself for seemed to be struggling with its own relevance. But then one day, a new hope arose…</p><blockquote>“And there came a day, a day unlike any other, when Earth’s mightiest heroes and heroines found themselves united against a common threat. On that day, the Avengers were born — to fight the foes no single superhero could withstand! Through the years, their roster has prospered, changing many times, their glory has never been denied! Heed the call, then — for now, the Avengers Assemble!” — prologue from 1970&#39;s era Marvel Avengers.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PigYtICeCoxUkgEzMu7ROA.jpeg" /><figcaption>This lovely TAG t-shirt is available from <a href="http://alvostore.com/collections/apparel">http://alvostore.com/collections/apparel</a></figcaption></figure><p>From their victory, a new TAG was born. A better TAG. And like the proverbial domino falling, this event has played a role in helping a lot more to happen too. The Extensible Web Manifesto, co-authored/co-signed by 4 of those newly elected Avengers…er…members, laid down a basic vision for change that has re-focused all of Web standards. The TAG began to reach out and work with ECMA TC-39 (the group in charge of standardizing the next version of JavaScript) and the IETF (the group in charge of standardizing HTTP2). They did reviews of drafts from numerous groups and helped re-focus designs on the underlying systems and commonalities. They helped organize meetups and the TAG <em>began talking to and listening to developers. </em>And other things fell in line too — the W3C Advisory Board began to take on a similar reform effort, reforms and the Extensible Web in particular were the talk of this year’s TPAC (annual W3C gathering).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*kIaILhKg8vFCNXx0MoIPZg.jpeg" /><figcaption>One battle — not easy.</figcaption></figure><p>But, like the Avengers coming together to face a seemingly never-ending array of ultra-bad guys, an effort to change something the scale of the Web isn&#39;t about a single battle, it’s a long war. It’s exhausting. Battles leave scars. And, believe it or not, superheroes want to have lives too. That’s why over the 60 or so years since Stan Lee and Marvel introduced the Avengers, the roster and even leadership has constantly shifted. Similarly, the membership of the W3C TAG changes with each new election, and once again, it’s time to choose next year’s members. We have a good heroes to choose from: There are six excellent candidates for 4 seats.</p><h3>Assemble 2015</h3><p>I&#39;d like to make the case for a particular lineup of heroes for what I think could be this year’s blockbuster smash…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2y44VymdokRinu8OMW5zIQ.jpeg" /><figcaption>Early concept art for W3C TAG Extensible Web Avengers Assemble 2015</figcaption></figure><ul><li><strong>Alex Russell</strong>. Let’s bring him back. He was an Extensible Web Avenger founding member pushed out by a rules technicality and unable to complete his term, and he&#39;ll be the only original left. Smart like Tony Stark, leadership qualities like Captain America, TC-39 Member who works on the Google Chrome team. I&#39;m not going to take this Avengers thing much further here, but in many ways, you can credit his ideas and tenacity as key ingredients us to getting this far.</li><li><strong>Mark Nottingham. </strong>Elected just a few months ago in a special mid-term election to fill Alex’s vacant seat, he’s proven a great asset already. He’s the chair of the HTTP WG in IETF, an excellent liaison, <em>super </em>smart, personable and he gets things done. Let’s re-elect him.</li><li><strong>Travis Leithead. </strong>Also ran for Alex’s vacated seat, but we had to make a really tough choice with two great candidates for one seat. <em>Now we can get all three!</em> Also a TC-39 Champion, works on the IE team. Travis has a great understanding of the platform and has been involved in a whole lot of the efforts that made it an increasingly competitive browser again and bring Microsoft back to the table. Travis could be a powerful add.</li><li><strong>Yan Zhu. </strong>Something the TAG and the Extensible Web sorely needs: Someone with a strong focus on security. From the security team at Yahoo and former EFF (Electronic Frontier Foundation) engineer, Yan’s background, open source work and positive working relationships make her a must-get for the team as we continue to refocus efforts toward uncovering the lower layers of the Web Platform.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*NyhF2u0vBV5xzBL9iXCzVA.jpeg" /><figcaption>Final poster — Assemble! I support these heroes!</figcaption></figure><p>You can read more of their own statements (and all candidates) at <a href="http://www.w3.org/2014/12/01-tag-nominations">http://www.w3.org/2014/12/01-tag-nominations</a>.</p><p>Combined with the members we have left on TAG like Dave Herman and special agents Dan Appelquist and Peter Linss, this could be a powerful force for good.</p><h3>I’m in! How do I vote?!</h3><p>Ok, now for what will seem like a punchline: Chances are, you don&#39;t actually even <em>get</em> a vote — only one AC member representative from each W3C member org actually gets to cast a formal vote. That’s a different problem, and one we&#39;re also working on…</p><p><strong><em>BUT</em></strong> — the past two years has shown us that normal people showing their support and asking members to vote with us has had good effect — every single election, it’s worked. So, if you support these heroes — tell someone! If you know someone who works for a member, email them! If not, just tweet it, blog about it, share it on facebook — believe it or not, people <em>are </em>listening and they know that ultimately the Web depends on people like us believing in it and rooting for a vision to succeed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*T7fQHIR8pgPu-jEjdAv7rw.jpeg" /><figcaption>That’s our secret cap — we’re always noisy.</figcaption></figure><p>In short, make a little noise and make sure you&#39;re heard — let’s do this #tag2015 #extendthewebforward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eb7788c2144" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Web Standards We Need: Part II — “Guilds” (CGs++)]]></title>
            <link>https://medium.com/@briankardell/the-web-standards-we-need-part-ii-guilds-cgs-1cd61b115751?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1cd61b115751</guid>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Thu, 04 Sep 2014 14:48:02 GMT</pubDate>
            <atom:updated>2014-09-04T15:31:41.669Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Web Standards We Need: Part II — “Guilds” (CGs++)</h3><p><em>This post is the second in a series discussing how we can help arrive at the Web Standards We Need. In the </em><a href="https://medium.com/p/web-standards-we-want-part-i-chapters-ca71985bf914"><em>first post </em></a><em>I examined why developers remain largely uninvolved in the standards process, even in ways that they could, technically be and how we might change that. In that post I introduced a new concept/pilot program we are setting up called “Chapters” which provides some ways to help tighten the feedback loop and provide more interest and education. In this post, I’d like to talk about how we take this a little further and help navigate the existing processes and bodies along the way.</em></p><p>For a while now, W3C reformers have been pushing the idea that developers need an actual voice in the W3C. The frequent counter points are that most work takes place in public (each group has a public mailing-list and IRC channel), that developers are free to participate and that W3C has many Invited Experts who participate in member only working group events, and that the W3C now allows the formation of Community Groups which provide a lot of opportunity and have shown some good success.</p><p>All of these counterpoints are true — so what’s left to discuss?</p><h4>What isn’t working with the status quo?</h4><p>The W3C itself is pretty much driven by membership. Ultimately, decisions about the goings on, the larger vision, how processes should work, what kind of licensing we need, etc of the body is derived through the pulse of AC (Advisory Committee) representation. Each member organization has one representative called an “AC Rep” with special powers: The ability to comment, discuss (and be taken seriously by default) and <em>actually vote</em> on matters, as well as the ability to name participants to working groups. Member orgs are also expected to donate participation, meeting and work time and travel expenses for anyone their AC nominates.</p><p>While the existing systems do have some good qualities that allow the most dedicated external technical contributors to do so without paying for membership, it is <em>very hard</em> to operate externally — and they do it all at their own cost. The Responsive Images Community Group is probably the poster-boy for external success, but it was <a href="http://arstechnica.com/information-technology/2014/09/how-a-new-html-element-will-make-the-web-faster/"><em>hard fought and long</em></a><em>. </em>The design of standards is such that it provides no effective way to help the organization (any of them really, but specifically I am talking about W3C here) get the pulse of developer interest, because there are is no equivalent representation in the AC — this further underscores the idea that these are “external” and creates a de-facto exclusionary posture which is alienating.</p><h4>So how can we fix these problems?</h4><p>One proposal intended to help was created by a W3C Task Force. It was called (unfortunately) “Webizen,” which would allow individuals a kind of limited membership for the bargain price of $100 per year. For the this, every N developers would be able to elect a kind of limited representative who could vote in elections, communicate with the ACs, but not actually appoint to Working Groups. The idea was to establish a kind of electoral college with an upper and lower house of representation.</p><p>Membership, who — again — speaks through the ACs, basically declined this proposal. They asked the task force to formulate a new one. Interestingly, AC comments are not really allowed to be made public, so really, only ACs, AB, CEO or Director can know exactly what was discussed— the best the task force can get is a rough third-party summary. This makes building a good proposal very hard.</p><h4>A Loophole?</h4><p>Actually, it’s not a loophole, it’s just how the process works: Today, any legal entity who pays the dues can join today regardless of whether that group is a giant multi-billion dollar venture like IBM, Apple, Google or Microsoft, or a tiny non-profit, or even a sole proprietorship with a single employee — and they all get the exact same rights and say.</p><p>In theory then, developers could form orgs — guilds or something — as legal entities and it would seem, problem mostly solved. They could elect a representative, amortize the cost of travel or even development across N members, accept donations or offer reasonable dues — just like a lot of members do — and I expect we’d see very good things.</p><h4>So why don’t we?</h4><p>Well… It turns out that setting up a legal entity is non-trivial: It costs money, it requires process, there are legal and monetary ramifications. If you think I’m making too much of it let me make the point a different way: At 20 years old, <strong><em>the W3C itself is still not a legal entity</em></strong>. Further, creating several according to similar models raises the question of whether they are affiliates which might harm their ability to individually join, etc.</p><p>It’s relatively easy for a business or organization who has created a legal entity for other purposes to use that as a badge to get in, but at the end of the day, this requirement is simply a tax preventing a looser collection developers from doing just that. That’s too bad too, because it could help the W3C (and the Web in general) in very practical ways.</p><h4>So here’s my proposal…</h4><ol><li>Get rid of the requirement to be a legal entity and provide a means to establish virtual orgs (CGs++) which are acceptable in the same way as any legal entity.</li></ol><p>That’s it. Then just treat them like anyone else.</p><p>You see, Community Groups <em>already </em>provide many necessary underlying raw materials that you’d need:</p><ul><li>Founding document</li><li>Concept of Membership</li><li>Affiliation disclosure</li><li>IP / Release agreements</li><li>Ability to collect votes and elect chairs</li><li>They even have a blog and wiki and IRC.</li></ul><p>Really the only thing lacking is a means to collect funds and utilize it which can get complicated with an ‘org’ — so my proposal here is simply that W3C allow membership for a specific guild/CG++ to come through channels like kickstarter without going through a middleman — this neatly sidesteps (I think) the difficulties incurred by an org itself directly collecting or holding money.</p><p>Because of this design, different org formulations can compete by simply altering their description or in the founding documents. This means it’s possible for a guild to state their intent to collect money to do things like fund an elected developer’s participation or travel, or to write tests or send feature pull requests. These would follow the same model — first choose what you want to do, then fund it directly. It’s easy to think of ways that scores of interested developers could collectively “unionize” (in an abstract sense — their collective bargaining power) and contribute as much or more than many current members — simultaneously getting rid of the exclusionary by default and lack of means to get a pulse from developers all in one swoop.</p><p>So that’s what I’d like to see, if you agree, contact your representative and ask them to…</p><p><em>oh… wait… You don’t have one</em>.</p><p>In lieu of that then, just share this post and say something positive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1cd61b115751" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Standards We Want: Part I — Chapters]]></title>
            <link>https://medium.com/@briankardell/web-standards-we-want-part-i-chapters-ca71985bf914?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca71985bf914</guid>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Wed, 03 Sep 2014 12:45:08 GMT</pubDate>
            <atom:updated>2014-09-03T12:45:08.782Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Web Standards We Need: Part I — Tightening the Feedback Loop (an experiment)</h3><p><em>The Web is 25 this year, and on this its silver anniversary, there is a new campaign called (The) </em><a href="https://webwewant.org/"><em>Web We Want</em></a><em> organizing efforts around 5 guiding principles all about keeping the Web a place for free expression, decentralized infrastructure, privacy, affordability and neutrality. It’s a good effort. I applaud it. But it’s all for naught if the Web can’t survive and thrive in the first place. The </em><a href="http://extensiblewebmanifesto.org/"><em>Extensible Web Manifesto</em></a><em> and articles about it lay out a new vision, but we need to carry through in practice. Specifically in my next two posts, I’d like to talk about one thing: </em><strong><em>Participation </em></strong><em>in standards — tightening the feedback loop and some new efforts to create the Web Standards We Need.</em></p><p>In reality, developer adoption is perhaps the most important element in a successful standard. It well outweighs technical purity or standards body approval. You need look no further than the specs we use compared with the ones we do not to see proof of this: Many failed standards are technically superior, but lost out for other reasons. Indeed, HTML itself is a less technically pure/capable offshoot of SGML and the more robust XML re-attempt also ultimately has largely lost out. Yet, many things we do use started out as low-end challengers to the standards.</p><p>There are many tens of thousands of Web developers, yet they remain largely uninvolved, despite the fact that there are ways in which they technically <em>could </em>be involved. Standards bodies have made few efforts to consider this problem. Even with recent improvements, when you look at how many people are actually involved in the creation of a standard, in many cases they would all fit in my (rather small) bathroom. Further, they tend to be the same small group of folks (measured in dozens) and, somewhat homogenous at that. Why?</p><h4>Understanding Barriers to Participation</h4><p>There are a number of reasons that this is the case — a lot of them are historical legacy.</p><p>First, because <em>most </em>developers who haven’t been around since nearly the beginning are unaware that such opportunities to contribute even exist. Since the main modes of participation are somewhat antiquated (mailing lists and IRC) and not exceptionally discoverable, this fact winds up just off the radar of the vast majority of developers.</p><p>Second, it’s a giant leap of faith to jump into the fray: These forums are public and full of the most knowledgeable (and opinionated and occasionally stubborn) people — that can be <em>very </em>intimidating. You might think you’ve got a pretty good grasp on science, but it’s very likely you don’t want to seem to publicly challenge Stephen Hawking with your pet idea about string theory. In some ways, that’s not entirely bad, it helps manage the noise level — I’m simply offering the observation that it is a deterrent that has probably helped to keep good ideas out.</p><p>If you can get past all that, you’ll see it can be <em>wildly </em>frustrating. If you’re unfamiliar, a recent <a href="http://arstechnica.com/information-technology/2014/09/how-a-new-html-element-will-make-the-web-faster/">article on the &lt;picture&gt; element</a> captures some of the challenges in recounting the trials and tribulations (but ultimate success) of the Responsive Images Community Group (RICG).</p><p>Finally, there have historically been numerous conceptual and business <em>disincentives </em>to developers, and companies who might otherwise allow them to contribute. Time is a huge one. Developers work on projects where weeks or months can be the time from start to finish, web standards operate on a comparatively glacial scale. Let’s imagine that you’re a manager at a company and a developer says “I’ve got a great idea for something and if it were standard it would lower costs to develop and maintain”. Isn’t it worth some time? Actually, no, in most cases — it’s not: Chances that you’ll get something spec’ed and implemented in time for your project are <em>literally zero</em>. Chances that it might be there for your next project are infinitesimally small as well. Next year maybe? Probably not, no, sorry.</p><p>It’s hard to be excited about things for years that may or may not someday deliver you some value.</p><p>And so it is that the majority of developers wait years for things that often fail to materialize at all, and frequently when they do and we are finally able to spend the time to learn and try them in a dizzying number of use-cases, we find them lacking or at best, underwhelming.</p><h4>Removing Barriers: Challenges</h4><p>There are several challenges to removing these barriers. <a href="http://extensiblewebmanifesto.org/">The Extensible Web Manifesto</a> lays out a few guiding principles that help: The aim of experimenting outside of browser implementations (prollyfills) means that it’s plausible that participation could actually yield you real value soon and allow you to provide feedback. But who is writing them? We need involvement. But what if suddenly even 1% of developers were involved in standards in the traditional fashion? We’d go from dozens of emails on a particular list in a day to thousands — and a whole lot of that would be noise. We need some concrete, new experiments toward fixing this problem.</p><h4>Experimentation</h4><p>To this end, several of us around the world have been consulting and we have something we’d like to try. We’re calling it “Chapters”.</p><p>Chapters aims to be a world-wide effort to establish local meetups and gather groups of interested parties for involvement in the standards process. The aim is to provide local outlets for developers of all grades of experience can come together to discuss developing standards in smaller groups according to their interests with the combined goals of education, larger participation and information gathering (tighten the feedback loop).</p><p>The general idea is that smaller, local groups choose and review a draft (potentially even submit one). They discuss — in person and digitally. The barrier to entry is low — new developers can be much less intimidated in a small, local setting where they aren’t the only non-wizard. Wizards, on the other hand can help mentor. <em>This alone would yield good and useful feedback which is currently late and lacking</em>: If after much help, the majority of people can’t understand something, standards bodies need that feedback. More importantly though, together they can look at prollyfills that simulate, attempt to use features before things get too far, attempt to make prollyfills where they don’t exist. Participants can write tests, discuss alternatives, etc.</p><p><strong><em>Very importantly</em></strong>, all of this feedback can be collected, distilled and fed back upward into the standards bodies by way of unified notes and a single champion in a manageable way that is productive and less disruptive than a thousand independent voices shouting, and even if a standard doesn’t arrive, both sides get some real value from the proposition.</p><p>I am currently putting together partnerships with local colleges, universities and meetups in my area for an early pilot and the University of Vermont has graciously donated a space. So, if you happen to be near Burlington, VT in the US on Monday, September 8th — I’d like to invite you to stop by UVM’s Perkins Hall between 6:30 and 9pm and help us see what we can do. Of course, we’ll adjust and tweak as we learn — it’s an experiment, after all. If you’re not in this area, but find the idea interesting — leave a comment, or feel free to contact me via Twitter @briankardell or email bkardell@gmail.com.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca71985bf914" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developers of Earth, ]]></title>
            <link>https://medium.com/@briankardell/developers-of-earth-750d6fee536c?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/750d6fee536c</guid>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Tue, 13 May 2014 20:15:21 GMT</pubDate>
            <atom:updated>2014-05-14T22:11:23.843Z</atom:updated>
            <content:encoded><![CDATA[<h4>Your attention please.</h4><p><em>(all quotes in this post are from the late Douglas Adams’ — mostly Hitchhiker’s Guide to the Galaxy — all conclusions and statements are my own).</em></p><blockquote>People of Earth your attention please…. regrettably, your planet is one of those scheduled for demolition… [panic…]</blockquote><blockquote><strong>There’s no point in acting surprised about it. </strong>All the planning charts and demolition orders have been on display at your local planning department in Alpha Centauri for 50 of your Earth years, so you’ve had plenty of time to lodge any formal complaint and it’s far too late to start making a fuss about it now. … What do you mean you’ve never been to Alpha Centauri? <strong>Oh, for heaven’s sake, mankind, it’s only four light years away, you know. I’m sorry, but if you can’t be bothered to take an interest in local affairs, that’s your own lookout.</strong></blockquote><p>The Web turns 25 this year, and the largest standards body/organization dedicated to it, the W3C, turns 20. When it was founded, the Web was new and the landscape of technology vastly different. There was so much excitement, those were heady days…</p><blockquote>“In those days spirits were brave, the stakes were high, men were real men, women were real women and small furry creatures from Alpha Centauri were real small furry creatures from Alpha Centauri.”</blockquote><p>But the Web needs to compete and remain relevant and vibrant and the truth is that we remain far from the state of the art. We’re not keeping pace and the standard process sometimes feels like it was created by Vogons. At 20, I think it’s a good time to stop -pause and reflect and perhaps learn some things about what is and isn’t working. Let’s see if we can re-align the trajectory where necessary before it’s too late.</p><h4>Cause and Effect…</h4><p>Development of a standard often takes many years and involves a lot of fits and starts of discussion along the way and many of them are bike shedding and speculation about what developers want, how they will interpret something, what might lead to unintended abuses by developers, etc. People sometimes wait until it’s very late in the process to comment and wind up rehashing fundamental questions. No matter how open a group is, the number of people actively involved in the creation of a standard would often still fit into a small room (the acknowledgement section of most drafts gives you a fairly good idea) and they tend to be the largely same groups of folks. Finally, when we do get a recommendation, even with implementations, on many occasions the result doesn’t get a very warm reception, and even when there is initial excitement, it often doesn’t last.</p><p>The W3C is not ignorant of these things, and it’s not that there isn’t genuine concern — there is always talk on how to improve things. So why is it not dramatically better?</p><blockquote>“This planet has — or rather had — a problem, which was this: most of the people living on it were unhappy for pretty much of the time. Many solutions were suggested for this problem, but most of these were largely concerned with the movement of small green pieces of paper, which was odd because on the whole it wasn’t the small green pieces of paper that were unhappy.”</blockquote><p>I think it’s easy to misinterpret — these things are not the cause of our problems, they are the effect of our problems. It’s not the standards process that’s unhappy.</p><p><strong>Developers: Mostly Harmless<br></strong>Despite lots of discussion or proposals, the W3C has historically failed to find ways to engage developers in important and meaningful ways. This is a terrible problem when you think about it.</p><p>Real “standards” and interoperability don’t exist because a standards body publishes them, or even because an implementer implements them. There are examples of both which none of us would really consider “standard”. No, standards exist because developers use them. We help make the argument that businesses benefit by unprecedented interoperability, a global audience, a large pool of skilled workers. etc… We use them because they allow us to complete meaningful things in an accomplishable way.</p><p>Until they don’t.</p><p>At the end of the day, we usually work for someone else and have requirements that need to be met. There are lots of reasons why developers don’t participate on lists so much, but this is one of them: Often it can’t help us <em>today. </em>It’s difficult to justify to your employer that they should pay you for hours a week for things that, hopefully, might come into existence several years in the future.</p><p>What’s more, the confluence of individuals involved (businesses, implementers, developers) seems to never select (in an evolutionary sense) the most technically or academically superior answer, yet historically, this has been ignored by segments of the membership and affects the larger direction. Prognostication at this level impossibly hard for a small group, especially when it leaves out or systematically tends to dampen perhaps the most important voice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/1*2HNJnyJ8CVH8Y3CaXWUFdQ.jpeg" /><figcaption>An actual product available from cafepress <a href="http://www.cafepress.com/+hitchhikers_dont_panic_organic_mens_t_iphone,484349320">http://www.cafepress.com/+hitchhikers_dont_panic_organic_mens_t_iphone,484349320</a> — the many devices with apps/different models are one of the latest competitors to the Open Web approach</figcaption></figure><h4>Don’t Panic</h4><p>Don’t panic, Act. There are group folks working together to address these issues. Step #1 is helping to place people into the right places where they can carry these voices and ideas to membership on our behalf. They can help us to change things for the better and fix the broken aspects of the model.</p><p>In the last year and a half we have helped to reach out to those members who are willing to listen and elect people to the two advisory groups within the W3C — TAG (the Technical Architecture Group) who works with the director to advise on the overall architecture and technical vision of the Web, and the AB (the Advisory Board) who works with the CEO to advise on matters of how the W3C works. Already we have seen numerous successes — The TAG matters to us, they’ve reached out to the community in a number of ways and made valuable comments and contributions. We have the <a href="http://extensiblewebmanifesto.org/">Extensible Web Manifesto</a> and a commitment by many members to support its ideals — and we even have W3c HTML spec editors <a href="https://github.com/ThePacielloGroup/w3c-heading/blob/gh-pages/README.md">proposing elements </a>from the ground up, in ways that developers can engage in more directly and in meaningful ways rather than years of contentious debate on a list — and arguments to <a href="https://github.com/dglazkov/html-as-custom-elements">explain the magic of all elements</a>. In the AB, we’ve seen a real effort to open things up and make them more public. Now, there is a proposal to allow individuals developers a limited membership — it’s still early and incomplete — but it’s a positive development.</p><p>Currently there is an AB election with 5 seats. The AB is an optimal spot to place folks who understand a developers’ perspective and the challenges faced by the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*QMlXLTmKzEsfsvsaPlBJeg.png" /></figure><p>Please — Act. It’s so easy to be involved. We need to let membership know that we support change and candidates like these:</p><p><a href="http://lea.verou.me/"><strong>Lea Verou</strong></a><br><a href="http://boazsender.com/about/"><strong>Boaz Sender</strong></a><br><a href="https://twitter.com/afbarstow"><strong>Arthur Barstow</strong></a><br><a href="http://poulpita.com/"><strong>Virginie Galindo</strong></a><br>David Singer</p><p><em>So, tweet, tell a friend, post a link on Facebook — make a meme… Spread the word! Anything that gets people to look and get involved is good! If you have time, write a post. If you know one, send a message to an AC rep. </em><strong><em>If you are one, lend us a voice for the greater good. </em></strong><em>Below is some more information on these candidates and why I support them…</em></p><p><strong>Lea </strong>is an <em>actual</em> developer and active in the community — you can find her at talks and conferences all the time. It should be obvious why think some real practitioner voice is important, but she also is an invited expert in the CSS WG and worked for W3C for a while in developer relations — so she has a very unique perspective having seen it from all sides and brings a direct connection to represent developers in the dialog.</p><p><strong>Boaz </strong>is also a developer and the flâneur at <a href="http://bocoup.com/">http://bocoup.com/</a> — a passionate advocate of the open web who has done quite a bit of outreach, hosting (<a href="https://www.youtube.com/user/BocoupLLC">recorded/live</a>) TC-39 and TAG events and whose employees are especially active in the community. He brings a drive and understanding of what it’s like for developers and non-megalithic companies to be involved and has a serious interest and skills with process. (Update: <a href="http://boazsender.com/2014-05-14-running-for-the-w3c-advisory-board.html">Boaz has since posted about why he is running</a>).</p><p><strong>Art </strong>is from Nokia — he has been working with standards for a long time, he’s been effective and involved and is outspoken and thoughtful on issues of process, involvement, licensing, etc. and has led efforts to streamline the ability to keep track of what is going on or how to get involved and open things up to developers.</p><p><strong>Virginie </strong>is from Gemalto and active in a number of groups (she chairs the security group) and I think <a href="http://poulpita.com/2014/04/28/running-for-w3c-advisory-board-again/">she can sum up why she is running and why you should vote for her </a>much better than I can. Suffice it to say for purposes here: She sees the problems discussed here (as well as others), brings a unique perspective and has been increasingly involved in efforts to figure out how to help give developers a voice.</p><p><strong>David</strong> is from Apple and he’s also been working on standards for a long time. He knows the process, the challenges and the history. I’ve not always agreed with him, but he has expressed a number of good things in relation to things mentioned above in his <a href="http://lists.w3.org/Archives/Public/www-archive/2013May/0033.html">candidate statement</a> which make me especially hopeful that he would be an excellent choice and a good voice to round things out.</p><blockquote>“Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so.” — From Douglas Adam’s “Last Chance to See”</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=750d6fee536c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Web]]></title>
            <link>https://medium.com/@briankardell/dear-web-343857bf55ff?source=rss-4b7e77c1355a------2</link>
            <guid isPermaLink="false">https://medium.com/p/343857bf55ff</guid>
            <dc:creator><![CDATA[•?((¯°·._.• вкαя∂εℓℓ]]></dc:creator>
            <pubDate>Thu, 26 Dec 2013 15:37:11 GMT</pubDate>
            <atom:updated>2013-12-26T15:37:11.698Z</atom:updated>
            <content:encoded><![CDATA[<h4>An open letter to W3C member representatives and Web developers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*3ququ31uhz-FbGOfYkhoHw.jpeg" /><figcaption>I am the Lorax, I speak for the developers. I speak for the developers because the developers have no tongues in this election.<br>(inspired by Dr. Seuss’ The Lorax)</figcaption></figure><p><em>You probably don’t know who I am, and that is ok. But I think you should listen to what I have to say. You need to, in fact, because I won’t go away.</em></p><p><em>I speak for the developer who works in the trenches — building the Web, not stuck on the benches.</em></p><p>Over time, we’ve collectively watched the W3C and, more generally, standards become increasingly dysfunctional. We’ve watched as problematic or half-way solutions that don’t address real use cases arrive — slowly only to fail to get implementation or adoption. We became disillusioned. Some even began calling for throwing things out and starting over — again.</p><p>Developers like myself have been pushing W3C standards for as long as there has been a W3C. We espouse the value of open standards to every potential client, manager, co-worker, director, vice president and patent attorney — even occasionally, to random people we meet who really don’t care. We use the products and tools that W3C member orgs make too. We are your best PR. We are the necessary lifeblood that keeps the Web ticking. Without us, there is no Web.</p><p>While there are some good organizations that help represent us, we have no formal voice in the W3C. The process for incorporating developer feedback and input has historically proven itself inadequate. Given this, I am writing on behalf of (and to) the vast army of everyday developers asking for help.</p><p>One year ago, we ran a slate of <em>different </em>candidates for the W3C Technical Architecture Group (TAG): Excellent developers from among our own ranks who offered up a plan and a rough vision to <em>reform. </em>Given TAG’s charter, these members are carry our collective voices across working groups which historically have lacked much direct developer participation. With the help of some member orgs voting on our behalf, these candidates won.</p><p>Then, earlier this year, partnered with a <em>diverse </em>group of developers involved with <em>multiple standards bodies</em>, these newly elected members helped to author <a href="http://extensiblewebmanifesto.org/">The Extensible Web Manifesto</a>. Further, they have helped promote these ideals in TAG itself, across working groups and in the developer community. I won’t make the case for the work here — I think it speaks for itself, but if you are unfamiliar, <a href="http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/">here is a lengthy piece from Smashing Magazine</a> and the manifesto itself contains numerous links. In the very least, I feel safe saying that I’m speaking many signers and social media sharers when I say that we’d like to see more of this progress: More developer involvement/engagement, more layering to explain the magic of high-level APIs, more prioritization, more cooperation and collaboration among groups and across standards bodies.</p><p><strong><em>So here it is in a nutshell….</em></strong></p><p><strong><em>If you’re a W3C member: </em>I’d like you to ask your AC to stand with us and cast a vote to elect two more of the original co-signers of the Extensible Web Manifesto to the W3C TAG — <em>excellent TAG nominees</em>: </strong><a href="https://twitter.com/littlecalculist"><strong>Dave Herman</strong></a><strong> (nominated by Mozilla) and </strong><a href="https://twitter.com/domenic"><strong>Domenic Denicola</strong></a><strong> (nominated by jQuery). </strong>We’d love to know that you’re standing with us in #tag2014- it’s good for you too. If, as an AC you don’t normally vote — <em>what are you waiting </em>for? Your vote carries every bit as much weight as those of the giant companies — exercise your powers on behalf of developers. If you have questions about <em>how — </em><a href="/service/mailto:ij@w3.org">Ian Jacobs</a> at W3C is always happy to help. You can always ask for help from <a href="http://twitter.com/w3ctag">@w3ctag</a> on Twitter, too.</p><p><strong><em>If you’re a developer:</em></strong> <strong>I’d like to ask you to share your support via social media if you haven’t already (again is ok too) so that member orgs — the ones who get to cast a vote on our behalf, know that we really care and want to #extendthewebforward.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*tV6PRRep1uv_yoPhvYH_ew.jpeg" /><figcaption>Unless someone like you cares a whole awful lot, nothing is going to get better. It’s not.<br>- Dr Seuss, The Lorax</figcaption></figure><p><em>When it’s all said and done, and there is no more-word — we’ll need all your help to #</em><a href="http://extensiblewebmanifesto.org/"><em>extendthewebforward</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=343857bf55ff" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>