<?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 Marcelo Theodoro on Medium]]></title>
        <description><![CDATA[Stories by Marcelo Theodoro on Medium]]></description>
        <link>https://medium.com/@marcelotheodoro?source=rss-46e1ce7ab8e7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*hDbtkc8N2bHvJhD-Bhrh7Q.jpeg</url>
            <title>Stories by Marcelo Theodoro on Medium</title>
            <link>https://medium.com/@marcelotheodoro?source=rss-46e1ce7ab8e7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:07:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marcelotheodoro/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[É impossível "não se preocupar" com algo]]></title>
            <link>https://medium.com/@marcelotheodoro/%C3%A9-imposs%C3%ADvel-n%C3%A3o-se-preocupar-com-algo-a011ea75efb2?source=rss-46e1ce7ab8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/a011ea75efb2</guid>
            <category><![CDATA[estoicismo]]></category>
            <dc:creator><![CDATA[Marcelo Theodoro]]></dc:creator>
            <pubDate>Tue, 22 Oct 2019 13:33:40 GMT</pubDate>
            <atom:updated>2019-10-22T13:33:40.122Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tentar não se preocupar com algo, é como se esforçar para não pensar no elefante branco.</h4><p>Primeira coisa que aprendi, e concordei, com o Estoicismo é a ideia de que devo focar minha atenção nas coisas que estão sob meu controle. Apenas aceitando as coisas que não estão.</p><p>O problema é que não é possível, ativamente, não se preocupar com algo. Com grande frequência noto que estou tentando não me preocupar com algo, e falhando totalmente nisso. Levando à ansiedade.</p><p>A solução que tento aplicar, e que eventualmente dá certo, ou às vezes não, é de não focar na parte de “não se preocupar com coisa X que está fora do controle” e sim, “vou dar toda minha atenção para problema Y porque este está sob meu controle”. Uma vez que preencho meus pensamentos com as coisas que estão sob meu controle, não sobra espaço para o resto.</p><p>Seja lavar uma louça, escrever algum código ou fazer algum exercício. Essas coisas funcionam para se livrar de pensamentos que não estão contribuindo com meu bem-estar.</p><p>Engraçado que fazendo uma avaliação do meu passado, é como se eu sempre soubesse disso, mas nunca tivesse formatado esse pensamento.</p><p>Os momentos mais legais da minha vida até hoje, foram exatamente os momentos em que eu estava com muita coisa pra fazer no trabalho, e, ao mesmo tempo, tinha projetos pessoais que me tomavam bastante tempo. Foi um período em que eu ficava exausto, porém tranquilo.</p><p>Em outros momentos que tinha mais tempo livre, o oposto acontecia. Parecia que eu tinha sempre tanta energia… No final, ficava ansioso e com vontade de sair correndo às 3:00 da madrugada ao invés de dormir.</p><p>Não é a toa que dizem que o Estoicismo é uma disciplina de ação.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a011ea75efb2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My personal guide to code review]]></title>
            <link>https://medium.com/@marcelotheodoro/my-personal-guide-to-code-review-35406bc7683e?source=rss-46e1ce7ab8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/35406bc7683e</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[quality-of-code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[code-review]]></category>
            <dc:creator><![CDATA[Marcelo Theodoro]]></dc:creator>
            <pubDate>Tue, 20 Aug 2019 00:17:53 GMT</pubDate>
            <atom:updated>2019-08-24T03:13:12.675Z</atom:updated>
            <content:encoded><![CDATA[<p>Just like any other process, code review is easier when you know exactly what are the steps needed to successfully finish the task.</p><p>I have been developing my personal process to code review for some years, but I never wrote it down before. This post is an attempt to formalize the process. My idea here is to start from the very basic, and grow this guide as I&#39;m able to detect more patterns.</p><p>I encourage anyone who&#39;s reading this guide to write your own guide, and share with us. It&#39;ll help both you and everyone else reading your method.</p><h3>Categorizing</h3><p>Usually, I&#39;m able to categorize the PR in one of these categories:</p><ul><li>Bug Fixes</li><li>New features</li></ul><p>When the PR is not <strong>clearly</strong> one, and preferably, only one of these things, we will have the first red flag. The team may need to discuss the context that this PR was created to make the process of reviewing easier.</p><h4>Bug Fixes</h4><ol><li>Understand when and what conditions the bug happens.</li><li>Reproduce the bug in the &quot;master&quot; branch so you can see the bug in the front of your eyes.</li><li>Checkout the branch that&#39;s fixing the bug and try to reproduce it again.</li><li>Run the regression tests. The expected is to pass.</li><li>Rollback the changes that are fixing the bug, run again the regression tests. The expected is to fail.</li><li>Review code line by line — I&#39;ll go deeper in this topic in some future post.</li></ol><h4>New Features</h4><ol><li>More usually than not, the Pull Request of a new feature is just an independent deployable part of a bigger delivery. In this case, if you are in a team that is good at breaking a large task in small ones, is expected that you’ll have the instructions of what needs to be done in that PR to allow the other parts that are coming. Focus on that. If, for some reason, you don’t have information enough to get the idea of that PR, do not think twice about asking as many questions as needed.</li><li>As we are adding new code, it’s important to check if this new code is following the patterns of the team.</li><li>The tests should not test only the “happy path” when everything works. It also should test what must happen when somethings goes wrong.</li><li>If you are working on an API, you probably have some documentation for this API. In this case, you must check if the changes made in that PR are reflected in the documentation.</li><li>As we do in the bug fix, we should go line by line here too.</li></ol><p>We might also consider the possibility of a third category. Sometimes we are just refactoring some code, updating a dependency or something like that. In this case, we could say that this is an &quot;internal change&quot;. I won&#39;t describe those yet because they vary a lot and I couldn&#39;t figure out the categories related to that kind of PR.</p><p>In the next post, I&#39;ll write about what are we looking for when doing a line by line review.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35406bc7683e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first acknowledgment with my hobby of  Lock Picking]]></title>
            <link>https://medium.com/@marcelotheodoro/my-first-acknowledgment-with-my-hobby-of-lock-picking-caf356cfaee6?source=rss-46e1ce7ab8e7------2</link>
            <guid isPermaLink="false">https://medium.com/p/caf356cfaee6</guid>
            <category><![CDATA[lock-picking]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[hobby]]></category>
            <dc:creator><![CDATA[Marcelo Theodoro]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 03:18:15 GMT</pubDate>
            <atom:updated>2019-08-12T16:28:17.627Z</atom:updated>
            <content:encoded><![CDATA[<h3>What my hobby of Lock Picking taught me</h3><p>Inspired by the <a href="https://www.youtube.com/channel/UCm9K6rby98W8JigLoZOh6FQ">LockPickingLawyer</a> I started to practice lock picking some time ago. Since the very first day of training, I noticed something strange, let’s say, a pattern about when I would be able to easily pick a lock, or would just fail.</p><figure><img alt="4 padlocks and a lock pick set" src="https://cdn-images-1.medium.com/max/765/1*d69t0RC0pDnM6Vh-6utmEA.png" /><figcaption>My first lock pick set</figcaption></figure><p>The pattern that I found out when picking a lock was pretty clear: I would perform significantly better when I was practicing it with a cool head in a calm state of mind. :)<br>For example, if I try to put pressure on myself to open the lock as fast as possible, I will have worse performance than if I just tried to calm my mind — by meditating, doing some ritual — before starting the practice.</p><p>The idea that we perform better in any activity with a cool head is not new for anyone. This realization impacts me because I had no idea of how much of the performance I was losing by working on it in the wrong state of mind.<br>After understanding this impact, I started to draw parallels between the performance while being in a good state of mind, in contrast of being in a bad state of mind in all my daily activities: programming, cycling, reading and even in social activities like having a quality time with my SO. I have to say, it impacts a lot.</p><p>To pick a lock is a challenge. Just like any other challenge we have to deal on a daily basis. Just as this pattern affects lock picking, it’ll affect all your challenges. <br>Before doing something important, what about try to identify how well you are felling? I’m sure it’ll bring some good for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caf356cfaee6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>