<?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 DV Team on Medium]]></title>
        <description><![CDATA[Stories by DV Team on Medium]]></description>
        <link>https://medium.com/@dvteam?source=rss-bb7dcbdbb6ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FuUGVTsLFZ-eKARHbOb66Q.jpeg</url>
            <title>Stories by DV Team on Medium</title>
            <link>https://medium.com/@dvteam?source=rss-bb7dcbdbb6ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:05:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dvteam/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[Recap: Halfway through]]></title>
            <link>https://medium.com/@dvteam/recap-halfway-through-808ed7c83de?source=rss-bb7dcbdbb6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/808ed7c83de</guid>
            <category><![CDATA[living-style-guide]]></category>
            <category><![CDATA[rgsoc]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[summer-of-code]]></category>
            <dc:creator><![CDATA[DV Team]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 11:06:37 GMT</pubDate>
            <atom:updated>2018-08-20T20:42:30.910Z</atom:updated>
            <content:encoded><![CDATA[<p>Recap: Halfway through</p><p>We can’t believe we are already halfway through RGSoC. It has been a great journey so far and we would love to share a recap with you!</p><h3>Nico @ 🌞 on Twitter</h3><p>The exciting part: We&#39;re building a #JavaScript version during #RGSoC! https://t.co/zzC4UD5kU8</p><p>Here are some of the most important points:</p><h4>Communication &amp; Workflow</h4><p>RGSoC requires us to define our general workflow, we can decide how and when to work, which is great considering that we work 40hs a week + 20hs on RGSoC and it’s also helpful to identify how we are most productive. At the same time, I believe it has been quite a challenge for the whole team to be on the same page and figure out how to work together. What we’ve learn so far is that pair programming is great for a kick-off and to get unstuck but it’s best to work on separate tasks in order to progress faster. We’ve decided to divide the issues to solve and this has lifted from us the pressure of having to keep up each other’s pace and figure out how to communicate when having opposite daily schedules. Working remote is a struggle but overall we have improved our workflow since the beginning and we are finally moving forward smoothly.</p><h4>Understanding Living Style Guide</h4><p>The second struggle for us was to understand the project and the code. It was really hard for us to jump into the issues, try to figure out what they were about, what was expected from us and where all those lines of code came from. We dedicated the first month to work very hard in order to improve our level of Git/GitHub, modular JS, ways of writing better code, testing and so on. We hit the biggest bump when we found ourselves disconnected from our coaches and without guidance. We knew we need to modify the way we worked and communicated to move forward but we didn’t know how and the project seemed too complicated for our level. At this point our supervisor <a href="https://twitter.com/medk_">Lucas</a> was a big support for us, as well as the other teams on RGSoC. Many gave us advice and resources, and <a href="https://github.com/sujinleeme?tab=overview&amp;from=2015-12-01&amp;to=2015-12-31">Sujin</a> from <a href="https://railsgirlssummerofcode.org/blog/2018-08-18-team-sunshine">Team Sunshine</a> even found us a new coach who is available everyday! Our new coach’s name is <a href="http://github.com/benevbright">Bright</a> and he just moved to Berlin to work as a mobile developer. He knows a lot about JavaScript and has helped us non stop since day 1.<br>When we started to feel a bit more confident, our project mentor <a href="https://github.com/hagenburger">Nico</a>, walked us through the code and explained how some parts worked. It was a key moment as we realised it was not that we were not ready for the challenge, but rather we needed some help in understanding the project and the tasks.</p><h4>Dealing with frustration</h4><p>Frustration management has been one of the biggest lessons learned so far. We learned that frustration can present itself as anxiety, low self-esteem, feeling lost or disconnected. I think <a href="https://medium.com/@diana.vile">Diana</a> and I deal differently with it. I found myself trying to fill in the gaps I felt I didn’t had 100% covered. For example, learning unit testing to feel more confident about it. But then I jumped into another subject I didn’t feel confident about, and then another one. I wasn’t getting any progress on the issues this way, I thought it was my lack of knowledge but in reality I needed clarification on the issues and some explanation about the code. I think working remotely added to it, as we weren’t communicating well which created much more confusion between the whole team. Reading other team’s daily logs created some extra anxiety for me, as I felt everyone was advancing and solving things but when I started talking to some of the team members I realised we were all struggling with pretty much the same issues. The combination of working remotely, self organising, depending on other people to advance, getting proper support from the coaches and jumping into a project that has been coded by someone else were some of the challenges everyone was facing.</p><h4>Our first tech conference of the Summer</h4><p>If you haven’t heard about it, we were lucky enough to attend <a href="https://medium.com/u/b7872dbf3fa">JSCamp 2018</a> and meet really cool people. Read more about it and all the amazing talks in <a href="https://medium.com/@dvteam/our-experience-at-jscamp-barcelona-2018-713dfe6fdf0e">this link</a>.</p><h3>Violeta on Twitter</h3><p>Waiting for #JsCampBCN to begin! @RailsGirlsSoC @jscamptech #womenwhocode</p><h4>Our first PRs</h4><p>After navigating through the first month, we managed to do our first Pull Request and close issue #2! We were super proud and Nico helped us a lot to improve the code in order to close it.</p><h3>LivingStyleGuide on Twitter</h3><p>🎊This morning we got our first pull request with our @RGSoC team @artnerdnet &amp;amp; @dianavile! https://t.co/xXvIxI5rfU</p><p>After that, we discussed about having more issues available to pick so we can keep working in case we get stuck with one in particular. We also started collaborating with documentation, we saw how important it was to have it available and it is something that needs a lot of work right now. Another thing we have been talking about is improving the Living Style Guide website so people can quickly grasp the main concepts and fall in love with the project.</p><h3>Nico @ 🌞 on Twitter</h3><p>I wrote a lot of tickets today - partially to support my #RGSoC team, partially to get a roadmap for v1.0.0 of the #JavaScript version of LivingStyleGuide: https://t.co/D2pvBwaq5L</p><p>For now, <strong>we are getting closer to do more Pull Requests and we can’t wait to see the LSG grow more and more in the next half of the summer!</strong></p><p>- <a href="http://www.twitter.com/artnerdnet">Violeta</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=808ed7c83de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Experience at JsCamp Barcelona 2018]]></title>
            <link>https://medium.com/@dvteam/our-experience-at-jscamp-barcelona-2018-713dfe6fdf0e?source=rss-bb7dcbdbb6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/713dfe6fdf0e</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[rgsoc]]></category>
            <category><![CDATA[jscamp]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[DV Team]]></dc:creator>
            <pubDate>Fri, 27 Jul 2018 08:25:25 GMT</pubDate>
            <atom:updated>2018-09-19T15:19:28.411Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/@diana.vile">Diana</a> &amp; <a href="http://www.twitter.com/artnerdnet">Violeta</a></p><p>We were able to attend the great JsCamp Barcelona 2018 thanks to the efforts of the organizer David Pich who gave us last minute tickets! We were very happy to find out that he is very committed to make the tech field diverse and friendly, and the general atmosphere confirmed that intention!</p><p>As for the speakers, we are still learning and listening to these people speak about their visions and knowledge was very inspiring. We keep finding new possibilities to explore and learn. In this article, we share our notes about some of the talks we loved:</p><h3><strong>#JSCAMPBCN 2018: The past, the present and the future of Javascript and beyond</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*umOkwt0wxuKQU4dAZyAhFw.jpeg" /></figure><p>A place where 530 JavaScript developers from 52 different countries come together to hear the latest and greatest of Javascript and beyond from world first class JavaScript experts. That is in short what <a href="https://jscamp.tech/">#JSCAMPBCN</a> is about. But it is more than that, as <a href="https://twitter.com/davidpich/">David Pich</a>, the organizator of JS Camp BCN 2018, says:</p><blockquote>“<em>this is not just a conference, this is an ongoing future project.</em>”</blockquote><p>Read what the experts foresee as the future of JavaScript and beyond.</p><h4><strong>DIVERSITY IN TECH</strong></h4><p>One of the main things, David Pich likes to see in the sector is <a href="https://medium.com/@JavaScriptCamp/diversity-scholarship-program-792adf5b53e2">more diversity in tech</a>:</p><blockquote><em>“Only 12% of the congress participants are women, thanks to the Diversity Program</em>.<em> </em><strong><em>We need a more diverse group of developers </em></strong><em>for we develop solutions for the entire society.” <br></em>-David Pich</blockquote><p>Looking at the attending pro-minority groups sponsors like <a href="https://www.mozilla.org/en-US/">Mozilla</a> and <a href="https://www.npmjs.com/">NPM</a>, the diversity scholarship programs and the various female speakers give the impression, that this is not just words.</p><h3>JSCamp #JSCampBCN on Twitter</h3><p>Code as an opportunity to have a better future. We were proud to welcome three students from @codeyourfuture_ We will keep collaborating to make an impact, We believe that there&#39;s big value in every human connection and in every bond... especially when times get tough. https://t.co/fEodENPTPa</p><h4><strong>THE FUTURE IS DIGITAL</strong></h4><p>David’s introductory speech is followed up by <a href="http://www.ajuntamentimpulsa.cat/es/entrevista-a-daniel-marco-parraga.aspx">Daniel Marco Párraga</a>, Director of Smart Catalonia strategy of the Government of Catalonia<em>,</em> convinced that Barcelona is in the midst of a digital transformation,<strong> the future is digital </strong>and it needs to be citizen centered: “<em>smarter digital development and developing software need to be used to help society improving social cohesion and meet the needs of the citizens</em>. <em>With JSCamp, BCN Mobile World Conference and a diverse ecosystem of 15.000 tech startups, — with companies like Zurich, Volkswagen, Nestly, Amazon, Facebook and King- Barcelona is transforming itself into the 5th Digital Hub in Europe. “Barcelona is in the midst of a digital transformation to the front-row strategy of TECH for future generations.</em>”</p><h3><strong>THE PAST AND PRESENT OF JAVASCRIPT</strong></h3><h3></h3><p></p><h4><strong>THE PAST, PRESENT AND FUTURE OF THE WEB<br>A talk by </strong><a href="https://jscamp.tech/speakers/steve-klabnik/"><strong>Steve Klabnik</strong></a></h4><blockquote><em>“The core technologies of the web -HTML, CSS and JavaScript- were build 23 years ago. The fundamental ideas remain still the same.” <br>- </em><a href="https://jscamp.tech/speakers/steve-klabnik/">Steve Klabnik </a>from <a href="https://www.mozilla.org/en-US/">Mozilla</a>.</blockquote><p>The speaker reminded us that the web wasn’t build too long ago.</p><p>In August of 1991, the first pictureless website goes live. This is the beginning of the HyperText based-language <a href="https://developer.mozilla.org/en-US/docs/Glossary/HTML">HTML</a> (known as the World Wide Web). Three years later (1994), <em>Hakon Wium Lie</em> send his first proposal to style websites: the start of the Cascading Style Sheets<a href="https://developer.mozilla.org/en-US/docs/Glossary/CSS"> CSS</a>. Followed, one year later (1995), by <em>Brendan Eich</em> who created <a href="https://developer.mozilla.org/en-US/docs/Glossary/JavaScript">JavaScript </a>in a short amount of time.</p><p>As one of the core members of the Rust team and WebAssembly, Klabnik leads the documentation team. He believes <strong>time has come to redesign the web. </strong>Mozilla, the place he works for, is often seen as the “platform team”, yet he would rather like to see it as “<strong>the web application platform</strong>”, as the web provides a platform for developers to build applications on it. A <strong>platform</strong> consists of three layers:</p><ol><li><strong>ISA:</strong> Instruction Set Architecture (what can the code do?)</li><li><strong>Runtime environment &amp; its API </strong>(which syntax is recognized in the language?)</li><li><strong>Tools:</strong> to help developers build things</li></ol><p>Steve points out the shortcomings of the web platform. “<em>The web platform is unusual, in the sense that is was developed out of order and historically lacks a platform. Whereas other platforms were local first and later become networked based, the web platform is quite the opposite: it has always been network based and only now is becoming local.</em>”</p><p><strong>Time has come to have offline web apps available</strong>,<strong> not only online first apps</strong>:</p><blockquote>“T<em>he problem of the current web architecture is that it limits the kind of Apps developers can build on the web platform. The web application platform not only experiences tech limitations, but also the way it is build seriously limits the imagination of web developers.</em>”</blockquote><blockquote>-<a href="https://jscamp.tech/speakers/steve-klabnik/">Steve Klabnik</a></blockquote><p>Steve seriously doubts if JavaScript will be able to deal with offline web apps, as JavaScript has never been designed for the task of web platform application in the first place. It is possible to compile languages into Javascript, but this has significant drawbacks:</p><ol><li>JavaScript creates <strong>lots of overhead </strong>(to download, parse, compile and execute the code)</li><li>JavaScript does <strong>not accept integers</strong></li><li>The JavaScript <strong>spec is far too complex </strong>(too big and complicated).</li></ol><p>Previously, the web could only handle “<em>high level tasks</em>”, but with the invention of the Web Platform <a href="https://webassembly.org/">WebAssembly</a> (WASM), the platform can handle “<em>lower level task</em>” as well. Web Assembly is able to:</p><ol><li>Create <strong>universal cross-platform applications (available offline)</strong>.</li><li>With <strong>no installation needed </strong>(no config files are needed).</li><li>Enable <strong>deployment on the web</strong> for <strong>both client and server </strong>applications.</li></ol><p>With this new tool, the web platform is closing in on offline Applications. Although <strong>JavaScript, will probably never be completely replaced</strong>, Steve foresees <strong>the future of the web being more related to Web Assembly instead of JavaScript only</strong>. “<em>The platform is expanding, soon web apps do no longer need network applications or web pages, as associated with the web platform today. Imagine your web application to be available directly in the browser, without any need to access the internet.” </em>Until now it is only available on the Google Chrome browser, not yet fully supported by other browsers.</p><h4><strong>KEEP BETTING ON JAVASCRIPT<br>A talk by </strong><a href="https://jscamp.tech/speakers/kyle-simpson/"><strong>Kyle Simpson</strong></a></h4><h3>Elisabeth Engel on Twitter</h3><p>&#39;Code is about communicating our ideas to other human beeings&#39;, so no need to shorten it down. Thanks to @getify for such a convenient way of pointing that out visually! #JSCampBCN https://t.co/OgTxBGQmkL</p><blockquote><em>‘Always Bet On JavaScript’</em></blockquote><blockquote>-Brendan Eich</blockquote><p><a href="https://jscamp.tech/speakers/kyle-simpson/">Kyle Simpson</a>, author of <a href="https://github.com/getify/You-Dont-Know-JS">“You Don´t Know JavaScript”</a>, evangelist of the Open Web and very passionate about JavaScript, looks back to the history of JavaScript to be able to predict its future:<em> “It’s safe to say that JavaScript (JS) is no longer trying to prove itself. It has arrived. Even if it was once a ‘dumb kid brother’ to something like Java, it’s now fully a first class citizen in the programming language ecosystem. JS is certainly not the only dominant language or the ‘best tool’ for every situation. But increasingly, most tech stacks have it as a central part of their strategy.”</em></p><h4><strong><em>JAVASCRIPT PAST, PRESENT AND FUTURE</em></strong></h4><p><strong>JavaScript has become the “<em>lingua franca</em>” of the web: “</strong><em>Javascript is not slow, sloppy, buggy, inconsistent. Instead, it is fasts evolving. It is a first class language and has its potential to be the most important language. So, JavaScript has come a far way.” says the speaker.</em></p><p>Yet ever since the beginning of <strong>Javascript, it has been an evolution of small baby steps</strong>: closures, strict modes, objects, extra features, promises, asynchronous, async functions and async generators have been added in a period of 23 years.</p><p>Simpson doubts if this is the right way to continue. “<em>Are incremental, open baby steps good to continue? Only focussing on such tiny steps, without the main roadmap in sight, is not useful. As JavaScript has too many layers of abstraction and we lose sight of our view source. We are experiencing a gap between JavaScript language and JavaScript machine (the JavaScript Engine). They are starting to become two opposite galaxies.</em>” says Kyle.</p><p>According to him <strong>the future of JavaScript is based on Open Web Technology with HTML5, CSS3 and PWA, taking into account Accessibility issues and build with open collaboration of the community. </strong>Taking into account that JavaScript and software development are all about human communication and code is about expressing ideas to other human beings, Kyle argues the need of one “human based JavaScript” to bridge the gap between “JavaScript as the language” and Javascript Engine (machine).</p><p>Web Assembly if fine, as it can take modern languages like Go and Rust to transform into machine code the JavaScript Engine can understand. It is much faster and takes less parsing (encoding) time. Yet, Web Assembly is not compatible with plain JavaScript, as Vanilla JavaScript is often called.</p><blockquote>Kyle Simpson argues to<strong> focus on Human JavaScript instead. </strong><em>“Nowadays, a new learner has to figure out many different parts. We should not longer think about baby steps, but focus on the dual direction of the JavaScript language: JavaScript as a language versus JavaScript the Machine Engine. It is time to focus on human JavaScript instead.”</em></blockquote><h3>Sergio Revilla on Twitter</h3><p>It&#39;s a hard work for browsers to run JavaScript. Better if we know this. Thanks to @bmeurer for explain to us #JSCampBCN @jscamptech</p><h4><a href="https://slidr.io/bmeurer/javascript-engines-a-tale-of-types-classes-and-maps#1"><strong>A TALE OF TYPES, CLASSES AND MAPS</strong></a></h4><p><strong>A talk by </strong><a href="https://jscamp.tech/speakers/benedikt-meurer/">Benedikt Meurer</a></p><p><a href="https://jscamp.tech/speakers/benedikt-meurer/">Benedikt Meurer</a> is a JavaScript compiler engineer at Google, currently involved in the V8 JavaScript engine that works with both Node.js and Chrome. In his talk he explores the most important ingredients of modern JavaScript engines and how these ingredients make it possible to write great JavaScript applications:</p><blockquote><strong><em>“JavaScript is very likely the most influential technology of our time in software engineering. </em></strong><em>A lot of this is due to the sophisticated JavaScript engines in modern browsers, Node, and Electron</em>”.<br>-Benedikt Meurer</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6KbbDK7sBJkV62lX" /></figure><p><em>Picture: The working of a JavaScript Engine.</em></p><p>Although <strong>JavaScript engines</strong> have much in common among different web browsers, they <strong>differ in their optimization tiers. </strong>Basically, JavaScript engines need to choose between “Generate their code quickly”, or generate “quick code” and optimization level vs.memory usage.</p><h3>Luis Manuel Palomo on Twitter</h3><p>Talking about web standards with @mhartington #JSCampBCN</p><h4><a href="https://speakerdeck.com/mhartington/rise-above-the-framework-jscamp-2018"><strong>RISE ABOVE THE FRAMEWORK</strong></a><strong><br></strong>A talk by <a href="https://jscamp.tech/speakers/mike-hartington/">Mike Hartington</a></h4><p><a href="https://jscamp.tech/speakers/mike-hartington/">Mike Hartington</a> is part of Ionic core team, Mike helps developers while they are building their apps and also frequently speaks and writes about Ionic. In his spare time, he’s a hybrid app maker, occasional musician, and craft beer lover.</p><blockquote><em>“JavaScript has evolved itself from a single MVC-application with Backbone, styled with global CSS and written in ES5 syntax back in 2011 to an intensive web of multiple frameworks and configuration files as we know it now, in 2018</em>” <br>- <a href="https://jscamp.tech/speakers/mike-hartington/">Mike Hartington</a>(Developer Advocate at Ionic).</blockquote><p>Mike helps developers while they are building their apps.</p><p>There is no doubt, that <strong>JavaScript is moving fast forward,</strong> many new build tools and new features are added on a daily base. Frameworks like Angular, React and Vue are all different frameworks, with different components (chunks of code) and different APIs. Yet, as <strong>developers are experiencing the “build tools fatigue</strong>”, it is time to take a step back to be able to think and <strong>rise above the framework.</strong></p><p>While in the near past, developers still used scripting and framework-based components, Hartington sees <em>building models and custom elements, with a standard-based APIs, reusable native components and lack of any framework and config files as the near future of JavaScript. </em><strong>Web standards help building better apps with less code. </strong>The less code needed to be sent to the browser, the better and faster the application will run.</p><h4><strong>THE FUTURE OF JAVASCRIPT AND BEYOND</strong></h4><blockquote><em>`More is not better or worst than less, it is just different` </em>-Peter van Roy</blockquote><h3>Dhilip on Twitter</h3><p>Opening keynote.. 157 slides in an hour.. &quot;Blazingly fast, prevents distraction and guarantees knowledge gaining&quot; #JSCampBCN @jscamptech @ag_dubs</p><h4><a href="https://ashleygwilliams.github.io/a-tale-of-two-asyncs/#124"><strong>A TALE OF TWO ASYNC LANGUAGES</strong></a></h4><h4>A talk by <a href="https://jscamp.tech/speakers/ashley-williams/">Ashley Williams</a></h4><p>The first JavaScript expert speaker is web passionate <a href="https://jscamp.tech/speakers/ashley-williams/">Ashley Williams</a> (Brooklyn/NYC, USA). As individual membership Director of <a href="https://nodejs.org/en/">Node.js (JS)</a>,Integer32 engineer contracted by Mozilla, and member of the Rust Core team, she leads the Community Team on the new Programming language <a href="https://www.rust-lang.org/en-US/">Rust</a>. Ashley is as vivid tech teacher, known for influencing the growth of JavaScript. Coming from a non-technical background, this badass woman, is doing a great job. The JavaScript expert explores the two async Javascript libraries Node.js and Rust. Unlike the other speakers, she holds the vision that <strong>JavaScript might not be “t<em>he best language out there</em></strong>”, for it has serious limitations.</p><p>Particularly interested in <strong>genealogical analysis</strong>, she questions herself</p><blockquote>“<em>what is the best first programming language?, what are the best tools for the job? And what do programming languages want to reach?”</em></blockquote><p>According to her, this must always be at the heart of any project, as programming languages are part of a cultural ecosystem itself, that needs to be taken into account, when looking at programming paradigms solving multiple problems for society. According to her, <strong>JavaScript has far too long been taken for granted.</strong></p><p>Originally created as<a href="http://www.ecma-international.org/"> ECMAScript syntax</a>, a standardized specification of a scripting language developed by <a href="https://en.wikipedia.org/wiki/Brendan_Eich">Brendan Eich</a> of <a href="https://en.wikipedia.org/wiki/Netscape_Communications_Corporation">Netscape</a>, to “<strong>serve easy to use scripting language</strong>”, JavaScript has instead become a <em>“very complex and overwhelming language with many add-on libraries, that is hard to maintain. It has epic problems to scale, a serious information overload and definitely a lack of qualified managers.</em>”</p><p>Ashley Williams is a JavaScript lover and expert, yet she strives to overcome the shortcomings of JS to bring the language back to where it belongs: the people. Therefore she is the leading force in Rust, that developed as result of Node.js, respond to <strong>the four main problems based on the current JavaScript ecosystem</strong>:</p><ol><li><strong>Lack of Vision</strong> in JS and NodeJS.</li><li><strong>Lack of Users: </strong>Add users back to the center to create a great product.</li><li><strong>Lack of Diversity:</strong> Get more people involved and a more diverse feedback.</li><li><strong>Lack of Consensus: </strong>How to reach consensus on a Large scale.</li></ol><p><strong>Speed, Safety and Productivity</strong> are the main features of the open source project RUST. These features should make improgramable programs programmable again. So that beginners, intermediate and advanced programmers can work hand-in-hand solving complex world based problems.</p><h4><strong>BUILDING A PLATFORM: WEBPACK AND THE FUTURE<br>A talk by </strong><a href="https://jscamp.tech/speakers/sean-larkin/">Sean Larkin</a></h4><h3>Elisabeth Engel on Twitter</h3><p>Even more #DeveloperUX by @TheLarkInn talking about #webpack at #JsCampBCN2018</p><blockquote><em>“At Microsoft we use the same tools, we write the same code. Therefore webpack is open source, as it is not only meant to solve issues for microsoft, but for coders as well”<br>-</em>Sean Larkin</blockquote><p>If JavaScript is not the solution, then what is? According to <a href="https://jscamp.tech/speakers/sean-larkin/">Sean Larkin</a>, Technical Manager at Microsoft, “<strong><em>JavaScript is currently experiencing a Renaissance,</em></strong><em> yet the future of programming is platform based</em>”. He proudly presents “<a href="https://medium.com/webpack/webpack-4-released-today-6cdb994702d4">Webpack 4 Legato</a>”, the first major version, sponsored by Trivago. <a href="https://webpack.js.org/">Webpack 4</a> is seen as the most groundbreaking set of changes for the future of webpack and the Javascript ecosystem.</p><p>The improved system puts developers first: the entire plugin system has been refactored. As a result, the platform is 98 percent faster. No configuration is needed, it comes with smaller and faster builds. The kernel of front-end framework works not only at microsoft, but everywhere, even with frameworks like <a href="https://angular.io/">Angular</a>, <a href="https://reactjs.org/">React </a>and <a href="https://vuejs.org/">Vue</a>.</p><p>“<strong><em>The future of programming is module based and platform build.</em></strong><em> Node.js and package json files are no longer needed. We can build on any Javascript as a platform and diagnostic directly inside the code editor. With a new JS library as Vue.js and the Webpack platform, we can develop, diagnose and redact all from one place</em>.”</p><p>To try: `yarn add webpack webpack.cli — dev` OR `npm add webpack webpack.cli — sav dev`</p><h3><strong>LESSONS LEARNED</strong></h3><p>After this two intensive days of amazing talks and speakers, we went home with a couple of conclusions and a bunch to things to figure out.</p><p>Being still on the early steps of becoming a front end developer, we got the chance to grasp some ideas and visions of the speakers.</p><p>We learned that Javascript had an evolution of small baby steps, with every version being released adding more features in order to make the language able to perform low level tasks like other languages out there. It has also became the ‘lingua franca’ of the web and it is thought as the most influential technology of our time in software engineering, even though it has serious limitations: lack of vision of where it is headed, users, diversity and consensus.</p><p>Other highlights and points of interest we found along the talks were:</p><ul><li>JavaScript has far too long too been taken for granted.</li><li>JavaScript is currently experiencing a Renaissance.</li><li>JavaScript is moving fast forward.</li><li>JavaScript developers are experiencing the “build tools fatigue”</li><li>Time has come to rise above the JavaScript frameworks.</li><li>JavaScript engines have much in common among different web browsers, yet they differ in their optimization tiers: “generate code quickly”, or generate “quick code”.</li><li>Time has come to redesign the web: to have not only online first apps available, but also offline web apps.</li><li>Time has come to focus on Human JavaScript.</li><li>The current JavaScript ecosystem experiences four major shortcomings: 1) lack of vision, 2) lack of users, 3) lack of diversity and 4) lack of consensus.</li><li>Web standards help build better apps with less code.</li></ul><p>As per the future of Javascript, the speakers made a strong point that the future is module based and platform build. The platforms allow to develop, diagnose and redact all from one place. Building models and customer element with standard-based APIS, reusable native components and lack of framework and config files are seen as the near future of JavaScript.</p><p>And also JavaScript, will probably never be completely replaced, yet the future of JavaScript is based on Open Web Technology with HTML5, CSS3 and PWA, taking into account Accessibility issues and build with open collaboration of the community.</p><h3>JSCamp #JSCampBCN on Twitter</h3><p>THANK YOU to our attendees, MC, speakers, sponsors and volunteers for coming together and making it unique! See you all at JSCamp 2019! #JSCampBCN</p><h4><strong>WHAT’S NEXT</strong></h4><h3>JSCamp #JSCampBCN on Twitter</h3><p>JSCamp 2018 we did it! Thank you ALL for making possible a great event 💜 Don&#39;t forget to tweet us your highlight @ #JSCampBCN After the massive success, we&#39;re excited to announce that the date of JSCamp&#39;19 has been set! Barcelona, 16-19 July #JavaScript https://t.co/2467fU8amV</p><h3>JSCAMP 2019!</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZIjgjhXmpmQ%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZIjgjhXmpmQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZIjgjhXmpmQ%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/3364d7b67ca17ba6a3ed02084785e34f/href">https://medium.com/media/3364d7b67ca17ba6a3ed02084785e34f/href</a></iframe><h4><strong>WORD OF THANKS</strong></h4><ul><li>Thanks <a href="https://twitter.com/davidpich/">David Pich</a>, sponsoring partners <a href="https://www.marfeel.com/">Marfeel</a>, <a href="https://www.npmjs.com/">NPM </a>and <a href="https://www.mozilla.org/en-US/">Mozilla</a> and JSCampBCN 2018 volunteers for such an welcoming, inclusive and diverse JavaScript conference.</li><li>Thanks to <a href="http://railsgirlssummerofcode.org/">Rails Girls Summer of Code</a> who work really hard to give opportunities to women and non-binary people in tech and gave us the opportunity to join this inspiring Tech conference.</li><li>Thanks to all great <a href="https://jscamp.tech/speakers/">speakers </a>and attending developers, we have met during #JSCampBCN for having such a great time together.</li></ul><p><strong>For more info on the speakers visit: </strong><a href="https://jscamp.tech/speakers/">https://jscamp.tech/speakers/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=713dfe6fdf0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Two weeks of Rails Girls Summer of Code]]></title>
            <link>https://medium.com/@dvteam/two-weeks-of-rails-girls-summer-of-code-e2f19182b63e?source=rss-bb7dcbdbb6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2f19182b63e</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[living-style-guide]]></category>
            <category><![CDATA[rgsoc]]></category>
            <category><![CDATA[summer-of-code]]></category>
            <dc:creator><![CDATA[DV Team]]></dc:creator>
            <pubDate>Tue, 17 Jul 2018 10:20:52 GMT</pubDate>
            <atom:updated>2018-07-17T10:43:19.441Z</atom:updated>
            <content:encoded><![CDATA[<h4>By <a href="https://medium.com/u/a8269b9b7b42">Diana Vile</a> with collaboration of <a href="http://www.twitter.com/artnerdnet">Violeta</a></h4><p>We, Violeta and Diana Vilé, are involved in the <a href="https://railsgirlssummerofcode.org/">Rails Girls Summer of Code scholarship</a> as the DV Team since 2nd of July. We met each other in November 2017 during the <a href="https://www.udacity.com/course/front-end-web-developer-nanodegree--nd001">Udacity Front-end Web Developer (FEND) Nanodegree</a>, for which we both received a full Google scholarship. This article shares our experiences and learnings of pair coding during the Rails Girls Summer of Code scholarship (july 2th- september 30th 2018).</p><h3>LivingStyleGuide on Twitter</h3><p>🎊Congrats and welcome aboard to our @RailsGirlsSoC 2018 team, DV Team! 🎊 👉🏾Find out more about the team, and how you can help Rails Girls Summer of Code support more teams next year on our blog: https://t.co/NzZbf5clUB</p><h3>EXPERIENCE: How to do pair programming in remote</h3><p>Pure excitement, is what we felt <a href="https://twitter.com/LSGorg/status/998830730405990400">when we got accepted</a> for the Rails Girls Summer of Code scholarship. We could not wait to start pair coding on the Open Source project <a href="https://livingstyleguide.org/">“Living Style Guide”</a> together. We felt very privileged to be part of the Rails Girls Summer of Code community. Knowing it would become a busy summer, it took relatively short to realise we needed to prepare ourselves.</p><h3>Getting ready</h3><p>Even before the Rails Girls Summer of Code experience started, life have been hectic, combining both a full-time job and complete opposite work schedules. Yet we managed to meet each other. In the days before the start:</p><ol><li>We met for a strategy session to <a href="https://twitter.com/artnerdnet/status/1012799490456158209">Plan and Research for @RailsGirlsSoC</a></li></ol><h3>ArtNerd on Twitter</h3><p>Doing some planning and research for @RailsGirlsSoC ❤️ @LSGorg is our selected open source project for the scholarship 🙌🏻 #code #womenintech #ruby #javascript #womenwhocode</p><p>2) Read the <a href="https://github.com/dianavile/RgSocDVTeam/blob/master/RGSoC%202018_%20Student%20onboarding%20guide.pdf">@RailsGirlsSoC guidelines</a>:</p><h3>ArtNerd on Twitter</h3><p>Reading the @RailsGirlsSoC guidelines 🤭🎉 #rgsoc #summerofcode @LSGorg</p><p>3) And attended a <a href="https://twitter.com/artnerdnet/status/1012799490456158209">Scrum Workshop</a> giving by our Coach @cristina_verdi</p><h3>ArtNerd on Twitter</h3><p>Awesome #scrum workshop today by @cristina_verdi 🙆🏻‍♀️ thanks a lot! It was really fun! #scrum #agile #womenintech #developer</p><h3>First day</h3><p>The first day, we prepared ourselves looking into the Code and attending the <a href="https://railsgirlssummerofcode.org/blog/2018-06-28-lets-get-rgsoc-started">@RailsGirlsSoC Kick-Off event</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42r3gEMkESGctE-VcimGsQ.png" /></figure><h3>Official RGSoC moments on twitter</h3><h3>RGSoC 2018 Kick-off</h3><p>The first days of RGSoC 2018! 🎉</p><p><strong>The next two weeks, we logged our progress in the </strong><a href="https://teams.railsgirlssummerofcode.org/"><strong>daily log</strong></a><strong>.</strong></p><h3>ArtNerd on Twitter</h3><p>Time to work!!! *Opens terminal* 30 minutes later on my browser... https://t.co/p3v65zuWiO ... #adhd #easilydistracted #codenewbie #100daysofcode #rgsoc #dvteam</p><h3>Struggling to find a way</h3><p>Shortly afterwards, we realized one thing: starting to code and do pair programming in remote isn’t easy:</p><ul><li>We didn´t understand the code. Not even a tiny bit.</li><li>We realised we <strong>need to learn a lot.</strong></li><li>We noticed that we need to review many things we learned and clarify concepts</li><li>We <a href="https://twitter.com/artnerdnet/status/1015567892081979393">struggled to focus after a long working day</a></li><li>Our <strong>work schedules and responsibilities are completely the opposite</strong>. While Diana has a daughter and can study at work during the week, Violeta is completely alone and far away from her family and can’t do anything until she’s home or during the weekends.</li><li>We need to <strong>find a way to work together</strong>. We realised we both have a <strong>different </strong><a href="https://en.wikipedia.org/wiki/Learning_styles"><strong>learning style</strong></a>. While Violeta is good at learning by reading, researching and using logic, Diana learns by writing, discussing ideas and needs to work more with people in order to move forward.</li></ul><h3>Pair programming</h3><p>We decided to let our coaches be the bridge between our tight schedules and different learning styles. While, Violeta’s attended her<strong> </strong><a href="https://twitter.com/artnerdnet/status/1015883042462818305"><strong>first tech conference</strong></a><strong>, </strong>Diana sticked with the basics learning<strong> </strong><a href="https://github.com/dianavile/RgSocDVTeam/blob/master/General%20Workflow%20Git%2C%20Version%20Control%20and%20Github.md"><strong>Git, Version Control and Github</strong></a>. While Diana is still catching up with Violeta, luckily we could communicate openly about it.</p><h3>ArtNerd on Twitter</h3><p>Just posted my experience during my @RailsGirlsSoC at my first tech conference #addc ☕️ my highlights @johnsundell and Victor Persson&#39;s talks. Check it out ! 👇🏻 https://t.co/nM63cd4XdH #codenewbie #rgsoc #womenwhocode @WWCodeBarcelona #womenintech</p><p><strong>Pair programming, especially almost fully remote, is hard</strong>, but even then still you can <a href="https://twitter.com/artnerdnet/status/1017905655422881793">enjoy working even Friday night</a>.</p><h3>ArtNerd on Twitter</h3><p>Friday night, I&#39;m up to date with Netflix and HBO, bf is busy, walked the dog, read for an hour... So... #code? #rgsoc #frontend #javascript</p><h3>Lessons Learned</h3><ul><li><strong>Preparation is key</strong>, but don’t stick in it too long.</li><li>Try to <strong>define tasks for the week</strong>, don’t plan too much ahead and <strong>stay on point</strong>.</li><li>Learn <strong>a bit every day</strong>, even if you are too tired read something related to avoid feeling you are not achieving your goals.</li><li><strong>Learn</strong> as much as you can. <strong>Start working and keep going.</strong></li><li>Coding is everything except being “a loner”. <strong>To code, you need to communicate.</strong> Especially in remote settings,<strong> communication is key.</strong></li><li>Pair programming is challenging, coding is hard, communication in remote is prone to misunderstanding. Despite this, <strong>attending the Rails Girls Summer of Code is really rewarding.</strong></li><li><strong>No more playing around</strong>, we are really preparing ourselves to become professional front-end- developers.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2f19182b63e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ADDC: My first Tech Conference]]></title>
            <link>https://medium.com/@dvteam/rgsoc-addc-99a42d843066?source=rss-bb7dcbdbb6ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/99a42d843066</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[summer-of-code]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[women-who-code]]></category>
            <dc:creator><![CDATA[DV Team]]></dc:creator>
            <pubDate>Sun, 08 Jul 2018 08:52:57 GMT</pubDate>
            <atom:updated>2018-07-08T09:15:51.671Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Violeta</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*wq4xPQQJbOJnFQ2q-IZV_g.jpeg" /></figure><p>I found out about <a href="https://addconf.com/2018/"><strong>ADDC</strong></a><strong> </strong>a month ago through <a href="https://www.womenwhocode.com/barcelona">Women Who Code Barcelona</a> and I applied for a ticket (they have <a href="https://twitter.com/WWCodeBarcelona">ticket giveaways</a> for women so check it out!). I am currently working as a UI designer for a company that provides services to high end hotels while I transition to web development so I thought it would be a great opportunity to further explore the mobile development/design world.</p><p>Coming from the art world, I know these events are full of opportunities to connect with more experienced people that are willing to share their ideas and knowledge and it truly met my expectations. I had an awesome experience and left with tons of new stuff to think and research about!</p><p>Here are the two highlights of the week:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AfqRt59gOFXN-mu3XvrgwQ.jpeg" /></figure><h3>Prototype Everything by <a href="https://twitter.com/johnsundell">John Sundell</a></h3><blockquote>About: John builds apps, games &amp; developer tools. He also makes Swift by Sundell, which is a weekly blog &amp; podcast about Swift development. He has worked for companies like Volvo &amp; Spotify, and is currently an iOS freelancer working with a Norwegian startup called Motimate. He’s the creator of several open source projects including Unbox, SwiftPlate, Marathon &amp; Imagine Engine<em> ¹</em></blockquote><h4>Why and how to Prototype?</h4><p>Prototyping is key in order to test out an idea or a new feature without doing much design or code, letting us play around without pressures and being able to throw away what we did in order to move on.</p><p>In his talk, John Sundell sets the main goal: to get to a MVP (Minimal Viable Prototype), the most basic and useful design or code to shape what you want to achieve in a limited period of time and detail.</p><p>On the developers end, tools like pseudo code, playgrounds, framer and React Native can get the work done, as Sketch and After Effects can for designers.</p><p>But you can also prototype simply by using mind-mapping, drawing by hand or HTML. Using plain HTML can be a great way to test navigation and user flow by creating trees and giving your potential users small tasks to perform and see how it goes.</p><h3>Luis Ascorbe on Twitter</h3><p>@johnsundell bringing @_inside to the stage 🍻 #ADDConf</p><h4>Prototype Pattern: Modularizing</h4><p>Another great point that Sundell explored in his talk was about modularizing your code in order to minimize the time you spend coding (when you build or when you need to update something). When doing so, you rethink the way you build your app and what prefixes you are using. An example given by him was a simple user card that just by renaming the parts from user related to something more general gave him the chance to reutilize this piece in another screen of the app (see above linked tweet) and also making it easier to change content types.</p><p>Find different ways of prototyping patterns, look at prefixes to find matches. So for example if you find four classes that start with ‘User’, you can probably create a user framework or user kit that you can reuse. You can also identify code that is performing a single dedicated task such as a caching or image loading code that can also perform in isolation. If you have this you can probably reuse it in the same or other project. Sundell also advices to avoid using global states, moving them out of your classes and code, and to define clear APIs and interfaces to have more dynamic code to work with.</p><h4>Prototype Everything</h4><p>At the end, prototyping is about saving time and work that should be invested later when your product is truly defined. Prototyping allows us to:</p><ul><li>Explore new ideas and see where they go.</li><li>Play with code or design without pressure and being able to throw it away when you are done.</li><li>Evaluate and test what you are doing.</li><li>Find the best way of doing something.</li><li>Realize if you need to add, remove or change anything about it (or start from scratch).</li><li>Have a tangible concept to discuss with your team and clients.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWaaq-qM3FHoN18f8FjXfg.jpeg" /></figure><h3>Remote Control by <a href="https://www.linkedin.com/in/viktor-persson-44622418">Viktor Persson</a></h3><blockquote>About: Previously lead designer for Googles Material design. Currently founder of the design studio [graf-ik] based in Stockholm &amp; New York.<em> ²</em></blockquote><p>I found this talk very interesting as working remotely is part of our day to day work in Rails Girls Summer of Code and it’s something I’m looking forward to do as a developer in the future. Persson’s talk was a good overview of a remote workflow and the things he realized along the way.</p><h3>ADDC - App Design &amp; Development Conference on Twitter</h3><p>Viktor Persson talking about overworking. #addconf</p><h4>Know your business</h4><p>After going through a bad financial moment, the speaker realized that he needed to figure out his client flow and how to manage his income. What was a need to accept all clients to survive became a work overload that taught him three important lessons:</p><ul><li>How and when to say ‘no’</li><li>The importance of knowing his sales pipeline</li><li>To always have a buffer of cash (one or two months)</li></ul><p>Regarding the first point, I found the following advice very clever and on point. When deciding on accepting or not a client, ask yourself two questions:</p><ol><li>Do I need this to cover my costs?</li><li>Would I tell people about this?</li></ol><p>The first question will give you the chance to realize if you need the job or if you are just being greedy. The second, will help you not to lose a valuable client that you can showcase in your portfolio to attract more potential clients, even if the money is not that good.</p><h3>ADDC - App Design &amp; Development Conference on Twitter</h3><p>Some guidelines for healthy remote working. #addconf</p><h4>Tips for Working Remotely</h4><p>Working remotely can be really good to optimize your schedule and to achieve a great life-work balance if you do it right. For that, Persson advices to create your own routine, as hard as it is, and to include in that routine the time to communicate with your team. To improve this, remember to send things unrelated to work from time to time, try to become a better writer so you avoid misunderstandings, do weekly reports and avoid zero time overlaps. On the last point, have always at least 3 hours of time overlap so you can work at the same time and solve issues that need short time replies.</p><p>And finally, the speaker reminds us that, if we are feeling lonely and crave some human interaction, working remotely means that you can move your office to your favorite cafe or rent a coworking space and meet some cool people while you get your work done!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*ZmmOXd4i1ObPwVTEgfrxCA.jpeg" /></figure><p>These were the two talks that I found more relevant to the point where I am in my career right now but all the talks were really enlightening and interesting. I encourage the readers to check the awesome people that spoke in ADDC at <a href="https://addconf.com/2018/schedule/">the conference website</a> and check out their twitter accounts.</p><p>Again, a shout out for the ladies at <a href="https://www.womenwhocode.com/barcelona">Women Who Code Barcelona</a> and the great team at <a href="http://railsgirlssummerofcode.org/">Rails Girls Summer of Code</a> who work really hard to give opportunities to women and non-binary people in tech.</p><p>See you next year ADDC!</p><p>Written by <a href="http://www.twitter.com/artnerdnet">Violeta</a></p><blockquote><em>¹</em> <a href="https://addconf.com/2018/speakers/john/">https://addconf.com/2018/speakers/john/</a></blockquote><blockquote><em>²</em> <a href="https://addconf.com/2018/speakers/viktor/">https://addconf.com/2018/speakers/viktor/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99a42d843066" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>