<?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 Jono Bacon on Medium]]></title>
        <description><![CDATA[Stories by Jono Bacon on Medium]]></description>
        <link>https://medium.com/@jonobacon?source=rss-4f7cc7b66c1e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gyf5EmqtsOrBF_VSJQKz0w.jpeg</url>
            <title>Stories by Jono Bacon on Medium</title>
            <link>https://medium.com/@jonobacon?source=rss-4f7cc7b66c1e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 16:38:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonobacon/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Building Blocks of Better User Interfaces and Communities]]></title>
            <link>https://medium.com/@jonobacon/the-building-blocks-of-better-user-interfaces-and-communities-311f5de6147c?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/311f5de6147c</guid>
            <category><![CDATA[user-interface-design]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[lego]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Tue, 18 Dec 2018 13:35:09 GMT</pubDate>
            <atom:updated>2018-12-18T13:35:09.093Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.lego.com/">Lego</a> is an ingenious invention in that there is value in the individual blocks, but unlimited value in what you can build with them. Sure, you get the instructions with a new set to build the race car, but what really rocks is the <em>super jet-powered drone boat</em> that you come up with yourself. Oh, and that drone boat? Yep, it has lasers attached.</p><p>This notion of plugging bricks together is becoming more and more prevalent in technology. There are tools such as <a href="https://zapier.com/">Zapier</a>, which allow you to connect together different components to automate business workflow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0wIHrp7puIDajmmw.png" /></figure><p>There is Axe Edit, which is used to produce audio patches for the <a href="https://www.fractalaudio.com/iii/">Axe FX</a> line of guitar processors:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ODNP1h2-Eu6MpX3K.png" /></figure><p>We have even seen this model in action for teaching kids rudimentary methods of programming and logic, such as with <a href="https://scratch.mit.edu/">Scratch</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lSFkemFzvnjLaAaP.png" /></figure><p>Part of the reason this block-based model works is that building things is intrinsically <em>intuitive</em> to us. There is a reason why Lego has been so popular with kids for the last 69 years: we like to build things from a very early age.</p><p>There are also various <a href="https://thepsychologist.bps.org.uk/volume-25/edition-8/when-psychologists-become-builders">psychological benefits</a> with this kind of block-based collaboration, such as increased communication between builders of their intention and key concepts, generating social capital for active participation, increased speech and communication, and a focus on central problem solving and implementing and testing hypotheses. It is no surprise that Lego is increasingly used in team building and problem solving workshops.</p><p>This block-based approach clearly works. What I find interesting though is just how powerful of an approach this is not just for structuring collaborative tools, but also how you can build engagement and communities around it.</p><h3>Why This Works</h3><p>There are 4 key areas that I think are important to highlight here.</p><h3>#1. Connecting together blocks is simple and intuitive</h3><p>As mentioned above, clicking together blocks is a fundamentally intuitive approach to building things. We think about what we want to do, select a block, connect it to another block, and see if it works. We do this via trial and error and it builds a mental model of not just how the blocks work, but how combinations of blocks work.</p><p>For example, in Zapier, once I understand (1) what two blocks do (such as <em>Google Docs</em> and <em>Wordpress</em>), and (2) how to click them together, I can immediately generate value and improve my business. This results in a very low learning curve, and a very quick route to experiencing value (which is often not the case as products get more and more complex.)</p><p><a href="https://www.jonobacon.com/2018/12/18/lego-blocks-and-better-user-interfaces/"><strong>READ THE REST OF THIS POST HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=311f5de6147c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Value of Failure and Feedback: A Guide]]></title>
            <link>https://medium.com/@jonobacon/the-value-of-failure-and-feedback-a-guide-e04abd1c080b?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/e04abd1c080b</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Tue, 22 Aug 2017 15:52:06 GMT</pubDate>
            <atom:updated>2017-08-22T15:52:06.671Z</atom:updated>
            <content:encoded><![CDATA[<p>When people are huddled at a conference or professional event, the subject often turns to the value of <em>failure</em> and embracing <em>feedback</em>. “It is the key to self improvement!”, many chant, channeling their inner self-help gurus, Sadly, many don’t quite practice what they preach.</p><p>Seeing the value in critical feedback and the lessons that failure can offer is a tough pill to swallow. For those confident in their capabilities, their social standing (in their companies/communities etc), and their abilities, the pill goes down a little easier. For those who experience imposter syndrome, feel insecure about their work, or are new in their careers, it is more difficult.</p><p>Here’s the thing: these are not binary personalities. While some people are overly confident about themselves, and some people are overly insecure about themselves, most people have a blend of both. As such, even the most confident people can feel the sting when they get critical feedback or screw something up. This is a guide with some things I have learned over the years about how to turn feedback and failure to your advantage.</p><h3>The Ideal Blend</h3><p>In my not-so-humble opinion, the perfect blend of a human being is confidence in their ability to execute and accomplish their goals, but with a healthy dose of awareness of their current limitations. Let’s face it, overly confident people are often not just at risk of being swallowed up by ego, but can also lack the empathy to understand other folks they need to work with who don’t share the same confidence.</p><p>An understanding of our current limitations is healthy. When we understand we are not great at something, but we are eager to learn and improve, it opens us up to counsel and tuition. The confidence piece plays an important role in helping us to remember: “I might suck now, but I am going to learn and get better”. When we have this in our heads it makes the journey more palatable: we know that our failure to succeed right now is temporary and it <em>will</em> improve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yosJPyu61FB8is9G." /></figure><p>Pictured: me in a kitchen.</p><p>As an example, historically I was an awful cook. When I moved to the US I barely knew how to cook an egg. I was just never interested to learn. Then, I decided to learn to BBQ (after eating some mind-blowing brisket and deciding I <em>needed</em> to make that in my back yard). I started smoking brisket, then pork, and then ribs. Of course, it was all awful and my family suffered through painful bite after painful bite with a lego-like fixed grin on their faces to offer their (at times quite reasonably muted) encouragement.</p><p>When I started BBQing though I knew I was at the start of my journey. My previous experiences learning new things (e.g. community strategy, programming in Python, playing the guitar/drums) taught me that we all suck at first. While it was awful, and the failure of making terrible food at family gatherings stung, I knew this was just part of the journey. It would not suck forever, and that focus on the journey helped to seal my confidence to keep succeeding. Importantly, the failure shone a light on where I need to look to improve.</p><h3>Failure</h3><p>So, let’s first dig into failure.</p><p>When we think of “failing” we typically think of screwing something up. We didn’t deliver a great talk, we didn’t handle a conversation with a peer/boss/customer very well, we didn’t deliver a project on time, the thing we did deliver didn’t work, etc.</p><p>Like many things, failure has two pieces to it: a <em>logical</em> and <em>emotional</em> component.</p><p><a href="http://www.jonobacon.com/2017/08/21/value-failure-feedback-guide/"><strong>READ THE FULL ARTICLE HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e04abd1c080b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Work Smarter: The Cocktail of Simplicity, Manageable Adversity, and Muntzing]]></title>
            <link>https://medium.com/@jonobacon/work-smarter-the-cocktail-of-simplicity-manageable-adversity-and-muntzing-a204e914baeb?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/a204e914baeb</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Thu, 15 Jun 2017 15:04:49 GMT</pubDate>
            <atom:updated>2017-06-15T15:04:49.922Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/795/0*FbXOBCkLCucBuwi_." /></figure><p>Back in the 40s, TVs were giant, ugly behemoths. They were jammed with vacuum tubes, big bulky components, and were prone to overheating and failure.</p><p>Earl “madman” Muntz was an engineer and businessman who started repairing radios when he was 8 and built his first car radio when he was 14. As only someone with the nickname ‘<em>madman</em>‘ could do, when he worked in the TV business, he would walk around the factory floor, step in front of an unsuspecting engineer and yank components from TV sets until they stopped working. Then, he would put the last removed component back in and the set would often work, but with fewer components (thus cheaper) and often other benefits such as reduced heat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4QXMwfcmqN-YPNBq." /></figure><p>This practice became known as <em>muntzing</em>, which while it sounds like some awful way of hazing people with a hosepipe, it was actually a deliciously simple exercise in efficiency and cost reduction. Rather unsurprisingly, this provides an interesting lesson we can apply outside of knackered, old TVs from the forties.</p><h3>Simple but not Simpler</h3><p>Muntz’ was fundamentally zoning in on <em>simplicity as a way to accomplish efficiency</em>.</p><p>He wasn’t the first. Around the same time period, Einstein, a man not especially unfamiliar with genius, said:</p><blockquote><em>“Everything should be made as simple as possible, but not simpler.”</em></blockquote><p>Einstein touches on the elegance in simplicity and not to be fooled by thinking simple minds create simple things. We see this every day with seemingly simple devices (e.g. the iPhone) that carefully conceal enormous amounts of complexity behind the scenes, both in terms of technology and workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MB3KjwH7YS26_rao." /></figure><p>For the work I do in <a href="http://www.jonobacon.com/consulting/">building productive and engaging communities and organizations</a>, this is nirvana. My ultimate goal is to build human systems that deliver solid, productive, and predictable results but are simple in their instrumentation and use. As you can imagine, there is often a lot of complexity that goes into doing this.</p><p>So, Muntz and Einstein give us a good recipe: focus on simplicity as a means to accomplish efficiency, and reduce the complexity as a means to become lean. Sounds great in theory, but how do we do this?</p><h3>Harnessing Adversity to Build Efficiency</h3><p>There are various reasons why things become inefficient: people get lazy and take shortcuts, complexity slows things down, too many layers of abstraction contribute to this complexity, people accept the new reality of inefficiency and don’t challenge it…the list goes on.</p><p>We see this everywhere in the products we build, the organizational methodologies we have in companies and communities, the systems we have to use to file our taxes or invoices, and elsewhere. Not seen this? Go to the DMV in America. You will get it in droves.</p><p>An effective way to create efficiency and optimization is when we have <em>manageable adversity</em>. That is, we face tough situations that are within our control, capability, and power to resolve and learn from.</p><p>Muhammed Ali said it best:</p><blockquote><em>“I don’t count my situps, I only start counting when it starts hurting, when I feel pain, that’s when I start counting, cause that’s when it really counts.”</em></blockquote><p>Our most difficult moments in life, when we can feel beaten down, tired, and lost, can be the most formidable times of personal growth, evolution, and development. If we therefore instill the right level of adversity into our work, complete with having the ability to resolve it (which is the key difference between adversity being a helpful thing or a discriminatory force), we develop efficiencies.</p><h3>Putting This Into Practice</h3><p>As such, there can be enormous value in deliberately injecting adversity into our work as a forcing function to get better results. In other words, sometimes the easiest path forward is not the best path if we want to increase our capability and creativity. Sometimes throwing a few obstacles people need to navigate can be a useful thing.</p><p><a href="http://www.jonobacon.com/2017/06/14/work-smarter-cocktail-simplicity-manageable-adversity-muntzing/"><strong>READ THE REST OF ARTICLE HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a204e914baeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anonymous Open Source Projects]]></title>
            <link>https://medium.com/@jonobacon/anonymous-open-source-projects-f595bcf6af44?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f595bcf6af44</guid>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Mon, 01 May 2017 16:51:34 GMT</pubDate>
            <atom:updated>2017-05-01T16:51:34.281Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Iw4Uf3VC1_6gpx5x." /></figure><p><a href="https://www.linkedin.com/in/solomonhykes/">Solomon</a> asked an <a href="https://twitter.com/solomonstre/status/857338053794209794">interesting question on Twitter</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/0*tIc2D5nv3m5my6oF." /></figure><p>He made it clear he <a href="https://twitter.com/solomonstre/status/857395435043815424">is not advocating for this view</a>, just a thought experiment. I had, well, a few thoughts on this.</p><p>I tend to think of open source projects in three broad buckets.</p><p>Firstly, we have the overall <em>workflow</em> in which the community works together to build things. This is your code review processes, issue management, translations workflow, event strategy, governance, and other pieces.</p><p>Secondly, there are the individual <em>contributions</em>. This is how we assess what we want to build, what quality looks like, how we build modularity, and other elements.</p><p>Thirdly, there is <em>identity</em> which covers the identity of the project and the individuals who contribute to it. Solomon taps into this third component.</p><h3>Identity</h3><p>While the first two components, <em>workflow</em> and <em>contributions</em> are clearly important in defining what you want to work on and how you build it, <em>identity</em> is more subtle.</p><p>I think identity plays a few different roles at the individual level.</p><p>Firstly, it helps to build <em>reputation</em>. Open source communities are at a core level meritocracies: contributions are assessed on their value, and the overall value of the contributor is based on their merits. Now, yes, I know some of you will balk at whether open source communities are <em>actually</em> meritocracies. The thing is, too many people treat “meritocracy” as a framework or model: it isn’t. It is more of a philosophy…a star that we move towards.</p><p>It is impossible to build a meritocracy without some form of identity attached to the contribution. We need to have a mapping between each contribution and the same identity that delivered it: this helps that individual build their reputation as they deliver more and more contributions. This also helps them flow from being a new contributor, to a regular, and then to a leader.</p><p>This leads to my second point. Identity is also critical for <em>accountability</em>. Now, when I say accountability we tend to think of someone being responsible for their actions. Sure, this is the case, but accountability also plays an important and healthy role in people receiving peer feedback on their work.</p><h4><a href="http://www.jonobacon.com/2017/04/28/anonymous-open-source-projects/"><strong>Read the full article by clicking here.</strong></a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f595bcf6af44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Community Leadership Summit 2017: 6th — 7th May in Austin]]></title>
            <link>https://medium.com/@jonobacon/community-leadership-summit-2017-6th-7th-may-in-austin-fa5a2bf9c61d?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa5a2bf9c61d</guid>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Thu, 23 Mar 2017 16:48:56 GMT</pubDate>
            <atom:updated>2017-03-23T16:48:56.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2_-SzGxSi61reDw7." /></figure><p>The <a href="http://www.communityleadershipsummit.com/">Community Leadership Summit</a> is taking place on the <strong>6th — 7th May 2017</strong> in Austin, USA.</p><p>The event brings together community managers and leaders, projects, and initiatives to share and learn how we build strong, engaging, and productive communities. The event takes place the weekend before <a href="https://conferences.oreilly.com/oscon/oscon-tx">OSCON</a> in the same venue, the <em>Austin Contention Center</em>. It is entirely <strong>FREE</strong> to attend and welcomes everyone, whether you are a community veteran or just starting out your journey!</p><p>The event is broken into three key components.</p><p>Firstly, we have an awesome set of keynotes this year:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*Tfmz2vb6vI0xonSp." /></figure><p>Secondly, the bulk of the event is an unconference where the attendees volunteer session ideas and run them. Each session is a discussion where the topic is discussed, debated, and we reach final conclusions. This results in a hugely diverse range of sessions covering topics such as <strong>event management, outreach, social media, governance, collaboration, diversity, building contributor programs</strong>, and more. These discussions are incredible for exploring and learning new ideas, meeting interesting people, building a network, and developing friendships.</p><p>Finally, we have social events on both evenings where you can meet and network with other attendees. Food and drinks are provided by <a href="https://data.world/">data.world</a> and <a href="https://about.mattermost.com/">Mattermost</a>. Thanks to both for their awesome support!</p><h3>Join Us</h3><p>The Community Leadership Summit is entirely <strong>FREE</strong> to attend. If you would like to join, we would appreciate if you could <a href="http://www.communityleadershipsummit.com/register/">register</a> (this helps us with expected numbers). I look forward to seeing you there in Austin on the 6th — 7th May 2017!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa5a2bf9c61d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Better Teams With Asynchronous Workflow]]></title>
            <link>https://medium.com/@jonobacon/building-better-teams-with-asynchronous-workflow-684d3760c166?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/684d3760c166</guid>
            <category><![CDATA[innersource]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[developer-relations]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Mon, 19 Dec 2016 21:41:44 GMT</pubDate>
            <atom:updated>2016-12-19T21:41:44.539Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cRMhrL_WnF4Wc6ZsCalYag.png" /></figure><p>One of the core principles of open source and innersource communities is <em>asynchronous workflow</em>. That is, participants/employees should be able to collaborate together with ubiquitous <em>access</em>, from <em>anywhere</em>, at <em>any time</em>.</p><p>As a practical example, at a previous company I worked at, pretty much everything lived in GitHub. Not just the code for the various products, but also material and discussions from the legal, sales, HR, business development, and other teams.</p><p>This offered a number of benefits for both employees and the company:</p><ul><li><strong>History</strong> — all projects, discussions, and collaboration was recorded. This provided a wealth of material for understanding prior decisions, work, and relationships.</li><li><strong>Transparency</strong> — transparency is something most employees welcome and this was the case here where all employees felt a sense of connection to work across the company.</li><li><strong>Communication</strong> — with everyone using the same platform it meant that it was easier for people to communicate clearly and consistently and to see the full scope of a discussion/project when pulled in.</li><li><strong>Accountability</strong> — sunlight is the best disinfectant and having all projects, discussions, and work items/commitments, available in the platform ensured people were accountable in both their work and commitments.</li><li><strong>Collaboration</strong> — this platform made it easier for people to not just collaborate (e.g. issues and pull requests) but also to bring in other employees by referencing their username (e.g. @jonobacon).</li><li><strong>Reduced Silos</strong> — the above factors reduced the silos in the company and resulted in wider cross-team collaboration.</li><li><strong>Untethered Working</strong> — because everything was online and not buried in private meetings and notes, this meant employees could be productive at home, on the road, or outside of office hours (often when riddled with jetlag at 3am!)</li><li><strong>Internationally Minded</strong> — this also made it easier to work with an international audience, crossing different timezones and geographical regions.</li></ul><p>While asynchronous workflow is not perfect, it offers clear benefits for a company and is a core component for integrating open source methodology and workflows (also known as innersource) into an organization.</p><p>Asynchronous workflow is a common area in which <a href="http://www.jonobacon.org/consulting">I work with companies</a>. As such, I thought I would write up some lessons learned that may be helpful for you folks.</p><p><a href="http://www.jonobacon.org/2016/12/19/asynchronous-workflow/"><strong>READ THE FULL ARTICLE HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=684d3760c166" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft and Open Source: A New Era?]]></title>
            <link>https://medium.com/@jonobacon/microsoft-and-open-source-a-new-era-ba80dcb448d7?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba80dcb448d7</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Wed, 23 Nov 2016 18:12:37 GMT</pubDate>
            <atom:updated>2016-11-23T18:12:37.773Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*jo2I_g2yonsYmTnWdwjOhA.png" /><figcaption>Satya Nadella, seemingly doing a puppet show, without the puppet.</figcaption></figure><p>Last week the <a href="https://www.linuxfoundation.org/">Linux Foundation</a> announced Microsoft <a href="https://www.linuxfoundation.org/announcements/microsoft-fortifies-commitment-to-open-source-becomes-linux-foundation-platinum">becoming a Platinum member</a>.</p><p>In the eyes of some, hell finally froze over. For many though, myself included, this was not an entirely surprising move. Microsoft are becoming an increasingly active member of the open source community, and they deserve credit for this continual stream of improvements.</p><p>When I first discovered open source in 1998, the big M were painted as a bit of a villain. This accusation was largely fair. The company went to great lengths to discredit open source, including <a href="http://www.theregister.co.uk/2001/06/02/ballmer_linux_is_a_cancer/">comparing Linux to a cancer</a>, <a href="http://en.swpat.org/wiki/Microsoft_FAT_patents">patent litigation</a>, and <a href="https://www.cnet.com/news/facts-behind-microsofts-anti-linux-campaign/">campaigns formed of misinformation and FUD</a>. This rightly left a rather sour taste in the mouths of open source supporters.</p><p>The remnants of that sour taste are <em>still</em> strong in some. These folks will likely never trust the Redmond mammoth, their decisions, or their intent. While I am not condoning these prior actions from the company, I would argue that the steady stream of forward progress means that…and I know this will be a tough pill to swallow for some of you…means that it is time to forgive and forget.</p><h3>Forward Progress</h3><p>This forward progress is impressive. They <a href="http://www.zdnet.com/article/microsoft-loves-freebsd-so-much-it-has-made-its-own-vm-image-for-azure/">released their version of FreeBSD for Azure</a>. They <a href="http://www.zdnet.com/article/microsoft-and-canonical-partner-to-bring-ubuntu-to-windows-10/">partnered with Canonical</a> to bring Ubuntu user-space to Windows (as well as supporting Debian on Azure and even building their own Linux distribution, the <a href="https://azure.microsoft.com/en-us/blog/microsoft-showcases-the-azure-cloud-switch-acs/">Azure Cloud Switch</a>). They <a href="http://tirania.org/blog/archive/2014/Nov-12.html">supported an open source version of .NET</a>, known as Mono, later <a href="https://blogs.microsoft.com/blog/2016/02/24/microsoft-to-acquire-xamarin-and-empower-more-developers-to-build-apps-on-any-device/">buying Xamarin</a> who led this development and open sourced those components. They <a href="http://www.hanselman.com/blog/PublishingAnASPNETCoreWebsiteToACheapLinuxVMHost.aspx">brought .NET core to Linux</a>, <a href="http://www.zdnet.com/article/not-a-typo-microsoft-is-offering-a-linux-certification/">started their own Linux certification</a>, released a litany of projects (including <a href="https://github.com/Microsoft/vscode">Visual Studio Code</a>) as open source, <a href="https://msopentech.com/about/">founded the Microsoft Open Technologies</a> group, and then later <a href="https://msopentech.com/blog/2015/04/17/nextchapter/">merged the group</a> into the wider organization as openness was a core part of the company.</p><p><a href="http://www.jonobacon.org/2016/11/23/microsoft-open-source-new-era/"><strong>READ THE FULL ARTICLE HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba80dcb448d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Risks of Over-Rewarding Communities]]></title>
            <link>https://medium.com/@jonobacon/the-risks-of-over-rewarding-communities-3a40204f36f8?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a40204f36f8</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Tue, 26 Jul 2016 16:37:23 GMT</pubDate>
            <atom:updated>2016-07-26T16:37:23.927Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Incentive</em> plays an important role in communities. We see it everywhere: community members are rewarded with extrinsic rewards such as t-shirts, stickers, gadgets, or other material, or intrinsic rewards such as increased responsibilities, kudos, reputation, or other benefits.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*j8MiVpd7aLZj7_I7." /></figure><p>The logic seems seems sound: if someone is the bees knees and doing a great job, they deserve to be rewarded. People like rewards, and rewards make people want to stick around and contribute more. What’s not to love?</p><p>There is though some interesting evidence to suggest that <em>over-rewarding</em> your communities, either internal to an organization or external, has some potent risks. Let’s explore the evidence and then see how we can harness it.</p><p><a href="http://www.jonobacon.org/2016/07/26/the-risks-of-over-rewarding-communities/"><strong>Read the full piece here</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a40204f36f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Safer Internet with HackerOne]]></title>
            <link>https://medium.com/@jonobacon/building-a-safer-internet-with-hackerone-f59a3f7a8f21?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f59a3f7a8f21</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Fri, 08 Jul 2016 17:55:09 GMT</pubDate>
            <atom:updated>2016-07-08T17:55:09.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/668/1*BmEjY61xyOFLmt3aQfHjmg.png" /></figure><p>Recently I started doing some work with <a href="http://www.hackerone.com/">HackerOne</a> and I thought many of you would find it interesting enough for me to share.</p><p>A while back my friend Mårten Mickos joined HackerOne as CEO. Around that time we had lunch and he shared with me more about the company. Mårten has an impressive track record, and I could see why he was so passionate about his new gig.</p><p>The idea is pretty neat: HackerOne provides a service where companies (e.g. <a href="https://hackerone.com/uber">Uber</a>, <a href="https://hackerone.com/slack">Slack</a>, <a href="https://hackerone.com/gm">General Motors</a>, etc, and even <a href="https://hackerone.com/blog/pentagon-hackerone">The Pentagon</a>) can provide a bug bounty program that invites hackers to find security flaws in their products and services. The company specifies the scope of the program (e.g. which properties/apps), and hackers are encouraged to find and submit vulnerability reports. When a report is approved, the hacker is often issued a payment.</p><p><a href="http://www.jonobacon.org/2016/07/08/building-a-safer-internet-with-hackerone/"><strong>Read my full article here on jonobacon.org</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f59a3f7a8f21" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kindness and Community]]></title>
            <link>https://medium.com/@jonobacon/kindness-and-community-ecdb5a5f4628?source=rss-4f7cc7b66c1e------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecdb5a5f4628</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jono Bacon]]></dc:creator>
            <pubDate>Wed, 18 May 2016 19:58:16 GMT</pubDate>
            <atom:updated>2016-05-18T19:58:16.161Z</atom:updated>
            <content:encoded><![CDATA[<p>This has been a pretty busy week. Last weekend was the <a href="http://www.communityleadershipsummit.com/">Community Leadership Summit</a>, followed by OSCON. Sadly, I had to cut my OSCON trip short due to our son Jack developing strep throat.</p><p>What resulted though were some interesting insights into the relationship between kindness and how we can tap these fundamental human instincts to build great communities.</p><p><a href="http://www.jonobacon.org/2016/05/18/kindness-and-community/"><strong>Read my full post here</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecdb5a5f4628" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>