<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dev Rule Book</title><link>https://devrule.dev/</link><description>Recent content on Dev Rule Book</description><generator>Hugo -- gohugo.io</generator><copyright>Copyright © 2021, Martin Majlis; all rights reserved.</copyright><lastBuildDate>Wed, 31 Mar 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://devrule.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>1002: Keep Files Smaller Than You</title><link>https://devrule.dev/r/1002-keep-files-smaller-than-you/</link><pubDate>Wed, 31 Mar 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/1002-keep-files-smaller-than-you/</guid><description>
&lt;p>Think about it when you are writing your code. You do not want to deal with building-sized Filesaurus. The creature with laser-eyes, poisonous breath, invisibility, and teleportation.&lt;/p>
&lt;h2 id="how-to-avoid-it">How To Avoid It&lt;/h2>
&lt;p>No file is large from the beginning. All files are created empty. However, over their existence, they slowly grow. If they are becoming too large, you should split them into multiple smaller files. If you want to split it, you have to figure out several new file names. It could be challenging to come up with names that would describe the content of newly created files. It is sometimes also the reason why splitting is postponed.&lt;/p>
&lt;h2 id="note">Note&lt;/h2>
&lt;p>Do not try to cheat by setting your font size to 1. It will use the font size that any of your colleagues can read.&lt;/p>
&lt;p>You may be thinking, it is better to be chased by a single skyscraper-sized creature than hundreds of small ones, so I should put all the code into a single file. It doesn't work like this. Some people believe, that only a handful of creatures from the size range between 99th to 98th percentile will awake, to make it fair for older developers.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/keep-methods-smaller-than-your-head">Keep Methods Smaller Than Your Head&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/1001-keep-methods-smaller-than-your-head">1001: Keep Methods Smaller Than Your Head&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/1003-follow-naming-convention">Follow Naming Convention: 1003&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>1003: Follow Naming Convention</title><link>https://devrule.dev/r/1003-follow-naming-convention/</link><pubDate>Wed, 31 Mar 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/1003-follow-naming-convention/</guid><description>
&lt;p>Each codebase is using some naming conventions. Either explicitly by following some document, or implicitly by following patterns already used.&lt;/p>
&lt;p>It should always look like the file was written by a single person. In the example below you can see how it should not look like:&lt;/p>
&lt;div class="highlight">&lt;pre class="chroma">&lt;code class="language-python" data-lang="python">&lt;span class="ln">1&lt;/span>&lt;span class="n">num_legs&lt;/span> &lt;span class="o">=&lt;/span> &lt;span class="mi">6&lt;/span>
&lt;span class="ln">2&lt;/span>&lt;span class="n">wings&lt;/span> &lt;span class="o">=&lt;/span> &lt;span class="mi">2&lt;/span>
&lt;span class="ln">3&lt;/span>&lt;span class="n">number_of_stings&lt;/span> &lt;span class="o">=&lt;/span> &lt;span class="mi">1&lt;/span>
&lt;span class="ln">4&lt;/span>&lt;span class="n">no_ears&lt;/span> &lt;span class="o">=&lt;/span> &lt;span class="mi">2&lt;/span>
&lt;span class="ln">5&lt;/span>&lt;span class="n">nr_hands&lt;/span> &lt;span class="o">=&lt;/span> &lt;span class="mi">0&lt;/span>
&lt;span class="ln">6&lt;/span>&lt;span class="n">eye_count&lt;/span> &lt;span class="o">=&lt;/span> &lt;span class="mi">2&lt;/span>&lt;/code>&lt;/pre>&lt;/div>
&lt;p>Before you start contributing to the existing codebase, it is always better to get familiar with its style. You can search in the code to figure out if somebody has already used a similar name.&lt;/p>
&lt;h2 id="naming-conventions">Naming Conventions&lt;/h2>
&lt;ul>
&lt;li>Python
&lt;ul>
&lt;li>&lt;a href="https://www.python.org/dev/peps/pep-0008/#naming-conventions">PEP 8 - Style Guide for Python Code&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://google.github.io/styleguide/pyguide.html#316-naming">Google Python Style Guide&lt;/a>&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/use-search-oriented-programming">Use Search-oriented Programming&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/1002-keep-files-smaller-than-you">1002: Keep Files Smaller Than You&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&amp;nbsp;
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0013: Be Aware of Bikeshedding</title><link>https://devrule.dev/r/0013-be-aware-of-bikeshedding/</link><pubDate>Thu, 18 Mar 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0013-be-aware-of-bikeshedding/</guid><description>
&lt;p>Law of triviality is C. Northcote Parkinson's 1957 argument that people within an organization commonly or typically give disproportionate weight to trivial issues.&lt;/p>
&lt;blockquote>
&lt;p>&amp;quot;The time spent on any item of the agenda will be in inverse proportion to the sum [of money] involved.&amp;quot; A reactor is so vastly expensive and complicated that an average person cannot understand it (see ambiguity aversion), so one assumes that those who work on it understand it. On the other hand, everyone can visualize a cheap, simple bicycle shed, so planning one can result in endless discussions because everyone involved wants to add a touch and show personal contribution.&lt;/p>
&lt;/blockquote>
&lt;p>You have most likely experienced during meetings as was pointed out by Parkinson. But this is also happening during code reviews.&lt;/p>
&lt;h2 id="law">Law&lt;/h2>
&lt;p>The number of comments is in reverse proportion to the number of changed lines.&lt;/p>
&lt;h2 id="easy-pull-requests">Easy Pull Requests&lt;/h2>
&lt;p>You have made some trivial change that is slightly improving the codebase. You were expecting a smooth review process, but it got stuck. Everybody had an idea how it could have been done slightly differently. There was endless discussion and instead of a quick win, it was very painful.&lt;/p>
&lt;p>There are several ways how you can try to mitigate this situation. You can either point out, that the time is not effectively used, or you can abandon that change since it is no longer worth the effort.&lt;/p>
&lt;p>This could extremely annoying especially when this was your &lt;a href="confidence-booster">confidence booster&lt;/a>.&lt;/p>
&lt;h2 id="complicated-pull-requests">Complicated Pull Requests&lt;/h2>
&lt;p>This law also demonstrates in pull requests that are changing something important and complicated. It is hard to gather enough mental energy to correctly review those complicated yet important parts. It is way easier to comment just on formatting, naming, or some other trivial stuff. It does not mean that complicated code could be written terribly. It means that if you have created such a pull request, you should not be surprised, that instead of having discussions about those complicated parts, a lot of discussions could be around those trivial parts.&lt;/p>
&lt;p>In these large pull requests, there are portions of the code that are doing the actual work, and the rest of the code is just supporting it. By pointing out those important parts to your reviewers, you can make their life easier. It allows them to focus their energy on these important sections. They use their energy more wisely and you get better feedback. This is a win-win situation for everybody.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/have-confidence-boosters-in-your-back-pocket">Have Confidence Boosters In Your Back Pocket&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-be-blocker">Don't Be Blocker&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-be-blocked">Don't be Blocked&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="links">Links&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://en.wikipedia.org/wiki/Law_of_triviality">Law of Triviality&lt;/a>&lt;/li>
&lt;li>&lt;a href="http://phk.freebsd.dk/sagas/bikeshed/#the-bikshed-email">Bike shed e-mail&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://thedecisionlab.com/biases/bikeshedding/">Bikeshedding&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0012-have-confidence-boosters-in-your-back-pocket">0012: Have Confidence Boosters In Your Back Pocket&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/1000-use-search-oriented-programming">Use Search-oriented Programming: 1000&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0012: Have Confidence Boosters in your Back Pocket</title><link>https://devrule.dev/r/0012-have-confidence-boosters-in-your-back-pocket/</link><pubDate>Wed, 17 Mar 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0012-have-confidence-boosters-in-your-back-pocket/</guid><description>
&lt;p>Every day may not be good. Sometimes when you get stuck, nothing works as expected, your morale and self-confidence may get low.&lt;/p>
&lt;p>It could happen to everybody, and it is completely fine. You should not, however, stay in this state for too long. To bounce back you should know what works for you. One such thing could be confidence boosters.&lt;/p>
&lt;h2 id="confidence-booster">Confidence Booster&lt;/h2>
&lt;p>Confidence booster is a small task, where you have a good understanding of the problem, it is straightforward, and you can finish it in few minutes.
By finishing it, you get a feeling of accomplishment, that you can still finish your tasks. This gives you new energy to finish your original task with which you have struggled.&lt;/p>
&lt;h2 id="pitfalls">Pitfalls&lt;/h2>
&lt;p>This approach has several pitfalls. By working on some completely new unrelated task you may be prolonging the time required to finish the original task. To reduce that always time box yourself, so you do not spend a whole day on it.
Another pitfall is that this could lead to some very long discussions because of the bike-shed effect. Be prepared for this and be prepared to abandon this task.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/bike-shedding">Be Aware of Bike Shedding&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0011-make-small-steps">0011: Make Small Steps&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0013-be-aware-of-bikeshedding">Be Aware of Bike Shedding: 0013&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0011: Make Small Steps</title><link>https://devrule.dev/r/0011-make-small-steps/</link><pubDate>Tue, 16 Mar 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0011-make-small-steps/</guid><description>
&lt;p>Finishing a task is a daunting challenge. It is not easy to figure out where to start, not to lose direction, and get to the finish.&lt;/p>
&lt;p>You can apply this rule on different levels. You can divide large work items into smaller tasks. You can split single routine into many smaller ones.&lt;/p>
&lt;h2 id="tasks">Tasks&lt;/h2>
&lt;p>Splitting large task into smaller ones provides several advantages:&lt;/p>
&lt;ul>
&lt;li>you can estimate required effort more precisely&lt;/li>
&lt;li>you can split work among multiple people&lt;/li>
&lt;li>you can better track progress&lt;/li>
&lt;li>you can have a feeling of accomplishment more often&lt;/li>
&lt;/ul>
&lt;p>Scrum recommends to have tasks smaller than &lt;a href="https://scrumguides.org/scrum-guide.html#sprint-planning">1 day&lt;/a>.&lt;/p>
&lt;h2 id="coding">Coding&lt;/h2>
&lt;p>Breaking down your task into several smaller methods makes your life easier. When you are implementing each method individually, you can:&lt;/p>
&lt;ul>
&lt;li>figure out what type of input is easy to digest and what type of output will be easily digestible by callers&lt;/li>
&lt;li>focus on expected inputs and outputs&lt;/li>
&lt;li>make the function more testable&lt;/li>
&lt;/ul>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/be-open">Be Open&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/start-simply">Start Simply&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/simply-start">Simply Start&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0010-multitask-with-caution">0010: Multitask with Caution&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0012-have-confidence-boosters-in-your-back-pocket">Have confidence boosters in your back pocket: 0012&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>1000: Use Search-oriented Programming</title><link>https://devrule.dev/r/1000-use-search-oriented-programming/</link><pubDate>Fri, 12 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/1000-use-search-oriented-programming/</guid><description>
&lt;p>The idea of search-oriented programming is based on two premises:&lt;/p>
&lt;ol>
&lt;li>Every useful class, method, or attribute has been used at least once. If nobody is using it, do not use it either.&lt;/li>
&lt;li>Every line in mature software has been checked by multiple people. Therefore every class, method, or variable has a descriptive and understandable name.&lt;/li>
&lt;/ol>
&lt;h2 id="search-in-existing-code">Search In Existing Code&lt;/h2>
&lt;p>If you know the name of the class or function you can try to &lt;a href="https://www.google.com/search?q=wikipediaapi.Wikipedia">google it&lt;/a>. You will get most likely just a &lt;a href="https://pypi.org/project/Wikipedia-API/">package page&lt;/a>, &lt;a href="https://wikipedia-api.readthedocs.io/en/latest/wikipediaapi/api.html#wikipediaapi.WikipediaPage">documentation&lt;/a>, or &lt;a href="https://stackoverflow.com/questions/34869597/wikipedia-api-for-python/47793106#47793106">Stackoverflow questions&lt;/a>. This is a good start but you can get better results if you use more specialized search engines. Specific examples will help you to learn not only about the entity itself but also about other entities that are used nearby.&lt;/p>
&lt;h2 id="where-to-search">Where To Search&lt;/h2>
&lt;ol>
&lt;li>Search in your project. It is just one keyboard shortcut away and it is the best code that you can find. It has passed code review, you can find relevant pull requests, or even talk with people who have written that code. Many IDE allows you to easily find all usages of the entity.&lt;/li>
&lt;li>Search in repositories of your organization. It could take a little bit longer and you may not be able to talk with the others of that code. On the other side, there is a greater chance that you will find something.&lt;/li>
&lt;li>Search in communication in your company. If you have problems with figuring out how it should be used, you are for sure not the first one. Try to search in wikis, Slack, e-mails, etc.&lt;/li>
&lt;li>Search in the source code of that project. If it is a public method, then it should be covered at least with unit tests. By finding these &lt;a href="https://github.com/martin-majlis/Wikipedia-API/blob/master/tests/wikipedia_page_test.py#L23">tests&lt;/a>, you can learn what was the intended usage by the authors.&lt;/li>
&lt;li>Search in open source repositories. GitHub allows you to search in their 100M+ repositories. So you will find for sure many good examples. If you compare search &lt;a href="https://github.com/search?l=Python&amp;amp;p=5&amp;amp;q=wikipediaapi.Wikipedia&amp;amp;type=Code">GitHub results&lt;/a> with initial Google results you can that it is much more useful.&lt;/li>
&lt;/ol>
&lt;p>Another advantage of using GitHub is that you not only find the function itself and its friends, but you will also find how it is used in tests. Documentation of how to use &lt;code>requests.Session&lt;/code> is &lt;a href="https://requests.readthedocs.io/en/master/user/advanced/#session-objects">short&lt;/a>, but since it is a lot, you will find many &lt;a href="https://github.com/search?q=%22requests.Session%22+import+requests+Session&amp;amp;type=Code">examples&lt;/a>.&lt;/p>
&lt;h2 id="guess-names">Guess Names&lt;/h2>
&lt;p>Since the code was written by sane people and reviewed by other people, there is a very high chance that used names would be descriptive. Therefore you can always try to search for possible class or method names to see if anything useful is there.&lt;/p>
&lt;p>If you are searching for code related to login workflow, you can try to search for string &lt;code>login&lt;/code>. If you want to find code related to manipulation with items in a shopping cart, you can search for words like &lt;code>cart&lt;/code>, &lt;code>basket&lt;/code>, or &lt;code>order&lt;/code>.&lt;/p>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0011-make-small-steps">0011: Make Small Steps&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/1001-keep-methods-smaller-than-your-head">Keep Methods Small Than Your Head: 1001&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>1001: Keep Methods Smaller Than Your Head</title><link>https://devrule.dev/r/1001-keep-methods-smaller-than-your-head/</link><pubDate>Thu, 11 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/1001-keep-methods-smaller-than-your-head/</guid><description>
&lt;p>Discussions about ideal function lengths are never-ending. My rule of thumb is that the ideal function should fit into your head. If it is longer, it will not fit there, and therefore you cannot reason about it.&lt;/p>
&lt;p>To determine if the function is too long, place your head next to the screen, and compare its length with the size of your head. In the ideal case you should be taking into account only the part where is your brain located.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/keep-files-smaller-than-you">Keep Files Smaller Than You&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="external-links">External Links&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://softwareengineering.stackexchange.com/questions/133404/what-is-the-ideal-length-of-a-method-for-you">SO: What is the ideal length of a method for you?&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://martinfowler.com/bliki/FunctionLength.html">Martin Fowler: Function Length&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/1000-use-search-oriented-programming">1000: Use Search-oriented Programming&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/1002-keep-files-smaller-than-you">Keep Files Smaller Than You: 1002&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0007: Don't Be Blocked</title><link>https://devrule.dev/r/0007-dont-be-blocked/</link><pubDate>Wed, 10 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0007-dont-be-blocked/</guid><description>
&lt;p>Getting your work done is very important. Therefore it is necessary to make sure that you can proceed with your tasks smoothly. To ensure that it is useful to look ahead and think about your dependencies. It is important to keep track of the work of your teammates to be able to see early if they are progressing as expected. If it looks that the parts on which you depend on will not be available on time, try to figure out if the work could be somehow divided or reduced, that part important for you will be finished on time.&lt;/p>
&lt;p>If you cannot help with finishing your dependencies earlier, you can either try to use mocked version, or work on something else.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/it-is-teamwork">It is teamwork&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-be-blocker">Don't be blocker&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0006-be-kind">0006: Be Kind&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0008-dont-be-blocker">Don't Be Blocker: 0008&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0008: Don't Be Blocker</title><link>https://devrule.dev/r/0008-dont-be-blocker/</link><pubDate>Wed, 10 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0008-dont-be-blocker/</guid><description>
&lt;p>Getting your team's work done is very important. Therefore it is necessary to make sure that you are not blocking others. Keep track of work of your teammates, so you know when your work will be needed by others. If you find out that somebody will need your work when it will not be done, reach out to them. Try to figure out, as team, how the work could be reorganized to make sure that there no unnecessary delays.&lt;/p>
&lt;p>If you are reviewer of some pull request, review them as soon as possible. That task is almost done and just your review is preventing it from being finished. It also pushing the author to greater degree of multitasking. This could be especially dangerous if there will be lot changes needed in that PR.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/it-is-teamwork">It is teamwork&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-be-blocked">Don't be blocked&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0007-dont-be-blocked">0007: Don't Be Blocked&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0009-reduce-round-trips">Reduce Round Trips: 0009&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0009: Reduce Round Trips</title><link>https://devrule.dev/r/0009-reduce-round-trips/</link><pubDate>Wed, 10 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0009-reduce-round-trips/</guid><description>
&lt;p>As developer you will be very often communicating with other parties asynchronously. Typical examples of such communication are email, messages, as well as discussions in pull requests or document. It may take from several minutes, to hours, or even several days before you will get reaction to your actions back. If the other party is replaying once per day, you can be able to achieve only 4 iterations in a week. This is not too much.&lt;/p>
&lt;h2 id="sample-scenario">Sample Scenario&lt;/h2>
&lt;p>There could be discussion like this in pull request or in chat and it could take days to get to the end.&lt;/p>
&lt;ul>
&lt;li>Alice: We should solve it differently.&lt;/li>
&lt;li>Bob: How differently?&lt;/li>
&lt;li>Alice: Approach Y is better.&lt;/li>
&lt;li>Bob: Why is approach Y better?&lt;/li>
&lt;li>Alice: Approach Y will help us in the future.&lt;/li>
&lt;li>Bob: How it will help us in the future?&lt;/li>
&lt;li>Alice: With integration.&lt;/li>
&lt;li>Bob: With which integration?&lt;/li>
&lt;/ul>
&lt;p>From this conversation we can see that:&lt;/p>
&lt;ul>
&lt;li>Alice has better of the knowledge of the system, its surroundings and its future.&lt;/li>
&lt;li>Bob knows very little about the system.
*.Alice is busy.&lt;/li>
&lt;li>Alice is not realizing how much context is Bob missing.&lt;/li>
&lt;li>Bob is asking very short and general questions.&lt;/li>
&lt;li>Alice and Bob may be frustrated that there is no progress.&lt;/li>
&lt;/ul>
&lt;h2 id="how-to-get-from-this">How To Get From This&lt;/h2>
&lt;p>If you are in this situation you have two different options:&lt;/p>
&lt;h3 id="use-synchronous-communication">Use Synchronous Communication&lt;/h3>
&lt;p>Synchronous communication has advantage of very low latency and therefore with the same approach you can get to the result more quickly. On the other side it has also several disadvantages. Knowledge that is transferred is usually not recorded anywhere, so it is lost for any other party involved. Cecile may show up and the same communication will start again. When Alice or Bob are not available this knowledge may be lost permanently.&lt;/p>
&lt;h3 id="improve-your-asynchronous-communication">Improve Your Asynchronous Communication&lt;/h3>
&lt;p>Main advantage of asynchronous communication is that we have record what was discussed and what was the outcome. If it was even public it can server as form of documentation. To be able to achive this both parties has to approach this with such goal in their mind. First step should be provide more context, motivation, and expected outcomes.&lt;/p>
&lt;h2 id="general-tricks">General tricks:&lt;/h2>
&lt;ul>
&lt;li>Make sure that pronouns like - &amp;quot;it&amp;quot; or &amp;quot;that&amp;quot; - refers to just single items. If there is more of them, try to be more specific, to restrict it more. &amp;quot;It is not working.&amp;quot; vs &amp;quot;Search form is not working.&amp;quot;&lt;/li>
&lt;li>Answer on the expected questions in advance. &amp;quot;Search form is not working.&amp;quot; vs &amp;quot;Search form is not working. I have tried to refresh the page and also multiple browsers.&amp;quot;&lt;/li>
&lt;li>Be as specific as possible. &amp;quot;I was searching Google on Google.com. I have tried multiple browsers and all of them are showing 500 Internal Server Error&amp;quot;.&lt;/li>
&lt;/ul>
&lt;p>Now this could be resolved quickly. Everybody knows that searching for google on google.com will break the Internet, so it is expected behavior.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/it-is-teamwork">It is teamwork&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/be-open">Be Open&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-beb-blocked">Don't Be Blocked&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-beb-blocker">Don't Be Blocker&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0008-dont-be-blocker">0008: Don't Be Blocker&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0010-multitask-with-caution">Multitask With Caution: 0010&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0010: Multitask With Caution</title><link>https://devrule.dev/r/0010-multitask-with-caution/</link><pubDate>Wed, 10 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0010-multitask-with-caution/</guid><description>
&lt;p>Working on multiple tasks is decreasing your chance that you &lt;a href="https://devrule.dev/r/dont-be-blocked%5D">will be blocked&lt;/a> and increasing the chance that you &lt;a href="https://devrule.dev/r/dont-be-blocker">will become a blocker&lt;/a>.&lt;/p>
&lt;p>Furthermore, every task you are working on is adding additional cost required by context switching. In the most extreme case, you may spend all your day just context switching and not have any time to get to the zone and get your job done.&lt;/p>
&lt;p>Multitasking is similar to juggling. When you overload yourself, all balls could end up on the floor, not just the extra one.&lt;/p>
&lt;p>People who claim that they are good at multitasking are usually not good at multitasking. (citation needed)&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/it-is-teamwork">it-is-teamwork&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-beb-blocked">Don't Be Blocked&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/dont-beb-blocker">Don't Be Blocker&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0009-reduce-round-trips">0009: Reduce Round Trips&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0011-make-small-steps">Make Small Steps: 0011&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0004: It Is Teamwork</title><link>https://devrule.dev/r/0004-it-is-teamwork/</link><pubDate>Sun, 07 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0004-it-is-teamwork/</guid><description>
&lt;p>Creating software systems requires cooperation of many people. It is important to observe other people to learn about their role, motivations, strengths, and weaknesses.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/be-open">Be open&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0003-ship-stuff">0003: Ship Stuff&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0005-be-open">Be Open: 0005&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0005: Be Open</title><link>https://devrule.dev/r/0005-be-open/</link><pubDate>Sun, 07 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0005-be-open/</guid><description>
&lt;p>Good communication is the essential part for any successfully finished project.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/it-is-teamwork">it-is-teamwork&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0003-ship-stuff">0003: Ship Stuff&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0006-be-kind">Be Kind: 0006&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0006: Be Kind</title><link>https://devrule.dev/r/0006-be-kind/</link><pubDate>Sun, 07 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0006-be-kind/</guid><description>
&lt;p>It will for sure cause no harm if you will be kind on other people. :D&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/it-is-teamwork">it-is-teamwork&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0005-be-open">0005: Be Open&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0007-dont-be-blocked">Don't Be Blocked: 0007&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0001: Simply Start</title><link>https://devrule.dev/r/0001-simply-start/</link><pubDate>Sat, 06 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0001-simply-start/</guid><description>
&lt;p>Starting is the most important step for finishing anything. Without a start, there is no finish. Do not be afraid to start.&lt;/p>
&lt;h2 id="where-to-start">Where to Start&lt;/h2>
&lt;p>There is a lot of uncertainty at the beginning that could be overwhelming. Do not get overwhelmed and create a list of potential first tasks. These tasks will differ by their importance, size, dependencies, difficulty, and required understanding of the problem. There are many different strategies how to pick the first one.&lt;/p>
&lt;h3 id="pick-deal-breaker">Pick Deal Breaker&lt;/h3>
&lt;p>If you are not sure if the task could be even achieved, you should start with the task on which your success depends. If you manage to solve it, then you can work on the remaining tasks. If you cannot solve it, then you should either try to figure out some workaround or stop.&lt;/p>
&lt;h3 id="pick-task-that-helps-with-understanding">Pick Task That Helps With Understanding&lt;/h3>
&lt;p>If there is a lot of uncertainty, then starting with a task that helps you to increase your understanding, is a reasonable idea. This however often requires clarification from other people, which could slow you at the beginning. It is worth it since there is no point in going in the wrong direction.&lt;/p>
&lt;h3 id="pick-simple-task">Pick Simple Task&lt;/h3>
&lt;p>A small task with no dependencies that you can finish with ease is a good starter. You should complete it quickly without any problems. The advantage is that it can give you a feeling of accomplishment. This approach has some disadvantages as well. You can throw away all your effort, if there are some deal breakers, or if you have misunderstood the problem.&lt;/p>
&lt;h2 id="it-is-fine-to-stop">It is Fine to Stop&lt;/h2>
&lt;p>If you have started quickly, you can also find out very quickly, that it was not a good start. Either the idea was bad, it is more complicated than it looked at in the beginning, or there is a better idea.
In your decision, you should not consider your previous effort. If you do so, be aware of &lt;a href="https://en.wikipedia.org/wiki/Sunk_cost">sunk cost fallacy&lt;/a>.&lt;/p>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/start-simply">Start Simply&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/make-small-steps">Make Small Steps&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://devrule.dev/r/reduce-round-trips">Reduce Round Trips&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="conflicting">Conflicting&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/understand-requirements">understand requirements&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&amp;nbsp;
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0002-start-simply">Start Simply: 0002&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0002: Start Simply</title><link>https://devrule.dev/r/0002-start-simply/</link><pubDate>Sat, 06 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0002-start-simply/</guid><description>
&lt;p>Starting with the simple version allows you to better understand the problem.&lt;/p>
&lt;ul>
&lt;li>Start with the main workflow.&lt;/li>
&lt;li>Each problem can be divided into multiple problems based on their certainty. Start with the most certain part.&lt;/li>
&lt;/ul>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/simply-start">simply start&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="conflicting">Conflicting&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/understand-requirements">understand requirements&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0001-simply-start">0001: Simply Start&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0003-ship-stuff">Ship Stuff: 0003&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item><item><title>0003: Ship Stuff</title><link>https://devrule.dev/r/0003-ship-stuff/</link><pubDate>Sat, 06 Feb 2021 00:00:00 +0000</pubDate><guid>https://devrule.dev/r/0003-ship-stuff/</guid><description>
&lt;p>Shipping stuff is crucial. If the product is not used by people, it is not providing any value to the word.&lt;/p>
&lt;p>There is always something that could improved, that could be done differently. Ship it first and observe.&lt;/p>
&lt;h2 id="quotes">Quotes&lt;/h2>
&lt;blockquote>
&lt;p>Real artists ship.&lt;br>
— &lt;cite>&lt;a href="https://en.wikiquote.org/wiki/Steve_Jobs#1980s">Steve Jobs&lt;/a>&lt;/cite>&lt;/p>
&lt;/blockquote>
&lt;blockquote>
&lt;p>Perfect is the enemy of good,&lt;br>
— &lt;cide>&lt;a href="https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good">Voltair&lt;/a>&lt;/cite>&lt;/p>
&lt;/blockquote>
&lt;h2 id="related">Related&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/simply-start">Simply Start&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="conflicting">Conflicting&lt;/h2>
&lt;ul>
&lt;li>&lt;a href="https://devrule.dev/r/understand-requirements">understand requirements&lt;/a>&lt;/li>
&lt;/ul>
&lt;table style="width: 100%; border: 0px; border-top: 1px solid">
&lt;tr>
&lt;td style="text-align: left; border: 0px; padding-left: 0px;">
&lt;a href="https://devrule.dev/r/0002-start-simply">0002: Start Simply&lt;/a>
&lt;/td>
&lt;td style="text-align: right; border: 0px; padding-right: 0px;" >
&lt;a href="https://devrule.dev/r/0004-it-is-teamwork">It Is Teamwork: 0004&lt;/a>
&lt;/td>
&lt;/tr>
&lt;/table></description></item></channel></rss>