<?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 Kara de la Marck on Medium]]></title>
        <description><![CDATA[Stories by Kara de la Marck on Medium]]></description>
        <link>https://medium.com/@karadelamarck?source=rss-8d5575680261------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cVjCqz_mBnYnAgeTixSMPg.jpeg</url>
            <title>Stories by Kara de la Marck on Medium</title>
            <link>https://medium.com/@karadelamarck?source=rss-8d5575680261------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 17:10:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karadelamarck/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[EuroPython 2019]]></title>
            <link>https://medium.com/@karadelamarck/europython-2019-249b82fa9405?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/249b82fa9405</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[nlp]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Fri, 30 Dec 2022 16:45:38 GMT</pubDate>
            <atom:updated>2024-05-14T03:29:11.437Z</atom:updated>
            <content:encoded><![CDATA[<p>[Originally published internally at work in July, 2019.]</p><p>Last week, <a href="https://ep2019.europython.eu/conference/talks/9kMWoUi-step-into-the-ai-era-chatbots-that-know-if-you-are-angry.html">I ran a workshop at EuroPython</a> with Cheuk Ting Ho on building a Natural Language Processing (NLP) powered chatbot. I have mentored before at <a href="https://codebar.io/">codebar</a> and <a href="https://codeyourfuture.io/">Code Your Future</a>; however, this was my first workshop delivered at a conference. It was also my first EuroPython. Both of these turned out to be wonderful experiences.</p><p>Here are some photos of Cheuk and I helping attendees during our workshop:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ip36efIuYruE2qaScbX_Bw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcFDZAGoHg32umxwjVNQvw.png" /></figure><h3>🤖 NLP powered chatbot workshop 🎉</h3><p>Through hands-on coding exercises, workshop participants learned how to build a chatbot with <a href="https://rasa.com/docs/">Rasa</a>, an open source machine learning framework for automated conversations. Rasa uses NLP to understand messages and hold conversations with users. The goal of the workshop was to build a small chatbot demonstrating the role of machine learning (ML) in assessing the sentiment of a user’s input and in generating the chatbot’s response.</p><p>Rasa has two main components, both of which rely on machine learning and the workshop was structured so that participants would be able to see how they connect and work together to form a responsive chatbot. The first main component of Rasa consists of natural language understanding (NLU), a subset of NLP. Rasa’s NLU extracts information from the user’s message to predict the meaning of a user’s message. For our workshop, we used a pre-trained <a href="https://spacy.io/">spaCy</a> model in our NLU pipeline. We fine-tuned our spaCy model on example data to create NLU capabilities that were appropriate for the chatbot we were building.</p><p>The second main component of Rasa is its dialogue engine, or Core. Rasa Core uses a machine learning model trained on example conversations to decide how to respond to a user. This enables more complexity in the conversation. We wrote our own example conversations for the chatbot, including custom actions for capturing specific user data.</p><p>In the third part of the workshop we used <a href="https://www.nltk.org/">Natural Language Toolkit</a> (NLTK), a suite of libraries for natural language processing, to analyze the sentiment of a user’s feedback to an event — such as EuroPython! — to determine if it was positive or negative and we displayed the results in a rudimentary dashboard using the lightweight web framework <a href="https://docs.cherrypy.dev/en/latest/">CherryPy</a>.</p><h3>Additional notes on the conference</h3><h4>🐍 First EuroPython! 🇪🇺</h4><p>EuroPython was fantastic! As its name implies it was a highly technical Python conference, including a PyData track with loads of talks on machine learning and artificial intelligence. For the purpose of this summary, I will focus on my impressions of how the Python community is grappling with CI/CD for cloud native applications and also community initiatives at the conference.</p><h4>Continuous Integration / Continuous Delivery (CI/CD) at EuroPython</h4><p>A number of talks entirely or partially focused on how enterprises were wiring up their CI/CD process. It was clear that people are using a number of different tools to put together their CI/CD process and that there is still a lot of hard work being done to discover and glue together these processes. Each enterprise seemed to be inventing and reinventing the wheel: best practices are not standardized and many people are doing a lot of discovery and fine tuning. Overall, in these Python centric talks, there was much sharing of own best practices for CI/CD and a ton of interest from the audience as demonstrated by high attendance and many audience questions.</p><p><a href="https://cd.foundation/">The Continuous Delivery Foundation</a> (CDF) has a fantastic role to play in creating an open space for people to share best practices and helping to condense best practices into a set of recommendations. This sharing of best practices happened at EuroPython for the Python community, but in an informal way. People are left reinventing the wheel on how to do CI/CD in an enterprise grade, production grade way. And they are not comfortable doing this on their own: they are actively looking at what others are doing, comparing notes, and looking for best practices.</p><h4>Community at EuroPython</h4><p>EuroPython is a conference governed by the community for the community. My first glimpse of the inclusive and rollicking EuroPython community was on the main, incredibly busy communication channel for the conference. Of course, people had side channels, but a lot of information was shared in the main channel, including many types of social events outside of the conference. Due to the endless sharing of plans and social events in and around the conference, the week felt like one big rolling, friendly gathering.</p><p>More formally, there were lots of planned ways for the community to contribute towards the conference and share what they were working on or passionate about. There was an open track, poster sessions, and lightning talks. These sessions were motivated by the realization that no matter how good the speakers or selection committee for a conference, no format will be perfect. Open spaces and lightning talks let attendees choose the subjects that matter most to them. Attendees are given space and invited to share with each other: their passions, their concerns, their experiences. These openings in a conference format are a fantastic way to give trust and space to the community and let people step forward to share.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=249b82fa9405" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Foundation Open Source Summit ]]></title>
            <link>https://medium.com/@karadelamarck/linux-foundation-open-source-summit-502be9346194?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/502be9346194</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Thu, 08 Nov 2018 12:03:07 GMT</pubDate>
            <atom:updated>2018-11-08T13:49:11.773Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Celebrating Open Source Software and Communities</em></p><p>The <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/">Linux Foundation Open Source Summit</a> is an enormous conference focused entirely on open source software and the communities that create OSS. There are many <a href="https://events.linuxfoundation.org/events/open-source-summit-europe-2018/program/schedule/">tracks</a> in the conference, including Linux Systems, Infrastructure and Automation, Kubernetes/Containers/Cloud Native Apps, etc. In addition, there are thematic ‘conference’ tracks on community, collaboration, and diversity running throughout the three to five day event. And associated conferences are run in conjunction with the Open Source Summit such as the Embedded Linux Conference and the Open IoT Summit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*VcKHrmSSxs9BY-a2opMiuA.jpeg" /><figcaption><a href="https://twitter.com/jzemlin">Jim Zemlin</a>, Executive Director, <a href="https://www.linuxfoundation.org/">The Linux Foundation</a>, <a href="https://www.youtube.com/watch?v=f4dlFMxmYgo&amp;list=PLbzoR-pLrL6qThA7SAbhVfuMbjZsJX1CY&amp;index=1">Welcome Keynote</a> <em>(Image: official OSS photographer)</em></figcaption></figure><p>With thousands of attendees, the conference might seem overwhelming, but the track structure, workshops, and welcome programs help attendees get the most out of the wealth of knowledge and opportunities that the conference presents. Many of the excellent <a href="https://www.youtube.com/watch?v=f4dlFMxmYgo&amp;list=PLbzoR-pLrL6qThA7SAbhVfuMbjZsJX1CY&amp;index=1">keynotes and talks</a> were filmed. I am still talking to people about <a href="https://www.youtube.com/watch?v=0cZBbkn9M2M&amp;list=PLbzoR-pLrL6qThA7SAbhVfuMbjZsJX1CY&amp;index=8">Eric Berlow’s keynote</a> on ‘The Future of AI is Data’ and <a href="https://www.youtube.com/watch?v=wGF6zAlE1hs&amp;index=9&amp;list=PLbzoR-pLrL6qThA7SAbhVfuMbjZsJX1CY">Patrick Ball’s keynote</a> on ‘Digital Echoes: Understanding Mass Violence with Data and Statistics’.</p><p>A conference is structured by the talks, keynotes, and workshops, but even more memorable are the people you meet. This is especially true in open source as most communities are made up of individuals from all over the world and projects generally have distributed teams: open source conferences are a perfect opportunity to be in the same location and to meet people with whom you have collaborated on projects. I had a wonderful time speaking with <a href="https://twitter.com/jpkrohling">Juraci Paixão Kröhling</a>, who was a very impressive <a href="https://www.outreachy.org/">Outreachy</a> mentor for <a href="https://www.jaegertracing.io/">Jaeger</a> tracing, and was fortunate to attend <a href="https://schd.ws/hosted_files/osseu18/c7/ossummit-eu-2018-what-are-my-microservices-doing.pdf">his talk</a> on Jaeger and distributed tracing.</p><p>I learned about the Outreachy programme last year at the Linux Foundation Open Source Summit in Prague and immediately applied to work on the Node client for Jaeger. A write up of last year’s OSSummit can be read <a href="https://railsgirlssummerofcode.org/blog/2017-11-20-karadelamarck-linux-foundation-ossummit-europe">here</a>. <a href="https://twitter.com/ines_opcoelho">Inês Coelho</a>, my mentor on <a href="https://railsgirlssummerofcode.org/">Rails Girls Summer of Code</a>, also attended the OSSummit and spending time with her and other RGSoC alumni and mentors made my first experience at an OSSummit so welcoming and enjoyable. Happily, this year I met <a href="https://twitter.com/alicetragedy">Laura Gaetano</a>, who does incredible work organising RGSoC and with the <a href="https://twitter.com/travis_fnd">Travis Foundation</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ufn9LwPA_fIDIUxksI8aZw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LbrNL3j7F7KqoabkfSfE_g.jpeg" /><figcaption>Kara de la Marck and <a href="https://twitter.com/alicetragedy">Laura Gaetano</a>; <a href="https://twitter.com/ines_opcoelho"><em>Inês Coelho</em></a><em>, </em><a href="https://twitter.com/kernel_girl"><em>Vaishali Thakkar</em></a><em>, and Kara de la Marck (at last year’s LF OSS)</em></figcaption></figure><p>If you are a member of an underrepresented group in tech and would like to find out more about applying to <a href="https://www.outreachy.org/apply/">Outreachy</a> or <a href="https://railsgirlssummerofcode.org/students/application/">Rails Girls Summer of Code</a>, please DM me on Twitter <a href="https://twitter.com/karamarck">@KaraMarck</a>; both programmes are amazing and highly recommended! If you are wondering how and why such programmes are necessary and beneficial to the open source ecosystem, then you can read this Wired article on <a href="https://www.wired.com/2017/06/diversity-open-source-even-worse-tech-overall/">diversity in open source</a> or some of the insights from GitHub’s <a href="http://opensourcesurvey.org/2017/#insights">open source survey</a>. If you are a member of an underrepresented group in tech, and those resources make you wary of engaging with open source, know that your contributions to projects are valuable and that your presence is welcome. I’ve had a wonderful time contributing to open source and met generous, kind, and fascinating people from all over the world.</p><p>At this year’s OSSummit, I mainly attended talks or workshops that fell into three buckets: 1) AI and data, 2) distributed systems, tracing, containers, and Kubernetes, 3) how to build, support, and maintain open source communities. I left the conference with new insights, tools to look into, and opinions changed.</p><p>One thing that really stood out to me was that no one spoke about the GPL; MIT and Apache together seem to have moved from being open source licensing options, to a default choice, to the standard way to license open source projects now. <a href="https://twitter.com/sogrady">Stephen O’Grady</a>, at <a href="https://redmonk.com/">Red Monk</a>, wrote an excellent article on ‘<a href="https://redmonk.com/sogrady/2017/01/13/the-state-of-open-source-licensing/">The State of Open Source Licensing</a>’. In the year and a half since he wrote his article, the trend towards more permissive licenses seems to have only grown stronger. This shift is interesting and it changes what we mean and understand when we speak about open source software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*AbUQ5YP_fdN1OEYigCGmaA.png" /><figcaption>Image Credit: <a href="https://twitter.com/sogrady">Stephen O’Grady</a>, <a href="https://redmonk.com/">Red Monk</a></figcaption></figure><p>On the fifth day of the OSSummit, I attended a hackathon where the challenge was to ‘connect up’ the reel boards running <a href="https://docs.zephyrproject.org/latest/introduction/introducing_zephyr.html">Zephyr</a> that <a href="https://phytec.com/products/single-board-computers/">Phytec</a> had provided to all the hackathon attendees. I managed to get lights to blink, rename my board, switch to Bluetooth Mesh mode, and send texts to other boards over the wireless mesh network. It was a very enjoyable introduction to embedded programming and a great way to end this year’s Linux Foundation Open Source Summit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n4wczOTYxIbD7xKHJbjmRw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VRTXtqjKm02oJovCyzVHfw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=502be9346194" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[uncodebar 4]]></title>
            <link>https://medium.com/the-codelog/uncodebar-4-fb12fc542069?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb12fc542069</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[unconference]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 13:09:56 GMT</pubDate>
            <atom:updated>2019-01-07T13:04:28.791Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Sharing knowledge and celebrating community</em></p><p>Globally, <a href="https://codebar.io/">codebar</a> runs over 150 programming workshops a year and this is only possible through the dedication of our coaches, organisers, and students. Our annual unconference, uncodebar, is an all day open space event where we have the opportunity to come together to learn from each other through workshops and discussions and to celebrate our community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CivScyffNsRhRiR5gEqT_g.jpeg" /><figcaption>Celebrating an excellent uncodebar</figcaption></figure><p>In the five years since codebar was founded, our community has grown rapidly and it was wonderful to see individuals from other UK chapters come to London for uncodebar. As such, this year felt like an impromptu reunion as well as a fantastic day of knowledge sharing. We were fortunate to have our large crowd of attendees well supported by our sponsors, <a href="https://www.quantumblack.com/">QuantumBlack</a>, <a href="https://onerubything.com/">One Ruby Thing</a>, and <a href="http://www.samsung.com/global/galaxy/apps/samsung-internet/">Samsung Internet</a>. Thanks to these sponsors not only did we raise funds for codebar, in addition, for the first time ever, we were able help 6 people from outside London attend uncodebar. We would also like to thank <a href="https://twitter.com/TwitterUK">TwitterUK</a>, who for the second year running were wonderful hosts!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YWlKDWT6kGVcsrcfunlsRw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4NTZ8IRy90gHixyp7jDnUQ.jpeg" /><figcaption><a href="https://twitter.com/funmmi">Funmi Adewodu</a> welcoming us and thanking our uncodebar sponsors! Images by <a href="https://twitter.com/frathgeber">Florian Rathgeber</a> and <a href="https://twitter.com/KaraMarck">Kara de la Marck</a></figcaption></figure><p>Unconferences are a format that suit the codebar community very well since our workshops are marked by a spirit of generosity, openness, and sharing and are created at each instance through the interests, skills, and curiosity of both coaches and students.</p><h4>What is an unconference?</h4><p>As an open space event, the schedule of an unconference is created from the sessions participants propose to run. Session pitching is done in the morning, after breakfast and coffee, and a schedule of the unconference is created. Happily, our awesome community proposed many great sessions, including on topics as diverse as: data science, coding diaries, ethics, running tech communities, assembly, git, baking bread, kotlin, python, SRE, Arduino, designing for users, microbit, coaching, APIs, startups, and more!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cRHGjNrEsPL-HgXxAl_pA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMivjtOpKtm-7iecCKLNiA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2yu5gapaXy11G2Dqu0z1Ng.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwlTDpNa-LQOgkc9h2Ng_w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K_Zz2d3SCnwXp1l8UByt3g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gr1-BtVEyTTAW86kjmKrrQ.jpeg" /><figcaption>Images by <a href="https://twitter.com/frathgeber">Florian Rathgeber</a></figcaption></figure><h3>Claire Inez Mitchell 👩🏻‍💻 on Twitter</h3><p>Omg we&#39;re about to play a game all together. And not just any game, this is EXAPUNKS, which is apparently based on the film &quot;Hackers&quot; 👩‍💻👨‍💻</p><p>Unconferences are meant to facilitate the sharing of insights and expertise. They are a great way for beginners to learn from those who have more experience and for all participants to solidify their knowledge through discussions and feedback. Sessions don’t need to be limited to purely technical topics, participants share their favorite hobbies, tips on avoiding burnout, and life hacks.</p><p>Unconferences arose from the realisation that conversations had during the ‘hallway track’ are often the most memorable part of a conference, with the most lasting personal impact. I had a wonderful time catching up with <a href="https://foundersandcoders.com/">Founders and Coders</a> alumni and continuing an ongoing discussion with <a href="https://twitter.com/gcapizzi">Giuseppe Capizzi</a> on design patterns.</p><p>One hallway conversation that has had a reverberating impact was with Benita Rajania (who works on the <a href="http://t.sidekickopen24.com/s1t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5X-FfhMynN4XrjtMdF2RzW56dxsc8J-W9P102?t=https%3A%2F%2Fmakers.tech%2Ffellowship%2F&amp;si=7000000001136063&amp;pi=f3c90a0b-a05d-4e09-d10f-808685cd8618">fellowship programme</a> at Makers) after her <a href="https://blog.makersacademy.com/why-stories-matter-for-creating-safe-inclusive-spaces-56d316246389">moving talk on the importance of language and stories in creating safe, inclusive spaces</a>.¹ We spoke about how the language you use in response to either experiencing or witnessing a microaggression has a strong influence on the subsequent impact of that event. Most of us have experienced microaggressions where we either didn’t respond as well as we would have liked, or saw someone handle the situation brilliantly and were inspired. In order to facilitate practice dealing with microaggressions, we discussed, with <a href="https://twitter.com/brainfoodinator">Charlotte Zhao</a>, how beneficial it would be to run supportive, fun improv sessions where participants practice responding to microaggressions.² In subsequent discussions over the last few weeks, Benita has proposed hosting such an improv session in partnership with codebar at <a href="http://t.sidekickopen24.com/s1t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5X-FfhMynN4XrjtMdF2RzW56dxsc8J-W9P102?t=https%3A%2F%2Fmakers.tech%2F&amp;si=7000000001136063&amp;pi=4b943a91-5bf8-4a43-e400-6c84dbfdb3ec">Maker’s Academy</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cDJPa-4a_PM9KV48dBOfkw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGrsWRD_dJYFIxfNoB4hfg.jpeg" /><figcaption><a href="https://foundersandcoders.com/">Founders and Coders alumni</a>, image by <a href="https://twitter.com/isnotafunction">Ivi</a>; Benita Rajania’s powerful talk inspired pivotal hallway discussions, image by <a href="https://twitter.com/brainfoodinator">Charlotte Zhao</a></figcaption></figure><p>Although unconferences are free-form events, they do have “four principles and one law”, all of which are aimed at enabling participants to shape their unconference experience. The four principles of an Open Space are:</p><ol><li><strong>Whoever comes are the right people.</strong></li><li><strong>When it starts, it’s the right time.</strong></li><li><strong>Whatever happens is the only thing that could have.</strong></li><li><strong>When it is over, it is over.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*ecOqOAj1CjCcSIV7VSkpzg.jpeg" /><figcaption>The Four Principles of an Open Space. Image by <a href="https://twitter.com/KaraMarck">Kara de la Marck</a>, taken at <a href="http://socratesuk.org/">SoCraTes UK</a></figcaption></figure><h3>Rosa Emerald Fox on Twitter</h3><p>Loved @ThisIsJoFrank&#39;s talk about her journey in creating a tweet controlled LED wedding dress #uncodebar</p><p>The one law of an Open Space is the<strong> </strong><a href="https://agilecoachcamp.org/tiki-index.php?page=OpenSpace">Law Of Two Feet</a>:</p><p><em>If at any time you find that you are not benefiting from the discussion, neither learning nor contributing, use your two feet and move to some place more to your liking.</em></p><p>Participants are encouraged to leave or enter sessions mid-discussion, grab a cup of coffee if they need a break, or engage in their own hallway track. The key is that participants should not feel stuck in any session.</p><h3>Claire Inez Mitchell 👩🏻‍💻 on Twitter</h3><p>I&#39;m looking at @pinglinh&#39;s trello board for everything she&#39;s learned and accomplished at work and I&#39;m beyond impressed. A coding diary is a great idea both for making the case for a promotion, and also boosting your self confidence! #uncodebar #uncodebar4</p><h4>uncodebar4</h4><p>This is the fourth time we’ve run uncodebar, codebar’s annual unconference, and each year it has grown larger. I’m always amazed at how generous and enthusiastic the codebar community is when sharing knowledge and supporting each other.</p><p>The talks, workshops, and lightning talks we had were fantastic. I’m already looking forward to next year’s uncodebar. Given the caliber of coaches we have at codebar, I’ll be proposing a round table discussion on coaching, tips and lessons learned, at uncodebar5!</p><p>[1] Benita Rajania has done a wonderful, highly recommended write-up of the talk she gave at uncodebar 4. You may read it <a href="https://blog.makersacademy.com/why-stories-matter-for-creating-safe-inclusive-spaces-56d316246389">here</a>.</p><p>[2] We are considering naming the fun, supportive improv sessions, where we discuss microaggressions and practice responding to them, a Feminist Fight Club. However, I do worry about scaring people off from attending the sessions, which will be entirely and absolutely nonviolent. What do you think? Feel free to post your opinions in the comment section and, if you are interested in attending, what you would like to get out of the sessions!</p><p>Also, please post what uncodebar sessions you enjoyed the most and what you learned at uncodebar4!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb12fc542069" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-codelog/uncodebar-4-fb12fc542069">uncodebar 4</a> was originally published in <a href="https://medium.com/the-codelog">the codelog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Configuring Travis CI to enable devDependencies incompatible with Node versions your application…]]></title>
            <link>https://medium.com/jaegertracing/configuring-travis-ci-to-enable-devdependencies-incompatible-with-node-versions-your-application-da00991b93dc?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/da00991b93dc</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[travis-ci]]></category>
            <category><![CDATA[dependencies]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Fri, 02 Mar 2018 14:59:01 GMT</pubDate>
            <atom:updated>2018-03-18T14:30:25.547Z</atom:updated>
            <content:encoded><![CDATA[<h3>Configuring Travis CI to enable devDependencies incompatible with Node versions your application supports</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v4hleaFWMGkgsfGB62DJ7g.jpeg" /><figcaption>“Wishes” (Glass Feathers with 24k Gold Leaf) by <a href="https://www.instagram.com/KiaraPelissierStudios/">Kiara Pelissier</a></figcaption></figure><p>As part of the current <a href="https://www.outreachy.org/">Outreachy</a> cohort, I am contributing to the <a href="https://github.com/jaegertracing/jaeger-client-node">Node.js client library</a> for <a href="http://jaeger.readthedocs.io/en/latest/">Jaeger</a>, an open source distributed tracing system.</p><p>Recently, we ran into the problem of wanting to update our tooling in a way that incorporated dependencies that were incompatible with all the Node versions we support. Note: the <a href="https://github.com/jaegertracing/jaeger-client-node">Node.js client library</a> for <a href="http://jaeger.readthedocs.io/en/latest/">Jaeger</a> is committed to supporting Node v0.10 and up.</p><p>Yes, Node v0.10 and v0.12 have <a href="https://github.com/nodejs/Release">end-of-life status</a>. However, surveys suggest that <a href="https://semaphoreci.com/blog/2017/11/22/nodejs-versions-used-in-commercial-projects-in-2017.html">30</a> to <a href="https://semaphoreci.com/blog/2016/10/12/nodejs-versions-used-in-commercial-projects-2016-edition.html">50</a> percent of Node.js commercial projects are using Node v0.10 or v0.12 in production. Jaeger, as a distributed tracing system, provides the ability to monitor and troubleshoot microservices-based applications. Jaeger’s Node.js client supports versions 0.10 and up so that projects using those Node versions in production can have the benefit of observability into their microservices-based distributed systems.</p><p>However, Jaeger’s current commitment to supporting Node v0.10 had a limiting effect on the dependencies that we were using in the Node.js client library.¹</p><p>To recap, the most common types of dependencies in every project are dependencies and devDependencies. Your package.json specifies your project’s dependencies:</p><pre>{<br>   &quot;name&quot;: &quot;my-project&quot;,<br>   &quot;version&quot;: &quot;1.0.1&quot;,<br>   &quot;dependencies&quot;: {<br>      &quot;package-a&quot;: &quot;^1.1.2&quot;<br>   },<br>   &quot;devDependencies&quot;: {<br>      &quot;package-b&quot;: &quot;^1.5.0&quot;<br>   }<br>}</pre><p>The packages specified in dependencies are the dependencies needed when running your code.</p><p>The packages in devDependencies are your development dependencies. These are the dependencies that you need at some point during your development workflow but not when running your code (e.g. a test framework or a transpiler).</p><p>Previously, we had <a href="https://travis-ci.org/">Travis CI</a> configured to build and test each version of Node that Jaeger’s Node.js client supports.² In practice, this meant that our dependencies and devDependencies had to be compatible with every version of Node the Jaeger Node.js client supports, including Node v0.10.</p><p>Then we decided to upgrade from babel-preset-es2015 to babel-preset-env.</p><h4>Upgrading to babel-preset-env</h4><p>For transpiling ES2015+ to ES5, Babel recommends using <a href="https://babeljs.io/env/">babel-preset-env.</a> Without any configuration options, babel-preset-env behaves exactly the same as babel-preset-latest (or babel-preset-es2015, babel-preset-es2016, and babel-preset-es2017 together). You can also configure it to target certain browsers or runtime environments, and this will make your bundles smaller.</p><p>There were enough benefits that we decided to upgrade from babel-preset-es2015 to babel-preset-env. However, <a href="https://github.com/babel/babel-preset-env/blob/1cf2642029d4a0b92eacaba1d85b6a7fbe793dc9/package.json#L98">babel-preset-env targets node 4</a>.</p><p>Our .travis.yml was configured so that Travis would build and test for each Node version the Jaeger Node.js client supported. The start of our .travis.yml looked similar to this:</p><pre>language: node_js</pre><pre>node_js:<br>- &#39;node&#39;<br>- &#39;8&#39;<br>- &#39;6&#39;<br>- &#39;4&#39;<br>- &#39;0.12&#39;<br>- &#39;0.10&#39;</pre><p>Then we had a script that both built and tested each version of Node listed under node_js. The result was that upgrading our devDependencies to include babel-preset-env broke the Travis build for Node v0.10 and v0.12.</p><p>We needed to reconfigure our .travis.yml file so that we would be able to upgrade to newer versions of our tooling, and then, once the transpiling was done, run our tests in Travis with different versions of Node. In order to do so, we utilised the <a href="https://docs.travis-ci.com/user/customizing-the-build/#Build-Matrix">Travis build matrix</a>:</p><pre>language: node_js</pre><pre>node_js:<br>- &#39;6&#39;</pre><pre>matrix:<br>  include:<br>  - env: TEST_NODE_VERSION=0.10<br>  - env: TEST_NODE_VERSION=0.12<br>  - env: TEST_NODE_VERSION=4<br>  - env: TEST_NODE_VERSION=6<br>  - env: TEST_NODE_VERSION=node</pre><p>If there is one version of Node listed under node_js Travis will interpret that Node version as it’s default version. We can then use the Travis default Node version as our build version for every set of tests, thereby enabling the use of devDependencies irrespective of whether they are compatible with every Node version we support. We also customise our tests to run against every version of Node included as an env within the Travis matrix. To do so, first we install the Node version we will test against and then switch to the Travis default version:</p><pre>before_install:<br># Install the Node version to test against<br>- nvm install $TEST_NODE_VERSION<br># Switch back to build-time Node version<br>- nvm use $TRAVIS_NODE_VERSION</pre><p>Then we build with the Travis default version of Node, and afterwards switch to the version of Node we are testing within our Travis matrix:</p><pre>before_script:<br>- make build-node<br>- nvm use $TEST_NODE_VERSION<br>- node --version<br>- rm -rf ./node_modules package-lock.json<br>- npm install</pre><p>Notice that we print out to our Travis CI logs the Node version that we’ll be testing. We then remove all the node_modules that had been installed during the initial build and, importantly, the package-lock.json that had been installed during that build. We then initiate another npm install while using our TEST_NODE_VERSION.</p><p>This worked great while updating from babel-preset-es2015 to babel-preset-env! However, soon we thought to add <a href="https://prettier.io/">Prettier</a> to the project.</p><h4>Adding Prettier, Husky, and Lint-staged</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8H0ISK79mZ3cQDvjS8HLvg.jpeg" /><figcaption><a href="https://medium.com/front-end-hacking/prettier-an-opinionated-code-formatter-excellent-for-open-source-5ecd2685238f">Prettier: An Opinionated Code Formatter, Excellent for Open Source</a></figcaption></figure><p>I’ve written about Prettier and why we decided to add Prettier to Jaeger’s Node.js client <a href="https://medium.com/front-end-hacking/prettier-an-opinionated-code-formatter-excellent-for-open-source-5ecd2685238f">here</a>. To facilitate smoother collaboration, we decided to add a pre-commit hook using <a href="https://github.com/typicode/husky">husky</a> and <a href="https://github.com/okonet/lint-staged">lint-staged</a>, which would ensure that all PRs would be formatted by Prettier using our chosen configuration.</p><p>Unfortunately, husky could not be installed on Node v0.10/v0.12. The Travis CI build status page is great for seeing at a glance if the build passes or fails and, in our case, for which versions of Node. When failures occur, reading the logs in Travis CI is fantastic to find out more information. In our scenario, we could see that our final npm install in our before_script would error out when trying to install husky on Node v0.10/v0.12. My first attempt to solve this problem was to place husky as an optionalDependency within our package.json:</p><pre>&quot;devDependencies&quot;: {<br>...<br>},<br>&quot;optionalDependencies&quot;: {<br>  &quot;husky&quot;: &quot;^0.14.3&quot;<br>},<br>&quot;scripts&quot;: {<br>...</pre><p>Optional dependencies are just that: optional. If they fail to install, npm will continue with the installation process and, once completed, will consider the installation successful.</p><p>This is useful for dependencies that won’t necessarily work on every machine, or every version of Node your application supports. However, you do need to have a fallback plan in case the optionalDependencies are not installed. For Jaeger’s Node.js client library, this is not a problem as husky is a devDependency not necessary when running the application in production and our recommended Node version for development is Node 6.</p><p>To ensure we had no problem with our builds in Travis CI, for our final npm install in our before_script, we used a --no-optional flag, like so:</p><pre>- npm install --no-optional</pre><p>Our Travis CI tests all passed! Excellent.</p><p>Except, optionalDependencies are by default installed as dependencies not devDependencies. In other words, optionalDependencies are also production dependencies. Unfortunately, this meant that husky was being installed for consumers of the Node.js client library. What we needed was an optional devDependency.</p><p>More broadly speaking, for any package downloaded from npm, all production dependencies are installed, including optionalDependencies. Unsurprisingly, we weren’t the only ones wishing for optional devDependencies. The problem and possible solutions are discussed <a href="https://github.com/npm/npm/issues/3870">here</a>.</p><p>Happily, <a href="https://github.com/tiffon">Joe Farro</a>, came up with an elegant, simple solution that works for Jaeger’s Node.js client. Husky and lint-staged are now both listed as devDependencies in the package.json; however, before the final npm install in the before_script, we remove husky and lint-staged from the package.json :</p><pre>- npm uninstall -D husky lint-staged</pre><p>For clarity, I’ll explain the components of the above command.-D is an alias for --save-dev, which when used with npm install would ensure that the listed packages would both be installed in the local node_modules folder and be listed as devDependencies in your package.json. As we are using it with npm uninstall it does the opposite, removing the packages from within your devDependencies in your package.json. When we run, in the next step, the npm install command, those packages are no longer listed in the package.json and so there will be no attempt to install them. The before_script in the .travis.yml file now looks similar to:</p><pre>before_script:<br>- make build-node<br>- nvm use $TEST_NODE_VERSION<br>- node --version<br>- rm -rf ./node_modules package-lock.json<br>- npm uninstall -D husky lint-staged<br>- npm install</pre><p>In the end, I’m really happy with the solutions we’ve come up with for enabling us to update the devDependencies for Jaeger’s Node.js client library, and hope that this explanation is useful for others!</p><p><em>Note:</em> In an attempt to make this explanation of how we reconfigured our .travis.yml file more helpful to others, I have simplified the descriptions of Jaeger’s Node.js client library’s .travis.yml file. The Node.js client library for Jaeger is open source and the current .travis.yml file can be viewed <a href="https://github.com/jaegertracing/jaeger-client-node/blob/master/.travis.yml">here</a>.</p><p>[1] The Node.js client’s current support for Node v0.10 and up also has an effect on which package manager we use. The Jaeger Node.js client uses <a href="https://www.npmjs.com/">npm</a>, as <a href="https://github.com/yarnpkg/yarn/blob/aee005aa16a929a69730235e4f178f5a7bc5f81b/package.json#L95">yarn supports Node 4 and up</a>.</p><p>[2] <a href="https://travis-ci.org/">Travis CI</a> is a continuous integration service used to build and test projects hosted on GitHub. For Jaeger’s Node.js client we have Travis CI run our tests on every pull request made to the GitHub repo. The .travis.yml file tells Travis the programming language for your project and how to build it. Any step of the build <a href="https://docs.travis-ci.com/user/customizing-the-build">can be customized</a>.</p><p><a href="https://travis-ci.org/">Travis CI</a> is free for open source projects on GitHub. ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da00991b93dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jaegertracing/configuring-travis-ci-to-enable-devdependencies-incompatible-with-node-versions-your-application-da00991b93dc">Configuring Travis CI to enable devDependencies incompatible with Node versions your application…</a> was originally published in <a href="https://medium.com/jaegertracing">JaegerTracing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monki Gras 7]]></title>
            <link>https://medium.com/@karadelamarck/monki-gras-7-f90da99efa72?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/f90da99efa72</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Thu, 15 Feb 2018 13:09:36 GMT</pubDate>
            <atom:updated>2018-02-15T13:09:36.476Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H6CR6MIbzN4cjVWirJTa_A.jpeg" /><figcaption>Excellent stickers at this year’s <a href="https://monkigras.com/">Monki Gras</a>, many courtesy of <a href="https://twitter.com/mipsytipsy">Charity Majors</a>.</figcaption></figure><p><a href="https://monkigras.com/">Monki Gras</a> is a developer conference about craft culture. As <a href="https://twitter.com/monkchips">James Governor</a> describes it, ‘Monki Gras is about thinking about making’.</p><p><em>Thinking about making.</em> That simple yet incredibly broad statement gives a good indication of the essence of Monki Gras. Part of what differentiates this developer conference is the emphasis placed on what tech, as a craft, can learn from other craft disciplines. Consequently, we had fascinating talks that referenced typography, printmaking, vintage car maintenance, sustainable fashion, beer (of course), and even sushi.</p><p>The theme of this year’s Monki Gras was ‘Sustaining Craft’. How do we sustain what we do? <a href="https://twitter.com/jesslynnrose">Jessica Rose</a> addressed this at the level of the individual with an excellent talk on handling burnout. Other talks considered how to build things to last and maintain them once they are built.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DIPCBWgP-GZmATS_V8Xz7A.png" /><figcaption><a href="https://www.explainxkcd.com/wiki/index.php/1909:_Digital_Resource_Lifespan">xkcd</a></figcaption></figure><p><a href="https://twitter.com/cemerick">Chas Emerick</a> discussed the history of PDFs, from their inception with the explicit goal of changing ‘the fundamental way people work’,¹ to how PDFs have been a reliable data source over a sustained and continuing period of time.</p><p>PDFs have obviously been an incredibly successful and widely adopted technology. Creating communities of adopters and users is a perennial goal with technology. <a href="https://speakerdeck.com/trieloff">Lars Trieloff</a> shared the good advice, in his talk on <a href="https://speakerdeck.com/trieloff/sustaining-through-change-learning-from-20-years-of-aem-history">learning from 20 years of AEM history</a>, that using standards lowers the risk for new adopters² thus enabling wider, faster adoption:</p><blockquote>Technology adoption is a game of chicken.</blockquote><blockquote>Use standards to guarantee compatibility.</blockquote><p>Creating communities of adopters and users is a perennial goal with technology. Building communities is an ongoing theme at Monki Gras and, this year, with sustainability as the theme, talks addressed how to build communities to maintain what we create and the importance of respecting the people that will come after us to maintain the systems we build.</p><p>Maintaining the maintainers, especially of open source projects, is a vitally important issue for the tech industry. Although open source software may appear to be free to consumers, someone is paying for it. <a href="https://twitter.com/piamancini">Pia Mancini</a>, cofounder of <a href="https://opencollective.com/about">Open Collective</a>, spoke on how they are enabling groups, such as open source projects, to become more financially sustainable.³</p><p>In her talk on ‘Sustainable Software Development’, <a href="https://twitter.com/mipsytipsy">Charity Majors</a>, CEO of <a href="https://twitter.com/honeycombio">Honeycomb</a>, emphasised that the craft of software engineering <em>is about maintainability</em>. Her clarion call is that it is time to stop pretending that maintenance and supporting production aren’t central to software engineering, and that this includes software engineers being prepared to be on-call.</p><p>Monki Gras mines the connections and insights that can be generated between disparate disciplines. What this means, as James Governor noted, is that, ‘When you put together a conference like this, weird themes emerge that you didn’t necessarily expect’. For me one theme was that of access, especially to power and knowledge, and inclusion. <a href="https://twitter.com/ThinkingType">Catherine Dixon</a> emphasised that the new technology of the printing press in 1450 revolutionised who had access to the written word. <a href="https://twitter.com/aneel">Aneel Lakhani</a> spoke eloquently on how power and knowledge are distributed under our current systems of production and consumption, in which the end consumer is a product whose consumption is sold by marketers and middlemen to producers of goods. <a href="https://twitter.com/mandywhaley">Mandy Whaley</a> drew parallels between the life and professional struggles of Marie Curie and some of the issues facing the tech industry today.</p><p>Monki Gras itself addresses the issue of access and inclusion in the tech industry by running a robust <a href="https://monkigras.com/diversityinclusion/">Diversity and Inclusion programme</a>.⁴</p><p>Monki Gras is very much about maintaining and fostering community. The ‘hallway track’ is fantastic, with space and time for attendees to meet, consider each other’s interpretations of the talks, and discuss potential new projects. All fueled by excellent food, coffee, and drinks.⁵ For James, ‘Sustaining the craft is about sustaining relationships’.</p><p>I was fortunate to be able to attend Monki Gras this year thanks to the generosity of the organisers and the support of my team at <a href="http://jaeger.readthedocs.io/en/latest/">Jaeger</a> tracing, who are mentoring me whilst I participate in the <a href="https://www.outreachy.org/">Outreachy</a> programme.⁶</p><p>For those who would like to watch the talks from this year’s Monki Gras, keep an eye on the <a href="https://www.youtube.com/channel/UCaUtAK8xECTkETCYivJegeQ/videos">RedMonk Tech Events</a> channel!</p><p>[1] The code name for the PDF project was ‘The Camelot Project’: <a href="https://blogs.adobe.com/acrobat/files/2013/09/Camelot.pdf">https://blogs.adobe.com/acrobat/files/2013/09/Camelot.pdf</a></p><p>[2] I was first introduced to the beauty of this idea with <a href="http://jaeger.readthedocs.io/en/latest/">Jaeger</a>, an open source distributed tracing system that is compatible with the <a href="http://opentracing.io/documentation/">OpenTracing</a> standard for distributed tracing.</p><p>[3] Open Collective enables groups to set up a collective, raise funds, and manage them transparently.</p><p>[4] <a href="https://twitter.com/_notwaving">Samantha Burke</a> did an excellent job managing this year’s Diversity and Inclusion programme.</p><p>[5] Monki Gras’ production and catering manager is Saffron Governor and she does a wonderful job.</p><p>[6] Still feeling this:</p><h3>Kara de la Marck on Twitter</h3><p>When you manage to get a last minute ticket to @monkigras, thanks to @monkchips, @_notwaving, &amp;amp; @geirmagnusson, and your team @JaegerTracing (@YuriShkuro &amp;amp; @ploffay) are all supportive and kind about you going to Monki Gras: https://t.co/tBvLJgKWD1</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f90da99efa72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prettier: An Opinionated Code Formatter, Excellent for Open Source]]></title>
            <link>https://medium.com/front-end-weekly/prettier-an-opinionated-code-formatter-excellent-for-open-source-5ecd2685238f?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ecd2685238f</guid>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 13:53:55 GMT</pubDate>
            <atom:updated>2018-01-30T14:04:48.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zaGeU8qPRDCyu6IoWH4EPA.jpeg" /><figcaption>Cherry Blossom Avenue, Greenwich Park, London</figcaption></figure><p>As part of my work with <a href="https://www.outreachy.org/">Outreachy</a> on <a href="http://jaeger.readthedocs.io/en/latest/">Jaeger</a>, an open source distributed tracing system, we’ve recently added Prettier to the <a href="https://github.com/jaegertracing/jaeger-client-node">Node.js client library</a>. 🎉</p><h4>Why Prettier is great for open source</h4><p><a href="https://prettier.io/">Prettier</a> is an opinionated code formatter. In practice, this means that Prettier leverages what computers are good at — parsing and analysing code — to enable smoother, easier collaboration in software development.¹</p><p>This is fantastic for many teams and projects, but especially for open source, where contributors are usually dispersed, often strangers, and sometimes new to the project. With Prettier, individuals who are not familiar with the project’s style guidelines have one less thing to worry about when making a pull request. And owners, maintainers, and collaborators don’t have to enforce a style guide using nits in code reviews. At the same time, Prettier makes code formatting consistent across an entire codebase, increasing legibility.</p><p>Prettier makes formatting computers’ work.</p><h4>More about Prettier</h4><p><a href="https://prettier.io/">Prettier</a> is an opinionated code formatter that supports JavaScript (including ES2017), JSX, Flow, TypeScript, JSON, CSS, Less, SCSS, styled-components, Markdown, and GraphQL.</p><p>Prettier guarantees consistency in formatting by parsing your code into an abstract syntax tree (AST) and pretty-printing the AST.</p><p>All of your original styling choices are gone² and your code is pretty-printed to a standard style, with some <a href="https://prettier.io/docs/en/options.html">options</a> that you and your team can decide on and preconfigure.</p><h4>What does Prettier mean for you?</h4><p>It means you can write stylistically idiosyncratic code and Prettier will fix it for you.</p><p>Hate writing semicolons in JavaScript? Can’t remember what statements are affected by the <a href="http://www.ecma-international.org/ecma-262/7.0/index.html#sec-rules-of-automatic-semicolon-insertion">rules of automatic semicolon insertion</a>? No problem, leave out all semicolons and Prettier will handle them for you.</p><p>Hard to decide what is the ‘best’ way to format a long argument list? Prettier will format that argument list beautifully for you.</p><p>Want to press Enter less often and instead write your code in one long line? Your teammates won’t be annoyed, because Prettier will prettify your code before they ever see it.</p><p>There is a huge amount of formatting decisions you’ll never need to think about again — that’s true for the individual developer and for the team. The background noise of constant small decisions about formatting is gone.</p><p>When I first started learning JavaScript, involved discussions on tabs versus spaces still happened. My favourite joke about those conversations is by <a href="https://twitter.com/richardwestenra">Richard Westenra</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*9OaKEErLtSpOFI6tvD4lPw.jpeg" /></figure><p><em>‘Personally, I prefer to increase the spacing for each successive indent according to the Fibonacci sequence.’</em></p><p>Fine. Each individual on your team, or contributor to your open source project, can write their own stylistically idiosyncratic code and Prettier will pretty-print it before anyone else has to read it. Or code review it.</p><p>You can ensure that PRs are prettified before they are reviewed, thus removing the need for nits regarding styling or formatting.</p><h3>GitHub on Twitter</h3><p>Spending too much time in code reviews on tabs vs. spaces? Leave your JavaScript formatting to Prettier 1.0: https://t.co/2Sv1vMpOEA https://t.co/0Ydsyf8so1</p><p>Prettier is a fantastic productivity win for developers, teams, and especially open source projects, where contributors are usually dispersed, often strangers, and sometimes new to the project. Prettier not only makes code formatting consistent across an entire codebase, it makes reading and reviewing each other’s code easier. It makes teamwork smoother. And it simplifies at least one aspect of contributing to open source.</p><p>Prettier is great because it is an elegant technical solution to what is above all a human problem of communication around code. That you and your team will find Prettier’s default style, with <a href="https://prettier.io/docs/en/options.html">limited options</a>, acceptable and even beautiful is something that Prettier’s contributors have worked hard to ensure. <a href="https://twitter.com/vjeux">Christopher Chedeau</a> gave a fascinating talk on the subject at <a href="https://react.london/">React London 2017</a>.³</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F0Q4kUNx85_4%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D0Q4kUNx85_4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F0Q4kUNx85_4%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b92bc851aad1bbe197a6170386f628e/href">https://medium.com/media/8b92bc851aad1bbe197a6170386f628e/href</a></iframe><p>Hopefully, this blog post has inspired you to use Prettier in your next project, or add it to an existing repository. Installing and using Prettier in a project is generally a straightforward process, and <a href="https://prettier.io/docs/en/install.html">Prettier’s documentation</a> is exemplary.</p><p>[1] Auto-formatting is not a new idea in software. <a href="https://twitter.com/jlongster">James Long</a>, who created Prettier, was inspired by Reason’s refmt tool. <a href="https://jlongster.com/A-Prettier-Formatter">His article on Prettier</a> is fantastic.</p><p>[2] Some original styling is preserved when practical — see in the docs how Prettier handles <a href="https://prettier.io/docs/en/rationale.html#empty-lines">empty lines</a> and <a href="https://prettier.io/docs/en/rationale.html#multi-line-objects">multi-line objects</a>.</p><p>[3] I’m very grateful to <a href="https://red-badger.com/">Red Badger</a>, who organised <a href="https://react.london/">React London 2017</a>, for providing me with the opportunity to attend the conference. I first heard of Prettier during React London 2017 and have happily used it ever since.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ecd2685238f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/front-end-weekly/prettier-an-opinionated-code-formatter-excellent-for-open-source-5ecd2685238f">Prettier: An Opinionated Code Formatter, Excellent for Open Source</a> was originally published in <a href="https://medium.com/front-end-weekly">Frontend Weekly</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Outreachy! Building diversity in open source]]></title>
            <link>https://medium.com/jaegertracing/outreachy-building-diversity-in-open-source-2cb89b396e1a?source=rss-8d5575680261------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cb89b396e1a</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[outreachy]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Kara de la Marck]]></dc:creator>
            <pubDate>Tue, 19 Dec 2017 15:15:10 GMT</pubDate>
            <atom:updated>2018-02-01T23:00:15.903Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBetHqP7GhoXXirWkK8jiQ.jpeg" /><figcaption>Image by <a href="https://twitter.com/frathgeber">Florian Rathgeber</a></figcaption></figure><h4>What is Outreachy?</h4><p><a href="https://www.outreachy.org/">Outreachy</a> organises three-month paid internships with free and open source software projects for people who are underrepresented in open source and in tech generally.¹ The goal of Outreachy is to “create a positive feedback loop” that supports more women participating in free and open source software.²</p><p>Organisations that participate in Outreachy include <a href="https://wiki.gnome.org/Outreach/Outreachy">GNOME</a>, the <a href="https://kernelnewbies.org/OutreachyIntro">Linux Kernel</a>, <a href="https://www.mediawiki.org/wiki/Outreachy">Wikimedia</a>, <a href="https://wiki.debian.org/Outreachy/Round15/">Debian</a>, <a href="https://git.github.io/Outreachy-15/">Git</a>, <a href="http://opentracing.io/outreachy">OpenTracing</a>, and <a href="https://www.cncf.io/">CNCF</a>. These organisations have specific projects for the interns to work on and provide remote mentors.³</p><p>The programme runs twice a year, with summer and winter cohorts.</p><p>I recently joined the December 2017 cohort of Outreachy, and now have the opportunity to be mentored by collaborators on the <a href="https://uber.github.io/jaeger/">Jaeger tracer</a> while contributing to the <a href="https://github.com/jaegertracing/jaeger-client-node">Jaeger Node.js client</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*7hCC2FuQrR4Yc1g57ccMHA.png" /><figcaption>Jaeger mascot</figcaption></figure><h4>What is Jaeger?</h4><p><a href="https://github.com/jaegertracing/jaeger">Jaeger</a> is a distributed tracing system, developed by <a href="http://opentracing.io/outreachy">Uber Engineering</a>, and released as open source in early 2017. A few months later, Jaeger became the 12th project to become hosted by the <a href="https://www.cncf.io/">Cloud Native Computing Foundation</a>.</p><p>Note: Jaeger (ˈyā-gər) is German for hunter or hunting attendant</p><h4>What is a distributed tracing system?</h4><p>A distributed tracing system is used to monitor, profile, and troubleshoot complex, microservice-based architectures. Modern microservice architectures have numerous advantages; however, there can be a loss of visibility into a microservices based system, specifically the interactions that occur between services. Traditional monitoring tools such as metrics and logging are still valuable, but they fail to provide visibility <em>across services</em>. This is where distributed tracing thrives.⁴</p><p>Distributed tracing provides observability of what is happening inside the flow of an application. Distributed tracing systems use traces to tell the story of a transaction or workflow as it propagates through a potentially distributed system. Jaeger, as a distributed tracing system, provides a concrete set of tracers and a trace storage backend, for usage on applications and microservices instrumented with <a href="http://opentracing.io/documentation/">OpenTracing</a>.</p><h4>What is OpenTracing?</h4><p>Many contemporary distributed tracing systems have application-level instrumentations that are incompatible, meaning that vendor lock-in can occur as systems become tightly coupled to a particular distributed tracing implementation. <a href="http://opentracing.io/talks-and-videos/">OpenTracing</a>, as an API standard, provides a series of vendor-neutral and language agnostic APIs for distributed tracing systems. OpenTracing thus makes it easy for developers to switch tracing implementations.</p><p>Jaeger has OpenTracing compatible client libraries in <a href="https://github.com/jaegertracing/jaeger-client-go">Go</a>, <a href="https://github.com/jaegertracing/jaeger-client-java">Java</a>, <a href="https://github.com/jaegertracing/jaeger-client-node">Node</a>, <a href="https://github.com/jaegertracing/jaeger-client-python">Python</a>, and <a href="https://github.com/jaegertracing/cpp-client">C++</a>. I am contributing to the <a href="https://github.com/jaegertracing/jaeger-client-node">Jaeger Node client</a> and, as a first step, am rewriting the <a href="https://github.com/yurishkuro/opentracing-tutorial/tree/master/nodejs">OpenTracing tutorial for Node.js</a>. That should be my next blog post! :)</p><h4>How does the first photo fit in?</h4><p>In early December, I spoke about Outreachy and how to apply at <a href="https://ti.to/codebar/24-pull-requests-2017/discount/codebar">codebar’s annual 24 Pull Requests event</a>. <a href="https://codebar.io/">codebar</a> runs regular programming workshops for underrepresented people with the goal of making technology and coding more accessible. At 24 Pull Requests, mentors help students who are new to programming learn how to contribute to open source and make their first PRs. The photo is of all the mentors at the event who are alumni of <a href="https://foundersandcoders.com/">Founders and Coders</a>, the full-stack JavaScript bootcamp I attended.</p><p>Supporting diversity in tech and in open source is important to me. If you have any questions about Outreachy, or would like advice on applying to the programme, I would love to chat with you! :) DM me on Twitter <a href="https://twitter.com/karamarck?lang=en">@KaraMarck</a>.</p><p>[1] Eligibility requirements for Outreachy can be found at: <a href="https://www.outreachy.org/apply/eligibility/">https://www.outreachy.org/apply/eligibility/</a></p><p>[2] <a href="https://en.wikipedia.org/wiki/Outreachy">https://en.wikipedia.org/wiki/Outreachy</a></p><p>Information about diversity in open source:</p><ul><li><a href="https://www.wired.com/2017/06/diversity-open-source-even-worse-tech-overall/">Diversity in Open Source Is Even Worse Than in Tech Overall</a></li><li><a href="http://opensourcesurvey.org/2017/">Open Source Survey</a></li></ul><p>[3] Additional information on the organisations and projects participating in Outreachy winter 2017 can be found at: <a href="https://www.outreachy.org/apply/rounds/2017-december-march/">https://www.outreachy.org/apply/rounds/2017-december-march/</a></p><p>[4] ‘Evolving Distributed Tracing at Uber Engineering’ by Yuri Shkuro: <a href="https://eng.uber.com/distributed-tracing/">https://eng.uber.com/distributed-tracing/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cb89b396e1a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jaegertracing/outreachy-building-diversity-in-open-source-2cb89b396e1a">Outreachy! Building diversity in open source</a> was originally published in <a href="https://medium.com/jaegertracing">JaegerTracing</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>