<?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 Jonathan Ramirez on Medium]]></title>
        <description><![CDATA[Stories by Jonathan Ramirez on Medium]]></description>
        <link>https://medium.com/@jonathanramirez_78463?source=rss-6f56caeb025a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZYe9v-w6XhnxCR4b.</url>
            <title>Stories by Jonathan Ramirez on Medium</title>
            <link>https://medium.com/@jonathanramirez_78463?source=rss-6f56caeb025a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:29:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonathanramirez_78463/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[Design Systems: React + Storybook]]></title>
            <link>https://medium.com/leafgrowio-engineering/design-systems-react-storybook-635db90aa812?source=rss-6f56caeb025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/635db90aa812</guid>
            <category><![CDATA[storybook]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Jonathan Ramirez]]></dc:creator>
            <pubDate>Fri, 31 May 2019 16:23:07 GMT</pubDate>
            <atom:updated>2019-05-31T20:36:57.472Z</atom:updated>
            <content:encoded><![CDATA[<h4>an investment that pays in velocity and productivity</h4><p>A Design System is a collection of reusable components that can be used to build applications. In this article, I am going to explain how a Design System helps us to plan, develop, test and deliver new features faster at <a href="https://www.leafgrow.io/">Leaf Grow</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fQI-RLlCHmvvYTBT0pjiMQ.jpeg" /><figcaption>A preview of what our design system looks like</figcaption></figure><p>Technology products always mutate. They can become huge or they can die to delegate resources to another project. Companies always need to decide how many times they will invest on a solid base at the beginning of the project. Maybe they have a small team and/or budget to build a functional prototype and they can’t invest in a<strong> </strong>scalable<strong> </strong>architecture, with reusable pieces and automated testing from the very beginning.</p><p>But investing time on a Design System at the beginning of the project is a time saver, no matter if the initial project will need to lag behind or change completely during the process. If the company has a defined brand already, creating components following brand principles will allow them to reuse these components on any project.</p><p>The best time for building a Design System is at the beginning of the project, but it doesn’t mean that it can be added later during the project development.</p><p>At Leaf we had a mix of the two options above. First, we started building the project; we created a components folder inside of our<strong> </strong>project repo. But then we found that other projects also needed some of the components and it was not efficient to duplicate them across different projects. So we decided to make an external project<strong> </strong>and publish it as a <a href="https://docs.npmjs.com/creating-and-publishing-private-packages">private npm package</a>, that way we had just one repository for components to maintain and we could access the library from any of our projects<strong>.</strong></p><p>To be able to preview and test these components project we are using Storybook, which is a useful React environment that allows you to browse and play with all of the pieces<strong> </strong>on your project<strong>.</strong></p><p>Here are some of the advantages we experienced by creating a separate project just for components:</p><h3>1. We have a place where the whole team can learn which components we already have</h3><p>When companies don’t have a components repository they tend to duplicate work because they end up developing<strong> </strong>components that somebody else already did. Or sometimes they create two similar components that could be merged into one just by adding a few changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1u3MX85nm3tzP91rQLWZIQ.jpeg" /></figure><h3>2. Develop new features based on existing components</h3><p>Each component should be very simple and perform the minimum amount of actions, these components can be combined to perform more complex requirements. Having the product owner and the UX team planning new features based on these existing components saves time. Otherwise, they would come up with a whole new list of components every time they sit to plan new features. Sometimes, there will be new components needed but this should be the exception, not the rule.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fo4t9DV3uvF0fAaQJ6mljQ.jpeg" /></figure><h3>3. Training new developers</h3><p>New members of the team should go to the components project before they start adding any code to the project, this way they know what components already exist and they don’t duplicate, as mentioned in point 1. Here’s where Storybook becomes very helpful, since we can easily extract the component code using snippets in there. It also allows us to play with the component parameters, to test different scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hBFcd2IT8UmDTxWidYyvKw.jpeg" /></figure><h3>4. Quality Assurance approval</h3><p>Having the QA team reviewing all the components before they get instanced on the project reduces the number of bugs on the final product. There are some <a href="https://storybook.js.org/docs/testing/automated-visual-testing/">automated testing</a> tools that have Storybook integration. Here you can even use automated visual testing tools that take screenshots of your components and warn you every time there’s a visual change on the library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mbcPqG-Tz-UJaRcghq77eQ.png" /></figure><h3>5. Components Dev owners</h3><p>Having everybody on the team building components can be useful for training purposes, but on a daily basis, it ‘s more efficient to have fewer developers creating and maintaining the library. This way they can follow the same process and standard, instead of having different approaches and code organisation on every component<strong>. </strong>It’s useful to name someone the owner of the library that it’s in charge or aware of every change, decision and coding standards on the components project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rQsZfCArBVEEfZp3-egqhw.jpeg" /></figure><h3>Conclusion</h3><p>Time is money and Design Systems save time. It’s hard to pitch the idea to Management or Finance that putting effort on reusable/extendable code will always pay back. But with the right tools and processes, they will find that spending time on a Design System was the right choice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=635db90aa812" width="1" height="1" alt=""><hr><p><a href="https://medium.com/leafgrowio-engineering/design-systems-react-storybook-635db90aa812">Design Systems: React + Storybook</a> was originally published in <a href="https://medium.com/leafgrowio-engineering">Engineering @ Leaf</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leyes Abiertas]]></title>
            <link>https://medium.com/@jonathanramirez_78463/leyes-abiertas-17ef3101ee14?source=rss-6f56caeb025a------2</link>
            <guid isPermaLink="false">https://medium.com/p/17ef3101ee14</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[law]]></category>
            <dc:creator><![CDATA[Jonathan Ramirez]]></dc:creator>
            <pubDate>Sun, 20 Aug 2017 04:50:14 GMT</pubDate>
            <atom:updated>2017-08-20T05:04:10.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fs4phefbP4u8drvpg1x2VA.jpeg" /></figure><p>El proceso de escribir una ley podría ser parecido al mecanismo que utilizan las organizaciones de Software libre para desarrollar y mantener sus productos. Donde existe un repositorio de código principal y muchas personas colaboran simultáneamente, mientras un organismo regulador incluye mejoras en el código principal, después de un proceso de revisión y aprobación.</p><p>Tomemos por ejemplo la Ley Reguladora del Servicio Público de Transporte Remunerado de Personas en Vehículos en Costa Rica. Sabemos que es una ley desactualizada, no sabemos por qué el gobierno simplemente decide apegarse a ella, aún sabiendo que está retrasando el desarrollo del país, protegiendo un servicio que la gente ya no quiere usar.</p><p>La ley actual es la fuente principal, a partir de ahí cada interesado genera una copia personal llamada ‘rama’ donde ingresa sus cambios. Y cada cambio se va revisando e integrando a la fuente principal, si el comité regulador considera que es un buen aporte. Se puede contar con colaboración de especialistas, incluso colaboradores internacionales que trabajaron en resolver el mismo problema en su país.</p><p>El comité regulador puede estar conformado por personas de diferentes partidos políticos, neutrales y sin intereses que puedan beneficiar a algún grupo en específico.</p><p>Sabemos que el gobierno puede simplemente ignorar el contenido de estos documentos, pero con presión de medios y apoyo de grupos claves, se puede hacer escuchar la voz de personas que sólo buscan aportar mejoras para el país y no beneficiar a ciertos grupos o partidos políticos.</p><p>Existen muchas plataformas gratuitas para generar documentos colaborativos, incluso se pueden utilizar <a href="http://github.com/">Github</a>, <a href="http://bitbucket.org/">Bitbucket</a>, entre otros, que fueron creados para código, pero funcionan perfectamente para documentos de texto simple.</p><p>Esta es una iniciativa que ya se ha propuesto y se ha utilizado en otros países, acá van algunos ejemplos:</p><p><a href="http://www.linuxinsider.com/story/58298.html">http://www.linuxinsider.com/story/58298.html</a></p><p><a href="https://opensource.com/government/12/9/creating-legislation-open-source-way">https://opensource.com/government/12/9/creating-legislation-open-source-way</a></p><p><a href="https://opengovfoundation.org/">https://opengovfoundation.org/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17ef3101ee14" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>