<?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 Ale Donoso on Medium]]></title>
        <description><![CDATA[Stories by Ale Donoso on Medium]]></description>
        <link>https://medium.com/@alesdonoso?source=rss-18fcf7ac4192------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PksTeqM4OI5C6XQDkX_y3w.png</url>
            <title>Stories by Ale Donoso on Medium</title>
            <link>https://medium.com/@alesdonoso?source=rss-18fcf7ac4192------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:17:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alesdonoso/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[Documentation is power]]></title>
            <link>https://alesdonoso.medium.com/documentation-is-power-6104a2ac6f58?source=rss-18fcf7ac4192------2</link>
            <guid isPermaLink="false">https://medium.com/p/6104a2ac6f58</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Ale Donoso]]></dc:creator>
            <pubDate>Fri, 25 Feb 2022 13:06:45 GMT</pubDate>
            <atom:updated>2022-02-25T13:06:45.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RqlE_wIFBMgLIY06" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund?utm_source=medium&amp;utm_medium=referral">Sigmund</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In the dynamic world of software, having references is the best tool to never lose your way and have a guide you can always turn to for having clear ideas.</p><p>Documentation plays a leading role here.</p><p>I’m a big fan of asynchronous work for many reasons. And here, documentation is my best ally.</p><p>Although synchronous work is very good on certain occasions to solve problems and come up with ad-hoc solutions, I personally think that it should only be an exceptional tool on a day-to-day basis.</p><p>Therefore, I love to introduce the documentation process in my workflow. For me, it is an essential part of the work that every PM must assume as a facilitator of the work for the rest of the departments.</p><h3>Why do I think documentation is power?</h3><p><strong>It is reusable</strong>. It’s like a good component that can be reused in the same logic countless times. When you create similar documented schemes of work, they allow you to reuse them in future tasks that need to come up with identical and tangential solutions.</p><p>These allow you to reach the same checkpoint at different stages of the product lifecycle, from research and ideation to marketing and sales.</p><p><strong>It is scalable</strong>. When you document, you are directly and indirectly improving processes used throughout the development cycle. The documentation will improve on its own as you introduce new mechanics and processes into your workflow.</p><p>Imagine that you have to propose a new A/B test, going back to your past experiments and reading the conclusions can help you more easily identify what can work better and worse.</p><p>In a chaotic world, knowing where to go at all times saves you valuable time, makes you more efficient and effective. Time matters, although I am also of the opinion that <em>nothing is so urgent</em>.</p><p><strong>Nothing is so urgent</strong>. I think this idea is quite powerful. The documentation allows you to take the necessary time to reflect, contrast ideas and propose hypotheses and scenarios after executing a key research phase for a subsequent definition.</p><p>Documenting gives you the necessary space to think and reflect.</p><p><strong>Block cold decision-making and save future debt</strong>. It seems to be all related, right? When you take your time to reflect and group ideas around a certain element, you ensure that you are not making cold decisions, which in most cases will end up showing debt in future development.</p><p>Cold decision-making has a brutal impact on the workflows of all the teams involved. It blocks the benchmark and teams can feel lost when doubts start to creep in. Making sure you create the reference is vital.</p><p><strong>Allows collaboration and abstraction</strong>. Creating documentation is not an individual job, it requires collaboration. Involving the rest of the team in the definition will allow them to abstract from their different realities and emphasize their needs, compare ideas, and reach a common landing point.</p><p>It creates a global vision, where many individuals contribute. Your team feels involved in decision-making and, therefore, more motivated to achieve a common goal. Never work isolate.</p><p><strong>The documentation creates an anchor</strong>. Documentation is the version control system for management profiles. It allows you to access a history of decisions to know when and how things were defined. Prevent you and your team from feeling lost in an ultra-dynamic world.</p><p><strong>It enables creativity</strong>. Lastly, I believe that one of the most powerful virtues of documentation is that it increases individual and group creativity. When you make decisions on the fly, you are reducing the possibility of creating creative solutions to your problem.</p><p>Take time to reflect (#3) with creativity to solve problems that are never easy. When it is also introduced to different parts, creativity grows exponentially. Don’t isolate yourself, trust your team to create meaningful things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6104a2ac6f58" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Imposter Syndrom and the Talent]]></title>
            <link>https://alesdonoso.medium.com/the-imposter-syndrom-and-the-talent-c2c1f242b082?source=rss-18fcf7ac4192------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2c1f242b082</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[talent]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[imposter]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Ale Donoso]]></dc:creator>
            <pubDate>Fri, 26 Mar 2021 16:16:12 GMT</pubDate>
            <atom:updated>2021-03-29T10:16:30.093Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Imposter Syndrome and the Talent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0nWj4Q3GpI5z2mi4" /><figcaption>Photo by <a href="https://unsplash.com/@jessedo81?utm_source=medium&amp;utm_medium=referral">jesse orrico</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Once a teacher asked all the students during a class: <strong>do you think you are talented people?</strong> The students began to look at each other, stunned and in silence, in front of the question that the teacher had just thrown.</p><p>Then and seeing that no one answered, the teacher decided to ask the same question again, this time individually: do you consider yourself a talented person? It was clear that the students were not expecting that question at the time.</p><p>Surely they would never have asked themselves that same question before. But there they were, exposed to the challenge of giving an answer to the teacher. The answer was simple: yes or no. The reflection on the question was a really complicated thing.</p><p>When the round of questions ended, more than fifty percent of the people answered: <strong>NO</strong>. The teacher — who was already used to this type of situation — began to give a motivational speech and ask out loud why these people did not consider themselves talented.</p><blockquote>More than fifty percent of the people answered: <strong>NO</strong></blockquote><p>These people thought they had no quality, skill, aptitude, or attitude to be considered talented. They hadn’t stopped to think that they really were unique. It was clear that his answers were wrong. <strong>But they did not know</strong>.</p><p>It may seem fiction, but the reality is that it is a situation that I experienced back in 2017 when I was studying for my Master’s Degree in Sociology. At that precise moment, these people did not stop to think about what they meant and the value they were really bringing to society.</p><p>Nobody had told them: <strong>you have a natural talent for being unique</strong>. Publicly accepting that statement is the true ally against the impostor syndrome.</p><p>This same week, my partner and <a href="https://z1.digital/?utm_source=medium&amp;utm_medium=link&amp;utm_campaign=imposter_syndrom">People Manager of z1</a>, Aure Contreras, raised this question, and, as always happens in z1, the debate arose.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*DgTFB7OaRgSEx2ftoW0Ssg.png" /></figure><p>There is no doubt that this sentiment is quite common in the digital sector. The challenges we face as creators of digital products exacerbate our mistrust. Day by day we face different and complex problems that require agile solutions in a sometimes hostile environment.</p><p>I am sure that we could brainstorm great and put on the table the main variables that can highly impact the appearance of this syndrome. However, I am going to focus on one: <strong>trust</strong>.</p><p>For me, in addition, trust also has two aspects: internal and external. The internal is the confidence that you have in yourself. The external is the trust that you transmit and receive from your environment. <strong>And both feed off each other</strong>.</p><p>From my point of view, in our professional lives, the trust that you place in your environment and vice-versa can clearly balance and unbalance the scale.</p><p>If you are in a safe environment, where you are provided with the necessary tools so that you can develop smoothly and <strong>without fear of making mistakes and where those are considered a learning point</strong>, the chances of the syndrome appearing will most likely be drastically reduced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uG5ATmjdCA4aQpXe" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>On the contrary, if you are in a more complicated environment, <strong>where making mistakes becomes a fear and mistakes are seen as a failure</strong>, the possibility that your confidence will decrease will increase. Not to mention your ability to develop as a professional, although that is another matter.</p><p>That is why I believe that <strong>the environment is the most important part to explain this phenomenon</strong> and that the tools we have to combat it are adequate, <strong>it is essential</strong>.</p><p>A hostile environment is most likely to trigger the onset of this syndrome. Self-pressure and ego-based battles can also play a role against you. And this is quite common, mainly in the world of software development.</p><p>In the end, the impostor syndrome is still a mental image that we potentially mold to our own detriment, when we try to self-answer questions such as: <em>do I really know how to do what I am doing? Do I really know what they expect me to know?</em></p><p>When the right question should be: <em>why do I judge myself if I’m already here?</em> In the end, the image of reality is quite different.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oq17SEs1I2D9mhWKz6ij_A.jpeg" /><figcaption>What you think vs reality</figcaption></figure><p>We have to be able to control the events and variables that are within our reach and depend entirely on us. <strong>Take responsibility for executing your work without fear of being wrong</strong>. Learning from your mistakes and making your environment learn from them too is an essential part of the process.</p><p>However, there are also another series of variables that are totally beyond our control and that are more casuistic and random. It is better not to pay attention to this series of variables directly. As <strong>Michael Jordan</strong> would say: “why would I think about missing a shot I haven’t taken yet”.</p><p>I know that it is not as easy as saying: obvious this. But the reality is that we must put the spotlight on the variables that we can control, and simply prepare for what is to come. I am sure you will know how to deal with the problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*qD-YEHyql9myj42TGEwv8g.jpeg" /><figcaption>One of the most famous shots of Michael Jordan in the finals against Utah Jazz</figcaption></figure><p>If we go back to the example of the teacher and the students, we can realize that the students were wrong because they had never really stopped to think about their answer to that question.</p><p>It is difficult to think about this type of approach individually. It is always the environment that urges and pushes us to bring out the talent that we carry inside.</p><p>It is when we face the problems that appear when we work as a team that we have to bring out our skills to solve them. Trying to fulfill the expectations that others have of us increases the levels of self-demand, and that is not necessarily bad.</p><p>It’s important to note that <strong>we must assume our part of individual responsibility in the process</strong>, always bearing in mind that proving who we are is not a matter of a specific moment. It is part of a whole process that requires time, effort, and dedication. It is a curve that we must overcome, and it is better that the team guide you until you reach the finish line and you collectively enjoy the success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2c1f242b082" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why small PRs increase developer productivity.]]></title>
            <link>https://medium.com/swlh/why-small-prs-increase-developer-productivity-577ad60ca360?source=rss-18fcf7ac4192------2</link>
            <guid isPermaLink="false">https://medium.com/p/577ad60ca360</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[git]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[workflow]]></category>
            <dc:creator><![CDATA[Ale Donoso]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 10:53:09 GMT</pubDate>
            <atom:updated>2020-10-01T11:04:18.931Z</atom:updated>
            <content:encoded><![CDATA[<h4>Reviewing huge lines of code modified is not efficient at all.</h4><p>Let’s be clear: all of us have dealt with a PR review with tons of lines modified. No one wants to review that kind of PRs, it could be annoying and you probably are not going to give a good look at everything. Here starts the malicious workflow.</p><p>Some time ago, a friend of mine, <a href="https://medium.com/u/a8c939b0c7c9">Jesús Darío</a>, wrote about <a href="https://itnext.io/how-to-make-great-code-reviews-9fb7d84b77e8">How to make Great Code Reviews</a>. I’d recommend you take a look at the article, it is an easy and understandable approach to greatly improve your review workflow.</p><p>He stated that it’s really important to reduce the size of the PRs if you are the contributor. Today I’m willing to explain this concept <em>a little more</em>.</p><blockquote>They should be as small as the minimum functional change that makes sense. — <strong>jsdario</strong>.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E1CbTpVbOAtqSACr" /><figcaption>Photo by <a href="https://unsplash.com/@yancymin?utm_source=medium&amp;utm_medium=referral">Yancy Min</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><a href="https://hacktoberfest.digitalocean.com/">Hacktoberfest</a> is just getting started and tons of Open Source repositories will start receiving PRs. Maintainers will have to deal with tens or hundreds of change proposals in their repositories.</p><p>Do you imagine how much time would it take to review a PR that has several hundreds of lines modified? Not enough time. Too many PRs will be opened at once.</p><p>But this is happening in private software companies too on a daily basis, not only in the open-source world, or because of a monthly event.</p><p>Managing software teams is something fun, enriching, and creative at the same time. But it can be quite stressful <strong>if you don’t have a clear work structure</strong>.</p><p>To this, we must add that, in many cases, technical debt and legacy code have a very important presence. And this is a really important point here: not having a good review culture might lead you to a huge technical debt issue.</p><p>Having a correct code structure helps to decrease this debt. For that, clean and understandable code is a must-have for every developer. And there, creating PRs <em>with sense</em> is the most important thing, so we have to be always thinking about the next step: the PRs should be reviewed, and <strong>the sooner it is reviewed, the better</strong>.</p><blockquote>Does it not start making sense that a small change makes the difference?</blockquote><h3>But… why?</h3><p>We will probably understand it by now. Creating small PRs has a great and important impact on the engineers’ workflow. It can create significant benefits for development teams, dramatically increasing the efficiency and effectiveness of each code change.</p><p>Let’s think it proposing a new feature release in exercise:</p><ol><li>A new feature has to be implemented. It is a new filter that will affect to 2 other features that are already in production.</li><li>The filter creates two different outputs.</li><li>Each output creates different results for each of the two functions in production.</li><li>Result? You have separated the new feature into 6 different tasks <em>— </em><strong><em>quantifiable and measurable minimum units</em></strong>.</li><li>PRs will be released with ease. People know what to do. PRs could also be subdivided into even smaller ones, but they have to be related to the exact branch. That’s the point. Make things easier.</li></ol><p>Let see this scheme:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dlGAR8l3RPu-VsUHzm-CbQ.png" /><figcaption>An example of a new feature release with PRs associated. Image created using <a href="https://whimsical.com/">Whimsical</a>.</figcaption></figure><p>The example is quite simple and I know that’s not going to happen in reality too many often. But what I want for you is to get the point. In software development, everything you do directly affects the workflow, and that&#39;s why <em>things must be thought from their highest level to their lowest level</em>.</p><p>Small PRs help your workflow be as efficient as it deserves. In terms of looking for better team productivity, this flow does not only increases your team velocity but also <strong>your team quality</strong>.</p><blockquote>Make people think better, work better, be better.</blockquote><h4>So, what are the benefits of creating small PRs?</h4><ol><li>Ease commit reading. Small PRs will probably have less number of commits, so it will be easier to read and understand the changes.</li><li>Regarding point #1, commit’s messages will (and need) be better and more useful and descriptive. Lower changes urge you to be a better developer overall, tho this may be an IMHO.</li><li>As it seems to be obvious, <strong>reviews will have a great improvement in terms of quality and velocity</strong>.</li><li>Notable increment in team communication and between engineers, creating a better communication culture and flow.</li><li>Enhance engineers’ motivation. For this I mean engineers won’t see their PRs in the “pending reviews” dashboard for a long time, since the workflow velocity will be greatly improved.</li><li>Decrease drastically tech debt since the <strong>code reviews will be done in a better way and with more frequency</strong>, boosting time engineers take to review the other&#39;s work.</li></ol><p>These are some of the main points, but the list could be endless.</p><p>Perhaps the most important point and the one related to the issue I raise is the connection between small PRs and quality reviews. It’s the union that makes the most sense.</p><p>Small PRs will motivate teams to create a proper review flow. <strong>It’s a fundamental starting point</strong>. I’d recommend you to try out this workflow and share your results with me. I’d be glad to hear from you in the comments.</p><p>Thanks for reading 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=577ad60ca360" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/why-small-prs-increase-developer-productivity-577ad60ca360">Why small PRs increase developer productivity.</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Microsoft Terminal? Let’s customize it with Oh My Zsh.]]></title>
            <link>https://alesdonoso.medium.com/using-microsoft-terminal-lets-customize-it-with-oh-my-zsh-69babbfa4f29?source=rss-18fcf7ac4192------2</link>
            <guid isPermaLink="false">https://medium.com/p/69babbfa4f29</guid>
            <category><![CDATA[zsh]]></category>
            <category><![CDATA[terminal]]></category>
            <category><![CDATA[oh-my-zsh]]></category>
            <category><![CDATA[wsl]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Ale Donoso]]></dc:creator>
            <pubDate>Tue, 17 Mar 2020 14:31:26 GMT</pubDate>
            <atom:updated>2020-03-17T14:36:59.183Z</atom:updated>
            <content:encoded><![CDATA[<p>WSL is probably one of the better options for development on Windows systems actually. Let’s give a better look to the terminal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DMBsKkgSmDeAFPY6" /><figcaption>Photo by <a href="https://unsplash.com/@cgower?utm_source=medium&amp;utm_medium=referral">Christopher Gower</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>You can find this guide also in </em><a href="https://github.com/alesdonoso/scope-windows-terminal-ohmyzsh"><em>my repository</em></a><em> on GitHub. If you like it, don’t forget to give me a ⭐!</em></p><h3>What is WSL?</h3><p>As Wikipedia says, <strong>Windows Subsystem for Linux</strong> (<strong>WSL</strong>) is a compatibility layer for running Linux binary executables (in ELF format) natively on Windows 10 and Windows Server 2019.</p><p>Basically, it permits you to use the Linux layer on Windows, so you will be able to use Linux commands on the terminal. And for that, Microsoft Terminal is a good option.</p><p><strong>Microsoft Terminal</strong> is an <a href="https://github.com/microsoft/terminal">open-source project</a> from Microsoft and a feature recently added to the OS. It is a new terminal that allows you to use different consoles like CMD, Powershell, Azure, Ubuntu, and etc. Crazy.</p><p>But…what if we can use <strong>ZSH</strong> on the terminal too? Doesn’t sound it awesome? Let’s see.</p><h3>What is ZSH?</h3><p>According to Wikipedia, The Z shell (Zsh) is a Unix shell that can be used as an interactive login shell and as a command interpreter for shell scripting. Zsh is an extended Bourne shell with many improvements, including some features of Bash, ksh, and tcsh.</p><p>macOS Catalina, released in October 2019, adopted Zsh as the default shell, replacing Bash.</p><p>Definitely, a good shell that you must try at least once, and you can do it in the Microsoft Terminal. So if you are using Windows 10 OS, you will be able to get Linux commands on a brand new terminal, with a cool look and with Zsh inside. Cool enough.</p><p>Let follow these steps:</p><h4>1. Install the new Microsoft (Windows) Terminal</h4><p>You can install it from the <a href="https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701">Microsoft Store</a> or from the <a href="https://github.com/microsoft/terminal">GitHub repository</a>. I personally think that is easier if you install it directly from the Store. With just a few clicks, you will get your brand new terminal installed in your Windows.</p><h4>2. Later, you must enable Windows Subsystem for Linux (WSL)</h4><p>This step is easy. Just open your PowerShell with Admin privileges and write the following command to enable WSL:</p><blockquote>Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux</blockquote><p>Later, you have to <strong>restart </strong>your computer.</p><h4>3. Download Ubuntu for Windows</h4><p>Do it directly from the <a href="https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6">Microsoft Store</a>. Easy step.</p><h4>4. Set up your Microsoft Terminal with Ubuntu</h4><p>For that, I invite you to use these following setup:</p><pre>{<br>            &quot;acrylicOpacity&quot; : 0.5,<br>            &quot;closeOnExit&quot; : true,<br>            &quot;colorScheme&quot; : &quot;Scope&quot;,<br>            &quot;commandline&quot; : &quot;wsl.exe -d Ubuntu&quot;,<br>            &quot;cursorColor&quot; : &quot;#39e5a7&quot;,<br>            &quot;cursorShape&quot; : &quot;bar&quot;,<br>            &quot;fontFace&quot; : &quot;Cascadia Code&quot;,<br>            &quot;fontSize&quot; : 12,<br>            &quot;guid&quot; : &quot;{`your guid by default`}&quot;,<br>            &quot;historySize&quot; : 9001,<br>            &quot;icon&quot; : &quot;`insert the url of your prefered icon`&quot;,<br>            &quot;name&quot; : &quot;WSL&quot;,<br>            &quot;padding&quot; : &quot;10, 10, 10, 10&quot;,<br>            &quot;snapOnInput&quot; : true,<br>            &quot;startingDirectory&quot; : &quot;<strong>`insert your default folder (Dev, maybe?)`</strong>&quot;,<br>            &quot;useAcrylic&quot; : false<br>        }</pre><p>As you can see, the name of the <em>colorScheme</em> is Scope, since we are going to use this scheme. Later I will explain how to create the scheme.</p><p>Take care of the “startingDirectory” row, you will have to add your preferred starting directory.</p><h4>5. Install Oh My Zsh plugin</h4><p>For those who don’t know what is <a href="https://ohmyz.sh/">Oh My Zsh</a>, it is an open source framework for Zsh. For me, is one of the best existing tools for consoles out there. Trust me, it is worth to try it.</p><p>To install Oh My Zsh, please, visit their <a href="https://github.com/robbyrussell/oh-my-zsh"><strong>GitHub repository</strong></a> and read the documentation.</p><h4>6. Last step: insert the Scope color scheme</h4><p>Why Scope? <a href="https://scope.ink/?utm_source=medium&amp;utm_medium=cta&amp;utm_campaign=wsl">Scope</a> is my company. In this case, I will add our color scheme, but you are <strong>free to use the colors that you like the most</strong>.</p><blockquote>Scope is a git analytics tool. We help software managers and engineers to better understand the workflow of the code processes to identify bottlenecks, reduce technical debt, compare trends and become more productive.</blockquote><p>For that, go, follow these steps:</p><ol><li>Open Microsoft Terminal.</li><li>Click in the arrow down, to the right of the tab.</li><li>Click on <strong>Settings</strong>.</li><li>A <em>profiles.json</em> file will be opened. Use the code editor you like most. I personally use <a href="https://code.visualstudio.com/">VScode</a>.</li><li>Copy the following commands in the <strong>profiles </strong>section of the json file.</li></ol><pre>{<br>            &quot;background&quot; : &quot;#0d0d24&quot;,<br>            &quot;black&quot; : &quot;#000000&quot;,<br>            &quot;blue&quot; : &quot;#0d0d38&quot;,<br>            &quot;brightBlack&quot; : &quot;#767676&quot;,<br>            &quot;brightBlue&quot; : &quot;#00e0ff&quot;,<br>            &quot;brightCyan&quot; : &quot;#ffd48a&quot;,<br>            &quot;brightGreen&quot; : &quot;#39e5a7&quot;,<br>            &quot;brightPurple&quot; : &quot;#b4009e&quot;,<br>            &quot;brightRed&quot; : &quot;#fa547a&quot;,<br>            &quot;brightWhite&quot; : &quot;#ffffff&quot;,<br>            &quot;brightYellow&quot; : &quot;#ffd48a&quot;,<br>            &quot;cyan&quot; : &quot;#3a96dd&quot;,<br>            &quot;foreground&quot; : &quot;#ffffff&quot;,<br>            &quot;green&quot; : &quot;#bff7e9&quot;,<br>            <strong>&quot;name&quot; : &quot;Scope&quot;</strong>,<br>            &quot;purple&quot; : &quot;#881798&quot;,<br>            &quot;red&quot; : &quot;#fa547a&quot;,<br>            &quot;white&quot; : &quot;#39e5a7&quot;,<br>            &quot;yellow&quot; : &quot;#ffd48a&quot;<br>        },</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-ExsoQHXE5shonXU.png" /></figure><p>There you got. That is the final result. As I said, you are free to use the colors you like most. For that, you have to change the colors on the <strong>Scope color profile </strong>(the commands above).</p><p>Feel free to try different Oh My Zsh themes too! You will find all of them in their <a href="https://github.com/ohmyzsh/ohmyzsh/wiki/Themes">themes gallery</a>.</p><p><strong>Thank you for reading! 👏🏻⭐</strong></p><p>—</p><p>Other articles of mine.</p><ol><li>What I’ve learned in the earlier months of a Startup: <a href="https://medium.com/@alesdonoso/what-ive-learned-in-the-earlier-months-of-a-startup-my-15-tips-19d3f431d443">https://medium.com/@alesdonoso/what-ive-learned-in-the-earlier-months-of-a-startup-my-15-tips-19d3f431d443</a></li><li>The importance of using good coding practices: <a href="https://medium.com/swlh/the-importance-of-using-good-coding-practices-343c5a91e570">https://medium.com/swlh/the-importance-of-using-good-coding-practices-343c5a91e570</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69babbfa4f29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I’ve learned in the earlier months of a Startup. My 15 tips.]]></title>
            <link>https://alesdonoso.medium.com/what-ive-learned-in-the-earlier-months-of-a-startup-my-15-tips-19d3f431d443?source=rss-18fcf7ac4192------2</link>
            <guid isPermaLink="false">https://medium.com/p/19d3f431d443</guid>
            <category><![CDATA[investment]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Ale Donoso]]></dc:creator>
            <pubDate>Wed, 18 Sep 2019 17:00:40 GMT</pubDate>
            <atom:updated>2020-03-17T09:15:00.407Z</atom:updated>
            <content:encoded><![CDATA[<h3>What I’ve learned in the earlier months of a Startup — 15 tips.</h3><p><em>As a Co-Founder of a Startup, I’ve acquired certain knowledge that I’d like to share with you. 15 tips that could help you a lot.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eRHVJcXsKztEx9IR" /><figcaption>Photo by <a href="https://unsplash.com/@room?utm_source=medium&amp;utm_medium=referral">ROOM</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let me present myself. I’m Alejandro and I’m Co-Founder of <a href="https://scope.ink/"><strong>Scope</strong></a>. Since the beginning of the year, I’ve acquired certain knowledge that I’d like to share with you.</p><p>I will talk about the core elements of a tech Startup (since we are a tech one) in its early stage and summarize them in <strong>15 tips</strong>, so these elements will probably be related to <em>product, strategy &amp; business model, marketing, investment and general behavior</em> with your teammates and Co-Founders.</p><p>I hope you find it useful! Let’s go 🚀</p><p><strong>1.-</strong> You don’t know how really important it is to <strong>define a mission and a vision </strong>of a company until you have to take care of your closest decisions. This may have less importance for many people, but for us, it has been extremely valuable to have defined <strong>who we are and where do we want to be</strong> to take several important decisions in the firsts months.</p><p><strong>2.- Define your roles</strong>. I know that in Startups, the roles are just only a title in the LinkedIn account of a person, but when you define roles, you reduce friction within the team when things start to get out of control.</p><p><strong>3.- </strong>It is not only important to define roles but to define <strong>tasks and responsibilities</strong>. Make use of weekly sprints, so you can better organize your teamwork for the entire week.</p><p><strong>4.- </strong>It’s more important to<strong> receive feedback</strong> from users than to try to receive money from potential customers. Try to increase your metrics, know your users, know their behavior, ask them. What do they really need? Have they found problems? Do they find your tool useful?</p><p><strong>5.- </strong>Related to the previous point, it’s tremendously important to <strong>validate the product/MVP</strong> before with users before than with customers. You’ll probably receive valuable feedback so your product will fit better with the market, reducing considerably the <em>time-to-market</em>.</p><p><strong><em>6.- </em></strong><em>Don’t be afraid</em> of <strong>freely </strong>offer your product to your potential users. Instagram was sold to Facebook just because it had more than 10 million active users.</p><p><strong>7.- </strong>This is probably one of the best tips I can give to you and sometimes may be the opposite of what was said above. <strong>Don’t lose your</strong> <strong>focus</strong>. Even if you receive feedback, don’t make quick decisions without a previous hypothesis or enough quantity of demand. Define your own roadmap, try to reach enough quantity of data before work on anything that will probably ask for your scarce resources.</p><blockquote>Sell your business model. Record it in your mind.</blockquote><p><strong>8.- </strong>Talking about resources, always keep in mind that <strong>everything you do cost money and time</strong>. And time is probably the most important resource in the early stage of a Startup. For that, it is incredibly important to have a good strategy of product at the same time as a good user acquisition strategy. Every decision you made, the more you have to invest.</p><p><strong>9.- </strong>Ok, let’s talk about the<em> money</em>. Another one of the best tips I’ll give you here today. <strong>Ask for money when you don’t need it</strong>. To raise an investment round could take you months, literally, and to have an investor deck and a one-pager it’s a must.</p><p><strong>10.- </strong>When you are looking to raise an investment round, one of the most important things you should understand from now is that <strong>investors want you to sell them your business model</strong>. Record it in your mind. They are not looking for a good product (that sometimes too, but it’s not common) but for a good strategy to raise your goals. What are your metrics? How do you pretend to fit-to-market? What is your strategy to reach your goals? How will you sell your product? Who is your target? and etcetera are some of the common questions.</p><blockquote>Garages? We are in 2019!</blockquote><p><strong>11.- Income projections</strong> are useless without a good marketing strategy. Define your plan. Where do you want to be? Is your project scalable? When do you think you reach <em>break-even</em>? Numbers in the early stages are just smoke.</p><p><strong>12.- Don’t lie with the numbers</strong>. That’s the best tip we received from our <a href="https://andalucia.openfuture.org/">acceleration program</a>. If you try to lie with numbers, you are putting a rope around your neck. Don’t fool yourself. Define a good strategy, build your product in a good way and work hard to place your product on the market.</p><p><strong>13.- Forget about garages</strong>. That time in which companies were built in garages has passed. Don’t isolate yourself and your company, it’s much better to work in a good and positive environment. Normally, acceleration programs and co-working spaces are the perfect environments to work on.</p><p><strong>14.- </strong>Be aware of the <strong>opinion of other companions</strong>, but do not get carried away by everything that they say to you nor you make decisions hurried in function of it.</p><p><strong>15.- </strong>And lastly but not least, <strong>if you are a woman</strong>, you will have it complicated in a world of men and probably you will be frustrated. Sadly, on most occasions, my partner and CTO of Scope Mariluz goes unnoticed in conversations and meetings. Very disappointing and I hope it will change in the nearest future. My best wishes to you, warriors 💪🏻.</p><p>These are the most important lessons I have acquired in these first months at <a href="https://scope.ink/"><strong>Scope</strong></a>. I loved sharing my experience with you people 💙.</p><p>I hope you find this publication useful. If you do, <strong>do not forget to give it 50 </strong>👏🏻 and share it with your friends.</p><blockquote>You can read my other publications👇🏻</blockquote><p>· <a href="https://medium.com/swlh/the-importance-of-using-good-coding-practices-343c5a91e570">The importance of using good coding practices</a></p><blockquote>You will find me in:</blockquote><p>🐦 <a href="https://twitter.com/alesdonoso">Twitter</a> / 💼 <a href="http://www.linkedin.com/in/alesdonoso">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19d3f431d443" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The importance of using good coding practices]]></title>
            <link>https://medium.com/swlh/the-importance-of-using-good-coding-practices-343c5a91e570?source=rss-18fcf7ac4192------2</link>
            <guid isPermaLink="false">https://medium.com/p/343c5a91e570</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ale Donoso]]></dc:creator>
            <pubDate>Mon, 15 Jul 2019 11:20:55 GMT</pubDate>
            <atom:updated>2019-07-19T08:20:52.368Z</atom:updated>
            <content:encoded><![CDATA[<h4>Improve your processes.</h4><figure><img alt="Working progress tree by scope.ink" src="https://cdn-images-1.medium.com/max/368/1*EyndLcGJ0c3N8gfNZmnwqA.png" /></figure><p>In code development, as in any other kind of job, it’s very important to organize work, structure efforts and prioritize tasks with the only purpose of having better results.</p><p>Although it’s true that there are several different established practices for a set of programming languages, they are not universalized among programmers and engineers to establish a series of guidelines and make processes follow a logical structure — as for the artisanal process <em>itself</em>.</p><p>Often, engineering teams discover problems only after having launched something; mainly due to factors such as lack of <strong>peer review</strong> and lack of testing resources before it reaches the whole user base.</p><p>It’s then when good practices appear. Although they seem to be universally accepted and known by the community, it’s also true that they are informal rules, learned by so many but rarely followed. Often this is what distinguishes a junior developer from a more seasoned one.</p><blockquote>Many problems occur due to not following good practices during the entire process: from hypothesizing a project to its launch.</blockquote><p>Even more, the results of the research <a href="https://ai.google/research/pubs/pub47853">What Predicts Software Developers’ Productivity?</a> (Emerson Murphy-Hill et al, 2019) from the Google’s Team state that one of the factors with highest variance of response is precisely the “use of best tools and practices”.</p><p>At <a href="https://scope.ink/"><strong>Scope</strong></a> 🔬, define good practices as the establishment of guidelines to follow even before starting to write code. They are a requirement that must be followed and used during the entire creative process.</p><h3>Which are good practices?</h3><p>—</p><p>Based on our experience and trivial knowledge, here is a non-exclusive list of proposed good practices:</p><p><strong>Peer Review:</strong> the reviews system is a fundamental piece in the software industry. Sometimes we ignore that we belong to a collective and as an individual we are subject to mistakes that affect the resulting product and can be prevented by simple read-proof.</p><p>Other times, the blind faith in our teammates can give us more headaches than expected. Peer Review can be the simplest and most effective way to ensure correct and functional products. Always have at least one approval from a code owner before merging to master.</p><p>At that stage we can quickly identify bugs or issues that may degrade our product, user experience or technical debt with very little cost.</p><p><strong>Comments:</strong> comments are always welcome; they are a signal that reviews are well done, and more importantly help other readers than the author to see implicit information hidden in the code structure. Although they are not always necessary, it’s a good way to have an informal documentation on <em>how to do things</em>, improve functionality or signal solutions for different kind of bugs.</p><p>Peer review and comments can be the main way of teaching new hires the way things are done, and learn from each other. Good advice is to tag your PRs by topic (that will depend on what your organization does) i.e. <em>Login</em>, <em>Shopping Cart</em>, <em>Checkout</em>… so developers can navigate your repository via those labels and find formulas on how to achieve a particular result.</p><p><a href="https://help.github.com/en/articles/about-pull-requests"><strong>Pull-Requests system</strong></a><strong>:</strong> and what if we analyze and comment at the same time? The pull-request (PR) system is a perfect way to make code reviews, since you are warning your team that you have done changes or have modified something in the code and those changes need to be reviewed before merging. The PRs are one of the best practices to follow, since they enforce the use of the two previous practices.</p><p><strong>Tags:</strong> usually we forget them. To have a post-it in a punctual moment will help a lot. The tags, in this case, would be like a post-it that we add to our files and with which we identify them. They ease the workflow and help to identify every feature, bugfix or enhancement, streamlining the processes. Additionally, tags are a good way to index the informal documentation that our repo actually is, as said before in the <em>comments</em> section.</p><h3>The benefits of using good practices</h3><p>—</p><p><strong>Improve workflow:</strong> with the use of good practices, processes are greatly streamlined, decreasing costs in time and money. The teams communicate better with each other, they understand what others are doing and prioritize goals depending on the project’s needs.</p><p><strong>Notable improvement of efficiency and productivity:</strong> if the guidelines are accepted by all, logically, the workflow and agility of processes will improve and so will the efficiency and productivity of a developer and of the entire team.</p><p><strong>Reduce costs:</strong> more productivity, more efficiency, dynamic processes → time and money guaranteed.</p><figure><img alt="Tags tree by scope.ink" src="https://cdn-images-1.medium.com/max/296/1*Q6XdkGc4Oo0H2ZMtwYYGzQ.png" /></figure><p><strong>General awareness:</strong> through tags and pull-requests system, developers can have a broad vision of all the processes that are being carried out inside a project.</p><p><strong>Less risks, more security:</strong> we use reviews to ensure code is well built before deploying it. With this, we notably decrease levels of risk when facing bugs. Time invested into reviews is gained by avoiding facing problems. More stability and performance are also a consequence.</p><p><strong>Non hierarchical organization:</strong> tags are very useful to better organize the work. We try ourselves to find tools that help us organize our work, like Trello, Jira or any other. With the use of tags, we have another way to access our directories and files, linked directly with our tasks and features, rather than an arbitrary hierarchy.</p><h3>Some examples with Scope 🔬</h3><p>—</p><p>In <a href="https://scope.ink/"><strong>Scope</strong></a> 🔬, we look to greatly encourage the use of good practices. It’s a strong value and the essence of our Startup. One of our visualizations called “Toggle by Color” shows us a graphic based on the work done by developers in the function of tags which they have been working with.</p><p>Let me show you some examples of public repositories using tags!</p><p><strong><em>microsoft/terminal</em></strong><em> repository</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5EJEStaqmqP-yEgcVEMppg.png" /></figure><p><strong><em>joomla/joomla-cms</em></strong><em> repository</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dYioSu9L520zbjiujw-aZw.png" /></figure><p><strong><em>ant-design/ant-design</em></strong><em> repository</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GBeoC4RDL9JomRdbHiZwiA.png" /></figure><blockquote>Feel free to analyze repositories by yourself asking us for a <a href="https://scope.ink/demo">Demo of Scope</a> 🔬</blockquote><h3>…</h3><p>This text does not pretend to be moralizing but a reflection based on my own experience and learning. Hope this is useful to you!</p><p>Find me on <a href="https://twitter.com/alesdonoso">Twitter</a> 🐦·</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=343c5a91e570" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-importance-of-using-good-coding-practices-343c5a91e570">The importance of using good coding practices</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>