<?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[Crafting products with joy - Medium]]></title>
        <description><![CDATA[The Lemontech Engineering team blog - Medium]]></description>
        <link>https://medium.com/5rabbits-engineering?source=rss----f3d442fc6737---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Crafting products with joy - Medium</title>
            <link>https://medium.com/5rabbits-engineering?source=rss----f3d442fc6737---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:09:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/5rabbits-engineering" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Cazando bots en Twitter]]></title>
            <link>https://medium.com/5rabbits-engineering/cazando-bots-en-twitter-f173e2315185?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/f173e2315185</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[venezuela]]></category>
            <dc:creator><![CDATA[Javier Segovia]]></dc:creator>
            <pubDate>Wed, 16 Aug 2017 16:06:09 GMT</pubDate>
            <atom:updated>2017-08-16T16:06:08.573Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagínense vivir en un país en dictadura, donde el dia anterior había sido el <strong>Dia del Trabajador</strong> y el salario mínimo mensual no llega a 50 USD, paralelamente habían<a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=2&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwjuzN-5wdLTAhWBipAKHbLiCEAQqUMIKjAB&amp;url=http%3A%2F%2Fwww.elnuevoherald.com%2Fnoticias%2Fmundo%2Famerica-latina%2Fvenezuela-es%2Farticle147825589.html&amp;usg=AFQjCNGPwgH2m6eH_rCQyci0OcLHop8qZA&amp;sig2=dNafQ8b9hCpHrLBzPl9T4w"> disturbios y manifestaciones</a> en todo el país (porque el país sufre<a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=8&amp;ved=0ahUKEwjW5vjGwdLTAhVEQ5AKHcahA60QFghKMAc&amp;url=http%3A%2F%2Fwww.eltiempo.com%2Fnoticias%2Fcrisis-en-venezuela&amp;usg=AFQjCNGffjGkccUKANNdLkaG_Ae8jw3MSA&amp;sig2=VHisGCalKYeFI2FK1fOI9Q&amp;cad=rja"> crisis económicas, sociales, de salud, etc.</a>) siendo reprimidas de forma violenta por el poder que juro proteger al ciudadano, un dia terrible, pues ese es mi país de origen, mi amada Venezuela.</p><p>Para mejorar la situación, el presidente convoca a una <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=6&amp;cad=rja&amp;uact=8&amp;ved=0ahUKEwi8o4jvwdLTAhVEQ5AKHcahA60QFghCMAU&amp;url=http%3A%2F%2Fwww.el-nacional.com%2Fnoticias%2Fgobierno%2Fmaduro-convoco-una-constituyente-comunal_179943&amp;usg=AFQjCNHBvlVf-h3shtusQ2SDmAipnTsXfw&amp;sig2=8GL5l9W82DffVG2yPzZyoA">“Constituyente Comunal”</a> el cual genera todo tipo de repudio nacional como internacional, aun así al siguiente dia en el <strong>twitter</strong> en medio de protestas y repudios la etiqueta pro-gobierno <strong>#AConstituyentePorLaPaz</strong> se mantiene posicionada, este fenómeno ocurre todos los días, al tener todos los medios censurados en el país, todo es color de rosa, pero muy contrario a la versión de las redes sociales, y al no poder censurarla, tratan de manipularla desvirtuando la opinión publica teniendo <strong>trending topics</strong> pro gobierno, para así tener una prueba de que el “pueblo” (a.k.a <strong>bots</strong>) están con ellos, este es un secreto a voces, muchas personas han demostrado con fotos, videos, etc como operan los bots, pero yo aproveche el fin de semana largo, y me dedique a demostrarlo como mejor lo se hacer, creando <strong>bots</strong> para detectar <strong>bots</strong> :D.</p><p>Cabe destacar que esto no es solamente para analizar los bots del gobierno, hay otros personajes que se dedican también a posicionar etiquetas de formas fraudulentas, sobre todo en las noches, así que parte de lo que mostrare no funcionara contra los <strong>bots</strong> <strong>“chavistas”</strong> porque usan estrategias distintas.</p><p>Así como este post lo hago en español, no lo haré tan técnico como mis posts anteriores, mostrare simplemente los resultados obtenidos al analizar para ser exacto <strong>15563 tweets</strong> con la etiqueta <strong>#AConstituyentePorLaPaz</strong></p><blockquote>Aquellos que son programadores, esto lo hice usando <a href="https://github.com/tweepy/tweepy">https://github.com/tweepy/tweepy,</a> y <a href="http://pandas.pydata.org/">http://pandas.pydata.org/</a>, luego subiré el código fuente</blockquote><p>Para detectar bots me base en varios criterios</p><ul><li>Tweets originales (no retweets) duplicados por distintas cuentas, es muy sospechoso que varias personas piensen igual (aunque eso es parte del modelo socialista, el pensamiento único :D)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OBwULKspP4a4WHVEN4Zsfw.png" /></figure><ul><li>Tweets falsos, como les mencione anteriormente, con los otros personajes que posicionan etiquetas, tienen varias cuentas que publican varios tweets con números o palabras aleatorias que no tienen que ver con la etiqueta.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yJ6Oi4pXE-oEZPK_bKp0UQ.png" /></figure><ul><li>Tweets masivos por el mismo usuario, hay varias cuentas que se dedican a twitter y a dar RT masivamente a los tweets con estas etiquetas</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*Ah8xA47gIFlwJzcuxMIHVw.png" /></figure><ul><li>Tweets provenientes de herramientas de automatización, algo que encontré muy resaltate, era como estos bots operaban mediante el uso de TweetDeck, Botize y IFTTT</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bRzCCeW2_XzUrl7MH_qug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KNOFHpZL1cQS5SRQdr_vSw.png" /></figure><ul><li>Y por ultimo, el mas descarado, RTs hecho masiva y simultáneamente, esta comparación la hice buscando todos los tweets hecho rt al mismo tiempo, es decir, con hora, minuto, segundos y mili-segundos!, sin dejar abierto la posibilidad de margen de error</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-ye_kS9ZSgE752Y-SpGwA.png" /></figure><p>En resumen, si bien despreciamos todas las pruebas excepto la ultima de los retweets simultáneos, representa mas del 15% de los tweets, por la densidad de los mismos, posicionan de manera eficaz las etiquetas, el resto de los tweets y menciones si se generan de manera orgánica, ya que algunos las respaldan y otros simplemente la condenan, de ambas formas mantienen la posición de la etiqueta, pero solo necesitaba el primer empujón, gracias al pueblo (bots)!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f173e2315185" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/cazando-bots-en-twitter-f173e2315185">Cazando bots en Twitter</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality assurance is no funky business]]></title>
            <link>https://medium.com/5rabbits-engineering/quality-assurance-is-no-funny-business-1633276e09e?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/1633276e09e</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[chefs]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[ideas]]></category>
            <dc:creator><![CDATA[jCi]]></dc:creator>
            <pubDate>Mon, 03 Apr 2017 13:19:43 GMT</pubDate>
            <atom:updated>2018-07-05T22:24:47.212Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Update (May 31, 2017) : I’ve been enlightened lately. After recovering from a hangover from crappy services and light-headed choices, I saw the sign. And it opened up my eyes. I saw. The Sign. Just kidding. I’m using Ansible now.</blockquote><p>Picture this. I was trained, most of the time, to be a system administrator. I studied to be a programmer, but I never catch on doing software. First program I wrote was some Visual Basic stuff for a veterinarian. Could not sell it so I gave it for free. Cool story, bro.</p><p>My first job ever was assembling computers. But I got to manage an old OLD AS FUCK Gateway computer with 32Mb of RAM running Windows NT3.1 with some obscure email software. I migrated that piece of garbage to Linux and that machine kept running Redhat 5.0 for two years until the power supply died. I took the machine home once it was retired and got for free a back injury. So I said “fuck it” and dropped it near a dumpster and forgot about it. Never reached home with that heavy thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/169/0*lycxbQ7p9jXzrS-T.jpg" /><figcaption>Shitty image for reference. I have no actual photo of that shit.</figcaption></figure><p>Just imagine if I had to create 20 of these behemoths to serve a web application at this time. I’d say <em>“kill it with fire”</em> and retire for good.</p><p>Now, almost 25 years after that episode (yes, I am that old), passed through many stages regarding computers. <strong>Linux</strong>? Yeah! <strong>Networking</strong>? Well, some of it. <strong>Cabling</strong>. And stuff.</p><p>Let’s jump to 2012. This involves my previous job. And thanks to an <strong>expired NDA</strong>, I can use at as example.</p><p>We (a team of sysapes) had to produce machines for consumption. All machines were cataloged as</p><ul><li><strong><em>vanilla</em></strong> : no patches, no updates, no major changes on the custom software infrastructure</li><li><strong><em>modified</em></strong> : some patches needed to be applied, some or none changes on the custom software</li><li><strong><em>fully modified</em></strong> or, as we called them at that time, <em>“</em><strong><em>lemons</em></strong><em>”</em> : all bleeding edge patches, new software versions, somethings that needed to be tested but dragons may be ahead...</li></ul><p>Better yet, for you developers on the audience:</p><ul><li><em>vanilla</em> is <strong>PRODUCTION</strong></li><li><em>modified</em> is <strong>DEV</strong></li><li><em>fully modified</em> is <strong>STAGING</strong></li></ul><p>So, the cycle says : <strong><em>vanilla</em></strong> goes eternally unchanged until some big changes are approved (not usual), <strong><em>modified</em></strong> are for testing of new features or lightweight modifications and <strong><em>fully modified</em></strong> are for testing not only new features, but new integrations with things that are untested and you may expect dragons and segmentation faults.</p><p>The process to install all those machines (for my previous job) had to be done <strong>MANUALLY</strong>. It was <em>a pain in the ass</em> (<strong>and I’m grateful that I haven’t got to do that again in the near future</strong>) but the process to ensure a minimum quality control was done by <strong>people</strong>. A manual checklist has to be filled (it was an Excel sheet…) but still, the quality control process was far from marginal.</p><p>Forget about automated assurance at that time. It was not authorized. Sad face. Emoticon.</p><p>I don’t want to smear my old job. So, let’s go to <strong><em>“select now() from dual;”</em></strong></p><p>Got exposed to AWS and OpsWorks on 2016. From my Sysadmin point of view, it was an offense!. This uses Chef. Based on Ruby. And for me (last year) anything more complex than a shell script was apeshit crazy.</p><p>So, Chef.</p><p>One thing about automated process is that processes are running and finishing with the same quality that the administrator wants them to. And the process can be repeated ad nauseam until the minimum quality required is achieved.</p><p>And it’s automated. Hell yeah.</p><p>So, your checklist can be automated. And if there are no errors (if you don’t put error traps) you, as an administrator, can make your job way easier. If you can achieve your job to deploy instances for the developers and everything is honky-dory, then you can play Battlefield or Urban Terror earlier on the day.</p><p>How does it work?</p><p>There are two methods:</p><ul><li>Chef server : put the recipes for the machines on a control center.</li><li>Chef solo : run the recipes manually.</li></ul><p>Chef server, BTW, is a paid product up to 20 machines. Chef solo is unlimited.</p><p>In the case of OpsWorks, machine provisioning is separated in three stages:</p><ul><li>Setup : put all you need here for the machine to be ready for deployment. Packages, program configurations, etc. Have to be done separated of the deployed element.</li><li>Configure : an intermediate state. Some requirements can be skipped on the Setup stage but can be added on the Configure state. This is fairly complicated to be explained on a single post.</li><li>Deploy : tasks that should run during the provision of the application. Compiling assets from the application, mainly. Other tasks are included too, but they depend if the application version changes due to versioning.</li></ul><p>For the Setup stage, let’s play with packages.</p><pre>package &quot;htop&quot;</pre><p>That will install the package “htop” (duh). This is semi straight-forward. Because of weird naming conventions between distributions, not all packages are called the same. For example, Ubuntu installs apache like this:</p><pre>package &quot;apache2&quot;</pre><p>but Redhat-CentOS-compatible distros it’s like this</p><pre>package &quot;httpd&quot;</pre><p>If you want to install the package, no matter what the distribution is , you can use some tricks being prepared from Chef:</p><pre>if platform?(&#39;debian&#39;, &#39;ubuntu&#39;)<br>  package &#39;apache2&#39; do<br>    retries 3<br>    retry_delay 5<br>  end<br>elsif platform?(&#39;centos&#39;, &#39;redhat&#39;, &#39;fedora&#39;, &#39;amazon&#39;)<br>  package &#39;httpd&#39; do<br>    retries 3<br>    retry_delay 5<br>  end</pre><p>This helps separating distros. Hell yeah.</p><p>If you have a checkbox for the installation of Apache, disregarding the distribution, you have one.</p><p>Now, let’s play with files.</p><p>Installing a file from the recipe has two conditions:</p><ul><li>verbatim file : no modifications</li><li>template file : requires modifications from provisioning</li></ul><p>In the first case (verbatim files), let’s install this file on /etc/myfiles.conf:</p><pre># this is a placeholder<br>config1 = one<br>config2 = two</pre><p>So, we need to create the “file” on recipename/files/default/myfiles.conf and then create the recipe that installs it:</p><pre>cookbook_file &quot;/etc/myfiles.conf&quot; do<br>  source &quot;myfiles.conf&quot;<br>  owner &quot;root&quot;<br>  group &quot;root&quot;<br>  mode &quot;0644&quot;<br>end</pre><p>Now if a file needs to be copied, then the file is copied. One additional check.</p><p>What about a file that needs some on-the-fly values? Such as the project name?</p><p>Create a file on templates/default/ called “myfiles.conf.erb” with the following:</p><pre># this is my configuration file<br>config1 = &lt;%= @value1 %&gt;<br>config2 = &lt;%= @value2 %&gt;</pre><p>Two variables, as they are shown. So the recipe to handle it should be like this:</p><pre>template &quot;/etc/myfiles.conf&quot; do<br>  source &quot;myfiles.conf.erb&quot;<br>  owner &quot;root&quot;<br>  group &quot;root&quot;<br>  mode &quot;0644&quot;<br>  variables ({<br>     value1: &#39;thisisvalue1&#39;,<br>     value2: &#39;thisisvalue2&#39;<br> })<br>end</pre><p>Once running this recipe, the /etc/myfiles.conf will be as this:</p><pre># this is my configuration file<br>config1 = thisisvalue1<br>config2 = thisisvalue2</pre><p>Templating is so awesome.</p><p>If you need to pass some variables, you need the attributes for the recipe.</p><p>Create the recipename/attributes directory on your Chef recipe. Add a default.rb file with the following (it’s comprehensive):</p><pre>default[&#39;myvar&#39;][&#39;value1&#39;] = &#39;thevalue1&#39;<br>default[&#39;myvar&#39;][&#39;value2&#39;] = &#39;value2&#39;</pre><p>and understand that passing variables should be like this (JSON):</p><pre>{<br>  &quot;myvar&quot; : {<br>    &quot;value1&quot; : &quot;thevalue1&quot;, <br>    &quot;value2&quot; : &quot;value2&quot;<br>}</pre><p>Unless you pass variables for Chef, the default values are assumed. Variables are a group of JSON packed values (in a personal note, a clustefuck on how to send data…). If you don’t pass data to this variables, the attributes/ directory will populate the variables that will be used. Generally, default.rb.</p><p>Just for sake of brevity, one thing I’ve used is including another recipe:</p><pre>include_recipe &quot;mycoookbook::myrecipe&quot;</pre><p>If I want to create a super-recipe-FTW, then I’ll go the obvious way:</p><pre>include_recipe &quot;mycookbook::setup&quot;<br>include_recipe &quot;mycookbook::configure&quot;<br>include_recipe &quot;mycookbook::installfiles&quot;<br>include_recipe &quot;mycookbook::holdupgrades&quot;<br>include_recipe &quot;mycookbook::fetchrepo&quot;<br>include_recipe &quot;mycookbook::generate_checklist&quot;</pre><p>Oh.</p><p>But that’s <em>vanilla</em> version. What about “modified” version?</p><pre>include_recipe &quot;mycookbook::setup&quot;<br>include_recipe &quot;mycookbook::configure&quot;<br>include_recipe &quot;mycookbook::update&quot;<br>include_recipe &quot;mycookbook::installfiles&quot;<br>include_recipe &quot;mycookbook::fetchrepo&quot;<br>include_recipe &quot;mycookbook::updaterepo&quot;<br>include_recipe &quot;mycookbook::generate_checklist&quot;</pre><p>Shit. What about the “lemon” version?</p><pre>include_recipe &quot;mycookbook::setup&quot;<br>include_recipe &quot;mycookbook::bleeding_edge_setup&quot;<br>include_recipe &quot;mycookbook::configure&quot;<br>include_recipe &quot;mycookbook::configure_bleeding_edge&quot;<br>include_recipe &quot;mycookbook::update_bleeding_edge&quot;<br>include_recipe &quot;mycookbook::installfiles_bleeding_edge&quot;<br>include_recipe &quot;mycookbook::fetchrepo_bleeding_edge&quot;<br>include_recipe &quot;mycookbook::updaterepo_bleedingedge&quot;<br>include_recipe &quot;mycookbook::cleanup&quot;<br>include_recipe &quot;mycookbook::generate_checklist&quot;</pre><p>So, three “full contained” recipes. I just need to create the correct cookbook, with the correct recipes for each stage.</p><p>Kids, this is why you need to automate things to ensure quality control. This is no funky business.</p><p>And this is the basis for DevOps. I cannot tell what is the real role of Devops on their everyday job. Just got involved on this, but one thing you need to know is this : better get some quality machines for developers. The QA process comes before and if you can automate it, the better.</p><p>And no back injuries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1633276e09e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/quality-assurance-is-no-funny-business-1633276e09e">Quality assurance is no funky business</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bienvenido Cristian Ferrari a 5rabbits!]]></title>
            <link>https://medium.com/5rabbits-engineering/bienvenido-cristian-ferrari-a-5rabbits-f341375dbf80?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/f341375dbf80</guid>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Mario Lavandero]]></dc:creator>
            <pubDate>Thu, 27 Oct 2016 18:38:55 GMT</pubDate>
            <atom:updated>2018-07-05T22:30:25.289Z</atom:updated>
            <content:encoded><![CDATA[<p>Bueno, como dice el titulo, queremos darle una gran bienvenida a nuestro más nuevo integrante: <strong>Cristian Ferrari</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WeV64uKFTLj3rJTSBI8oHQ.jpeg" /><figcaption>El que esta al medio con los brazos cruzados es Cristian</figcaption></figure><p>Estamos muy felices de contar con toda su experiencia en UX como también en el desarrollo de productos. Sabemos que con su apoyo seguiremos en nuestra senda por crear los mejores productos SaaS para el mundo desde Chile.</p><p>Pueden ver otro proyecto de Cristian en <a href="http://vadb.org/">http://vadb.org</a> y revisar lo que ha hecho en GitHub: <a href="https://github.com/cristianferrarig">https://github.com/cristianferrarig</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f341375dbf80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/bienvenido-cristian-ferrari-a-5rabbits-f341375dbf80">Bienvenido Cristian Ferrari a 5rabbits!</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 21st Century]]></title>
            <link>https://medium.com/5rabbits-engineering/chaos-in-the-21st-century-9aebfcead49a?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/9aebfcead49a</guid>
            <dc:creator><![CDATA[jCi]]></dc:creator>
            <pubDate>Tue, 25 Oct 2016 21:06:32 GMT</pubDate>
            <atom:updated>2016-10-25T22:16:56.043Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Chaos in the midst of chaos isn’t funny, but chaos in the midst of order is.” — Steve Martin</blockquote><p>Here are my observations of what happened on October 21st.</p><p>In the ye-old times, phones were connected by human operators. One person sent a pulse to the central, an operator picked up the connection, a quick chit-chat about the destination, another connection to another operator…until the phone conversation started. It was the old times. Well, I know this first hand: mom was an operator for CTC (Compa~ia de Telefonos de Chile, before the merger with Telefonica) in the south of Chile, so I had some insights about that job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*ZloMHNMbZZ2HDzCB.jpg" /><figcaption>Source: <a href="http://www.fotoleren.nl/component/bronnenbank/?view=bronnen&amp;tmpl=iframe&amp;start=5360">http://www.fotoleren.nl/component/bronnenbank/?view=bronnen&amp;tmpl=iframe&amp;start=5360</a></figcaption></figure><p>But that job got stressful if something happened locally. Not all operators could fulfill in a timely manner all requests to call. Sometimes during festivities not all hands could process all calls. And this caused a “denial of service”. Simply put: not all calls could be processed and new calls were stacking up until the volume of calls got reduced to be handled properly.</p><p>Enter the internet.</p><p>The first occurrence of a denial of service that comes to mind is the “Slashdot effect”, first described near 2003.</p><p>Once a link got published on Slashdot (http://slashdot.org), the influx of people trying to get to a smaller site caused always a denial of service and a spike on the network usage of the site. Most of the times the sites got kicked off the internet and could not be accessible for a while. Add, of course, if the site got dynamic content, such as Perl CGIs, CPU time of the (poor) server went up the roof and cannot serve any other request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/659/0*_s0WMXpIzd1PB6yx." /><figcaption>If you see this on your /status page, start praying. Source: <a href="https://www.trustwave.com/Resources/SpiderLabs-Blog/ModSecurity-Advanced-Topic-of-the-Week--Mitigation-of--Slow-Read--Denial-of-Service-Attack/">https://www.trustwave.com/Resources/SpiderLabs-Blog/ModSecurity-Advanced-Topic-of-the-Week--Mitigation-of--Slow-Read--Denial-of-Service-Attack/</a></figcaption></figure><p>Of course, this comes with the TCP/IP territory.</p><p>There’s no basic mitigation rule on the protocol, but on the implementation. After network devices got a little bit more smart (read <em>intrusive on the connections</em>), it was easier to put measures, such as:</p><ul><li>Bandwidth Limitation (total/time based/load based/etc)</li><li>Source Limitation</li><li>Geographic Limitation</li></ul><p>These measures are basic elements implemented on routers, switches, firewalls and more.</p><p>Of course the people of the internet got a little creative.</p><p>Enter the zombies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y4s--RFP_waMJow5.jpg" /><figcaption>This.</figcaption></figure><p>As the techniques to “infect” (and control) a computer got more sophisticated each year , so are the motivations of the people behind the infections. They are economic (identity theft, bank fraud, etc). Or purely chaotic.</p><p>Taking control of several hundred thousand computers can guarantee to cause any server to go down to its knees. And adding more and more zombie computers can have several services down for (almost) unlimited time.</p><p>This is called <strong>Distributed Denial of Service</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/0*aF3hQTOl-af1UHt2.jpg" /><figcaption>Pretty much self explanatory.</figcaption></figure><p>There are two basic elements :</p><ul><li>Command and Control (or Command Center)</li><li>Zombie Attackers.</li></ul><p>Command Center gives an order to the Zombie hosts which go with all their possible bandwidth (or requests) against the victim. So, the victim drains its bandwidth, their resources (CPU, requests/second, etc) and finally kicking it off from the network. Sometimes the network equipment got severely affected causing also some network delays, such as firewalls running out of memory. Generally, the Zombies run the control software undetected. The success rate of this infection is related to the security of the operating system. As Windows XP has reached its end-of-life, several computers are running insecure software and are connected to the internet…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/0*s_qnhTqf1pzcYQpS.jpg" /><figcaption>Yup. Donald’s doctor uses Windows XP.</figcaption></figure><p>Picture now that the combined bandwidth of the zombies will always be bigger than the victim’s. Of course, now with the “Cloud” (emphasis is mine), scalability of services is much easier now, so putting additional resources to mitigate the incoming attacks will always be a matter of cat/mouse game.</p><p>Before going on, I must speak a little bit about two recent protagonist on the recent DDOS attacks that come to mind: <em>Lizard Squad</em> and <em>PoodleCorp</em>.</p><p><em>[ Disclaimer: I’ll keep my own thoughts about those groups ]</em></p><p>Lizard Squad got “famous” on the internet for putting down PSN (Playstation Network) and Xbox Live services down.</p><p>In Christmas.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*ZxK1JYo8mLU5hZtY.jpg" /><figcaption>Lizard Squad Twitter avatar. Source: Twitter</figcaption></figure><p>These pranksters did it purely for the fun of it. And also to create awareness to the maintainers of these projects to invest more on the mitigation efforts against these type of attacks.</p><p>By quoting ‘Ryan’, from Lizard Squad :</p><blockquote>“We did it mostly to raise awareness, to amuse ourselves,”</blockquote><p>Of course, messing with the wrong people and doing the wrong things got them notoriety. Three members of LS are now serving jail time for several charges, some of them include extortion…</p><p>Enter PoodleCorp later on.</p><p>They repeated some of the exploits made by LS. This time they got a little more sophisticated. Also got a stressing service offered for a few Bitcoins. At the time of this writing, the service (along with PC page) is down. The offered stressing service was able to put 15Gbps of traffic for 1200 seconds for unlimited times. This is enough to make a sysadmin day from bad to worse.</p><p>But some things went under the radar.</p><p>Two members of LS/PC (I’m not sure if these groups were connected anyways, so I’ll just say “can’t tell”) were arrested on October 13th. Along with this, Assange’s internet connection was severed (again, I’ll keep my thoughts to myself) due to the US presidential election and Wikileaks constant “leakage”. Oh, and source code for a botnet targetting IoT devices was disclosed.</p><p>And then October 21st comes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/0*n9ySafFny2tPJfgP." /><figcaption>Also, Battlefield 1 was released the same day… Source: Twitter</figcaption></figure><p>According to Dyn’s report <a href="http://dyn.com/blog/dyn-statement-on-10212016-ddos-attack/">here</a>, around 7:00 EST, they perceived an unusual spike of network usage. Of course, not unusual for an internet service provider. But two hours later they could not handle the DDoS attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/0*ZlEc6ypkZIM-QdWL.png" /><figcaption>Skynet is here!</figcaption></figure><p>The attacks persisted until 13:00 EST (6 hours!) until a new attack was detected but easily mitigated.</p><p>Services <a href="https://krebsonsecurity.com/2016/10/hacked-cameras-dvrs-powered-todays-massive-internet-outage/">affected</a> by this attack were Twitter, Amazon, Tumblr, Reddit, Spotify and Netflix. Some others also, but those are the ones I can verify.</p><p>Now, let’s put things with numbers:</p><ul><li>The amount of IP addresses used in the attack was around 10 million.</li><li>The attacks used several techniques and vectors.</li><li>Many of the devices used on the attacks were infected with the Mirai botnet.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZSmnw247QZkH8-zx.jpg" /><figcaption>Sort of. Source: Imgur</figcaption></figure><p>So, now the new actor is stealing the spotlight: the infamous <strong>Internet of Things</strong>.</p><p>Mirai botnet code was released on October 1st, 2016. It contained a series of attacks all oriented to Internet of Things capable devices. As these “things” rely on amateurish software (without any source code available for the people to audit), they come with some pretty funny things in there:</p><ul><li>Some passwords are embedded on the firmware.</li><li>Changing the default password does not guarantee that any superuser password cannot be used.</li><li>Some administrative tools are enabled by default. Usually, these tools are insecure as fuck, such as telnet.</li><li>Some accounts are hidden from the user and are for administrative purposes.</li><li>Did I mention that these administrative tasks can be ran remotely?</li></ul><p>XiongMai Technologies sells surveillance cameras (and some other things) that are IoT capable, can be operated remotely and, of course, <strong>had the problems mentioned above</strong>. According to <a href="https://krebsonsecurity.com/2016/10/iot-device-maker-vows-product-recall-legal-action-against-western-accusers/">Krebs on Security</a>, millions of devices are being recalled because someone fucked up. Big time.</p><p>The root password was embedded on the firmware of the device and can be used for remote connection. Not only that, it allowed to upload programs that can be used as a Zombie station (like an infected computer) and can happily phone home to the Command Center. This is not a mishap, it’s a big fuck up. XM social media account said this:</p><blockquote>“XM have to admit that our products also suffered from hacker’s break-in and illegal use.”</blockquote><p>And it’s not only internet cameras. So far, the amount of devices that can be infected with this botnet is unknown. DVRs are known to be vulnerable.</p><p>In a time when an <a href="http://www.theregister.co.uk/2015/10/19/bods_brew_ikettle_20_hack_plot_vulnerable_london_pots/">internet-powered kettle can not be operated from the other room but spews the Wifi password</a>, <a href="https://twitter.com/ScriptedTech/status/789860698499284993">a door cannot be opened because an application crashed</a>, <a href="https://twitter.com/matsbs/status/781446243226714112">coffee machines that require a password to brew</a>, <a href="https://twitter.com/internetofshit/status/767732717786132480">smart electrical sockets that can potentially be a botnet</a> and a <a href="https://twitter.com/kashhill/status/763052577193721856">sex toy that phones home to the manufacturer every time its being used</a>… there should be a tipping point.</p><p>That tipping point is now.</p><p>Welcome to the 21st century. We were promised flying cars. Instead, we have the IoT, the best and worst idea ever conceived.</p><p>BTW follow @internetofshit on Twitter. Please.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9aebfcead49a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/chaos-in-the-21st-century-9aebfcead49a">The 21st Century</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LEGO Mindstorm, más que un juguete…]]></title>
            <link>https://medium.com/5rabbits-engineering/lego-mindstorm-m%C3%A1s-que-un-juguete-e5b7fb247e5c?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5b7fb247e5c</guid>
            <category><![CDATA[ideas]]></category>
            <category><![CDATA[lego]]></category>
            <category><![CDATA[robotics]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Nicolás Torres]]></dc:creator>
            <pubDate>Thu, 06 Oct 2016 13:01:01 GMT</pubDate>
            <atom:updated>2018-07-05T22:23:08.263Z</atom:updated>
            <content:encoded><![CDATA[<p>¿Quién no jugó con Lego cuando era un niño? Pues bien, al ingresar a la universidad me di cuenta que Lego no era un juguete tan sólo para niños (de hecho esta línea no dejó de serlo, pero generó gran interés en adultos con alma de niño), existía una línea de Lego (ignorada por mí) la cual permitía construir los mismos diseños que hacía de niño, pero ahora podían cobrar vida…</p><h3>Un juguete que cobra vida…</h3><p>Apenas ingresé a la universidad, la primera interacción que tuve fue crear un auto con Lego, pero a diferencia de los de antaño, este tenía ruedas con motores, y las luces pasaron a ser sensores de luminosidad en vez de una pieza transparente que simulaba ser un foco.</p><p>Utilicé un ladrillo programable RCX (de Robotix Command eXplorers) el cual programé con el lenguaje NQC. Este ladrillo tenía un procesador de 16 MHz y 32K de RAM (pequeño, pero empeñoso).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCotQ5LRJJvc6CniXpAtCQ.jpeg" /></figure><p>Tenía una simple misión, seguir un camino demarcado por una cinta aisladora 3M de 18mm de ancho. Para ser sincero no me fue muy bien en esta primera experiencia, pero marcó mi interés en lo que sería el programar bichos (microcontroladores) y el trayecto de mi carrera.</p><h3>Una competencia internacional…</h3><p>Al año siguiente se comentó que existía una competencia internacional de robótica con sede en la UTFSM (Valparaíso), era la LARC 2009. Junto a unos compañeros tomamos la decisión de ir a probar suerte a dicho evento, por lo que fuimos a hablar con el director de escuela de ese entonces quién alegremente nos dio todo su apoyo y nos facilitó los ladrillos que necesitáramos, fue ahí donde conocí la segunda versión de ladrillos creados por Lego.</p><p>El NXT de (NeXT) ya tenía más capacidad, contaba con un procesador de 46MHz y 64KB de RAM, también cambiamos de lenguaje y pasamos a utilizar RobotC para darle vida a este bicharraco.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HfK2y3U715moUh6KauwCQ.jpeg" /></figure><p>El desafío acá cambió, ya no era un simple autito que sigue la línea, sino que debíamos pensar en grande. Producto de un desastre natural (un terremoto), era necesario utilizar robots para reconstruir la ciudad e ir por los heridos e ilesos. Para ser la primera vez que concursábamos en algo así no nos fue tan mal, obteniendo un 5to lugar en la tabla.</p><p>Gracias a esta experiencia, mi interés por los este tipo de tecnologías creció y di un paso más allá adquiriendo una placa Arduino.</p><h4>A viajar por el mundo (Sudamérica)</h4><p>Dada la buena experiencia obtenida anteriormente, y con la confianza del director de escuela, fue cuando con un amigo decidimos ir más allá en este descubrimiento de los Lego y propusimos ir a otro concurso internacional, esta vez con sede en Bogotá, Colombia. La Pontificia Universidad Javeriana sería la sede del LARC 2011.</p><p>Con el apoyo del director de escuela (el mismo aún) nos embarcamos rumbo a esta aventura, la cual ya no constaba en seguir líneas ni rescatar gente, ahora debíamos transformarnos en recolectores de granos de café. El aparato debía partir en un punto, atravesar un camino con un obstáculo en medio (un charco de agua dibujado) y llegar a los árboles de café. Al situarse en el árbol se debía reconocer los granos maduros, medio maduros e inmaduros, separar los maduros de los medio maduros y dejar los inmaduros en el árbol.</p><p>Si bien esta vez no nos fue tan bien como pretendíamos, sirvió de gran experiencia para compartir ideas, ver distintos prototipos de robot y entender la forma de ver distintas soluciones para un mismo problema.</p><h3>De vuelta a la realidad</h3><p>De vuelta ya en Santiago, dejé de lado un poco este entretenido mundo, ya me encontraba trabajando y terminando de estudiar, por lo que mi <em>target</em> ya era terminar de estudiar. Quisimos ir a un último desafío antes de salir de la Universidad, pero por problemas en la casa de estudio no se logró concretar.</p><p>Pese a que ya no nos reuníamos a programar robots, aún de vez en cuando juego con mi Arduino y un ladrillo Lego NXT a luchar entre ellos.</p><h3>¿Comprar uno?</h3><p>Si bien no es llegar y comprar un juguete de estos (dado su valor), en mi opinión, para niños que les gusta la tecnología, adultos que quieren seguir jugando y dar soluciones con Lego, es un gran aporte al desarrollo profesional y creativo. Además no es necesario saber programar en algún lenguaje para usarlo, Lego cuenta con un software bastante intuitivo para dale vida a estos aparatos en el cual tan sólo hay que conectar acciones (avanzar, retroceder, detenerse, etc).</p><p>Siento que este tipo de vivencias fue un aporte en mi proceso de formación profesional, tanto por las tecnologías aprendidas, como las experiencias compartidas con distintas personas de distintos lugares del mundo, por lo que estoy ampliamente de acuerdo con la adquisición de este tipo de juguetes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5b7fb247e5c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/lego-mindstorm-m%C3%A1s-que-un-juguete-e5b7fb247e5c">LEGO Mindstorm, más que un juguete…</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interfaces gráficas con ReactJS]]></title>
            <link>https://medium.com/5rabbits-engineering/interfaces-gr%C3%A1ficas-con-reactjs-2c43481a1c8d?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/2c43481a1c8d</guid>
            <category><![CDATA[talks]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[ideas]]></category>
            <dc:creator><![CDATA[Rodrigo Díaz Vergara]]></dc:creator>
            <pubDate>Mon, 01 Aug 2016 13:48:34 GMT</pubDate>
            <atom:updated>2018-07-05T22:23:40.964Z</atom:updated>
            <content:encoded><![CDATA[<p>Más que hablar de código, este artículo busca explorar los conceptos tras React para evaluar los beneficios y pilares fundamentales en su diseño.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*E_rzIJdXS4ZmkwrRFd7Tfg.png" /></figure><h4>¿Qué es React?</h4><p>React es una biblioteca creada por Facebook y que permite construir <strong>interfaces gráficas</strong> complejas con datos que cambian a través del tiempo.</p><p>Para React el concepto más importante a entender es el de <strong>Componente</strong>, de hecho, lo único que escribirás son componentes…</p><p>Entonces, ¿qué es un componente?.</p><p>Básicamente un componente representa una unidad lógica acotada dentro de tu interfaz gráfica. Por ejemplo, puede ser algo tan simple como un botón o un icono, o más complejo como un calendario o un menú.</p><h3>Pensando en React</h3><p>React se basa en tres grandes pilares que definen su experiencia de uso:</p><ol><li>Código declarativo</li><li>Composición de componentes</li><li>Aprende una vez, escribe donde sea</li></ol><h4>Código declarativo</h4><p>En tus componentes defines qué vista se debe generar a partir de ciertos datos. Cuando esos datos cambien React se encargará de llevar tu interfaz del estado A al estado B… te debes preocupar de <strong>qué</strong> mostrar y no del <strong>cómo</strong>.</p><p>En pocas palabras, cada vez que tus datos cambien React generará una nueva interfaz para representarlos, la comparará con la interfaz actual y aplicará la menor cantidad de modificaciones posibles para actualizar las partes que cambiaron.</p><h4>Composición de componentes</h4><p>Recapitulando, un componente representa una unidad lógica acotada en la interfaz gráfica (por ejemplo, un botón).</p><p>Tu objetivo debe ser siempre crear componentes lo más simple posibles y usarlos para construir otros componentes más complejos. Siguiendo este patrón tendrás componentes con un dominio acotado, lo que otorga muchas ventajas:</p><ul><li>Cada componente encapsula la lógica de su dominio.</li><li>Cada componente tiene responsabilidades bien acotadas. De hecho, cada componente debería tener solo una responsabilidad.</li><li>Facilidad para hacer pruebas unitarias.</li><li>Gran reutilización de código.</li></ul><p>Por ejemplo, podrías tener un componente para desplegar un calendario:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*Ze5sWn0Ck32y3UXnapAxNw.png" /></figure><p>Y luego puedes usar el componente anterior para crear un componente más complejo que permita anclar el calendario a un campo de texto:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*nxml9aWmOLhq-phyHhiVLQ.png" /></figure><p>El primer componente se preocupa de generar el calendario y permitir seleccionar un día, mientras que el último se encarga de sincronizar la fecha seleccionada con un campo de texto.</p><h4>Aprende una vez, escribe donde sea</h4><p>Otro de los puntos claves de React es que a pesar que partió como una biblioteca para generar interfaces en la Web, ahora es mucho más que eso.</p><p>En Marzo de 2015 se <a href="https://code.facebook.com/posts/1014532261909640/react-native-bringing-modern-web-techniques-to-mobile/">anunció <strong>React Native</strong></a>, que lleva los mismos conceptos antes expuestos al mundo de los dispositivos móviles. Si aprendiste a usar React para generar aplicaciones web, ya sabes usar React Native.</p><p>En la actualidad Facebook mantiene tres bibliotecas para aplicar React en las siguientes plataformas:</p><ul><li>react-dom: Crea elementos del dom en una aplicación web.</li><li>react-dom-server: Genera el código html como string, pensado para utilizarse en servidores Node.</li><li>react-native: Genera aplicaciones para iOS y Android.</li></ul><p>Lo que es aún más llamativo es que la comunidad se está aventurando a aplicar React en otros ámbitos. Por ejemplo:</p><ul><li><a href="https://github.com/Flipboard/react-canvas">react-canvas</a>: Flipboard creó este proyecto para generar interfaces web utilizando canvas, que tiene un mayor rendimiento en animaciones con respecto CSS. Está siendo utilizando en ambiente de producción para el timeline de la página web para móviles.</li><li><a href="https://github.com/iamdustan/react-hardware">react-hardware</a>: Dustan Kasten utiliza React para enviar instrucciones a elementos de hardware (por ejemplo, encender o apagar leds).</li></ul><p>Ciertamente estas incursiones de la comunidad pueden ser experimentales pero la idea es indudablemente poderosa, aprende a usar React y crea aplicaciones en distintas plataformas aplicando los mismos conceptos y flujo de trabajo.</p><h3>En definitiva, ¿debo utilizar React?</h3><p>Deberías darle una oportunidad a React si:</p><ul><li>Tienes una interfaz gráfica dinámica. Especialmente si te preocupa su rendimiento.</li><li>Buscas escribir código mantenible.</li><li>Quieres poder hacer pruebas unitarias sin sufrimiento de por medio.</li><li>Te entusiasma poder aplicar lo que aprendas en otras plataformas.</li></ul><p>React podría no ser para ti si:</p><ul><li>Tienes una interfaz mayoritariamente estática (puedes utilizar React de todas maneras, pero tal vez los beneficios que obtengas no valgan la pena con respecto al esfuerzo).</li><li>Necesitas dar soporte a Internet Explorer 8 o anterior, porque funciona solo desde la versión 9 en adelante.</li></ul><p>Un punto importante a considerar es que puedes utilizar React selectivamente dentro de tu aplicación. Nada te impide utilizarlo en un pequeño bloque y usar otra biblioteca (o ninguna) en el resto. Esto es particularmente importante cuando quieres migrar una aplicación existente a React… ¡hazlo progresivamente :)!</p><h3>Enlaces de interés</h3><ul><li><a href="https://facebook.github.io/react/">React</a></li><li><a href="https://facebook.github.io/react-native/">React Native</a></li><li>R<a href="https://github.com/Flipboard/react-canvas">eact Canvas</a></li><li><a href="https://github.com/iamdustan/react-hardware">React Hardware</a></li><li><a href="https://github.com/rdiazv/simple-todos-redux">rdiazv/simple-todos-redux</a>: Ejemplo de ToDo List utilizando React y Redux.</li><li><a href="https://github.com/rdiazv/simple-todos-redux-native">rdiazv/simple-todos-redux-native</a>: El mismo ejemplo anterior migrado a React Native.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c43481a1c8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/interfaces-gr%C3%A1ficas-con-reactjs-2c43481a1c8d">Interfaces gráficas con ReactJS</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tech Talks and Hello to Medium]]></title>
            <link>https://medium.com/5rabbits-engineering/tech-talks-and-hello-to-medium-6fbcb7bdab7?source=rss----f3d442fc6737---4</link>
            <guid isPermaLink="false">https://medium.com/p/6fbcb7bdab7</guid>
            <category><![CDATA[team]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[talks]]></category>
            <dc:creator><![CDATA[Mario Lavandero]]></dc:creator>
            <pubDate>Wed, 03 Feb 2016 02:11:04 GMT</pubDate>
            <atom:updated>2018-07-05T22:28:38.235Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vP9il4A-zycCYDQysrMFDg.jpeg" /></figure><p>Here at 5rabbits we are always trying to learn new things and trying to become better engineers to deliver better products.</p><p>We are ever-learning folks that appreciate beatifully crafted product that we can be proud of. Trying to work with new technologies to have better performance of our apps. Learning how to get the most out of every single piece of the stack so that we can scale products to handle hundreds of thousands of users without any delay.</p><p>In this quest, we find that one of the best ways to become better at what we do, is by learning form other member of our team. That is why every week we have a member prepare and present to the rest a #TechTalk. A presentation on a subject of their choosing in which they feel they have gained expertise in the past months. With this, we feel we are sharing the knowledge with everyone in the team. But, we would like to share our knowledge with everyone else that is interested. To accomplish this, all our #TechTalks are uploaded to our YouTube channel:</p><p><a href="https://www.youtube.com/channel/UCVbaQ_GvmiOapfn2GOyBiLQ">5rabbits</a></p><p>Yes, they are in spanish, but we are working on having subtitles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*KHOCoLNGGveD4bwzJ-9Fjg.jpeg" /><figcaption>5rabbits Engineering Team</figcaption></figure><p>On the other hand, we will start a new way of sharing our knowledge of technology and maybe some of our personal passions: This Medium Publication. We hope to be able to help others and teach them what we have learned through years of crafting amazing products.</p><p>With this, I would like to welcome you to our new publication, invite you to follow and comment on the posts and hope that our passion for Software Engineering can rub off on you.</p><p>En 5rabbits estamos siempre aprendiendo nuevas cosas y buscando convertirnos en mejores ingenieros para entregar los mejores productos.</p><p>Somo aprendices constantes que aprecian productos bien hechos de los cuales podemos orgullesernos. Trabajamos con nuevas tecnologias para tener las mejores apps posibles. Analizando y viendo como sacarle el mejor provecho a cada tecnologia que ocupamos para poder escalar productos a cientos de miles de usuarios de la manera mas eficiente.</p><p>En esta travesía, encontramos que una de las mejores maneras de aprender, es de la gente mas cercana, de otros miembros del equipo. Es por esto que cada semana un miembro del equipo de prepara y presentar un #TeckTalk. Una charla sobre cualquier tema del cual ellos crean que poseen una expertise y que quieran compartir. Con esto el conocimiento de todos es compartido internamente. Pero, también creemos que debemos compartir esto con la comunidad, por lo que tambien grabamos nuestros #TeckTalks y los subimos a nuestro canal de YouTube:</p><p><a href="https://www.youtube.com/channel/UCVbaQ_GvmiOapfn2GOyBiLQ">5rabbits</a></p><p>Por otro lado, empezaremos una nueva manera de compartir nuestro conocimiento y tecnología (y tal vez alungas de nuestros pasiones personales): Esta publicación en Medium. Esperamos poder ser de ayuda para el reesto y enseñarles lo que hemos aprendido de años de experiencia creando grandes productos.</p><p>Con esto quisiera darles la bienvenida a nuestra nueva publicación, invitarlos a seguirnos y comentar nuestros posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fbcb7bdab7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/5rabbits-engineering/tech-talks-and-hello-to-medium-6fbcb7bdab7">Tech Talks and Hello to Medium</a> was originally published in <a href="https://medium.com/5rabbits-engineering">Crafting products with joy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>