<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>jwaghetti</title>
    <link>http://waghetti.com/</link>
    <description>Recent content on jwaghetti</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Jun 2021 16:00:00 -0300</lastBuildDate><atom:link href="http://waghetti.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Conflict as an Impediment</title>
      <link>http://waghetti.com/posts/2021/06/conflict-as-an-impediment/</link>
      <pubDate>Fri, 04 Jun 2021 16:00:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/06/conflict-as-an-impediment/</guid>
      <description>&lt;p&gt;Conflict in a team can range from simple misunderstandings to
hurt feelings and personal attacks.&lt;/p&gt;
&lt;p&gt;Most of the time, conflict
provides a constructive basis for a high-performance team.
In other cases, it becomes an impediment. As such, it
must be removed.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Fake Cross-Functionality</title>
      <link>http://waghetti.com/posts/2021/05/fake-cross-functionality/</link>
      <pubDate>Thu, 20 May 2021 23:00:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/05/fake-cross-functionality/</guid>
      <description>&lt;p&gt;Imagine a team where every member can execute every task with
near-perfection results. Is it nice? Is it possible?&lt;/p&gt;
&lt;p&gt;In this article I&amp;rsquo;ll discuss Cross-Functionality
and a dysfunction I call Fake Cross-Functionality.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>White-Box Testing is Fragile</title>
      <link>http://waghetti.com/posts/2021/05/white-box-testing-is-fragile/</link>
      <pubDate>Tue, 11 May 2021 00:46:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/05/white-box-testing-is-fragile/</guid>
      <description>&lt;p&gt;White-box tests expose the internals of your code,
instead of just the behavior. In this
article I argue why this kind of testing may
lead to fragile tests (the ones that break
even if no bugs were introduced).&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Velocity Without Direction is Speed</title>
      <link>http://waghetti.com/posts/2021/03/velocity-without-direction-is-speed/</link>
      <pubDate>Thu, 18 Mar 2021 00:30:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/03/velocity-without-direction-is-speed/</guid>
      <description>&lt;p&gt;In agile environments, &lt;strong&gt;velocity&lt;/strong&gt; is commonly used to measure how much a team delivers each iteration. In this article
I will relate this metric with concepts from classical mechanics, telling
why you should always consider velocity towards your
goals instead of going as fast as you can.&lt;/p&gt;
&lt;p&gt;The objective of this article is not to explain what velocity is. I assume you already know this concept. If you would
like a more detailed article about velocity, please let me know in the comments or any other options of &lt;a href=&#34;http://waghetti.com/pages/contact/&#34; title=&#34;contact&#34;&gt;contact&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Know Your Tools</title>
      <link>http://waghetti.com/posts/2021/01/know-your-tools/</link>
      <pubDate>Mon, 25 Jan 2021 00:45:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/01/know-your-tools/</guid>
      <description>&lt;p&gt;I usually talk a lot about the importance of understanding
concepts. They are crucial as a common ground for discussion
and collaboration to achieve the team&amp;rsquo;s goals.&lt;/p&gt;
&lt;p&gt;In this article, I&amp;rsquo;ll talk about tools, telling my story on
how I became dependent on Integrated Development
Environments (IDEs) and what I did about it.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Delivering Incrementally</title>
      <link>http://waghetti.com/posts/2021/01/delivering-incrementally/</link>
      <pubDate>Tue, 19 Jan 2021 00:00:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/01/delivering-incrementally/</guid>
      <description>&lt;p&gt;Agile methodologies are based on incremental and
iterative product development. Just breaking the
product into &lt;em&gt;parts&lt;/em&gt; is not what you want. Each
of these &lt;em&gt;parts&lt;/em&gt; must have value: if they don&amp;rsquo;t,
you are not iterating - you&amp;rsquo;re just in a
disguised &lt;em&gt;waterfall&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Static Dependency Injection</title>
      <link>http://waghetti.com/posts/2021/01/static-dependency-injection/</link>
      <pubDate>Sat, 09 Jan 2021 00:30:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/01/static-dependency-injection/</guid>
      <description>&lt;p&gt;In this article I will show you a pattern I call
&lt;em&gt;static dependency injection&lt;/em&gt;. This can be used to
automatically include new functionality to a module
by just creating new classes - not modifying any line
of existing code.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>SOLID Principles</title>
      <link>http://waghetti.com/posts/2021/01/solid-principles/</link>
      <pubDate>Fri, 08 Jan 2021 02:00:00 -0300</pubDate>
      
      <guid>http://waghetti.com/posts/2021/01/solid-principles/</guid>
      <description>&lt;p&gt;In this first article of the blog I will talk about SOLID Principles.
These are principles for software development consolidated by
&lt;a href=&#34;http://cleancoder.com/&#34;&gt;Bob Martin&lt;/a&gt;. Material about them you can
find it everywhere, so I&amp;rsquo;ll keep mine short.&lt;/p&gt;
&lt;p&gt;My initial idea was to talk about some patterns I use (or thought of) to
overcome design issues. To show their value, it would be nice to relate
them to the SOLID principles. That&amp;rsquo;s why this first article&amp;rsquo;s subject.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title></title>
      <link>http://waghetti.com/pages/aboutme/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://waghetti.com/pages/aboutme/</guid>
      <description>About Me Hello all,
I&amp;rsquo;m Jean Waghetti, agilist and software developer based in Porto Alegre/RS, Brazil. By the way, you can call me Jiba.
Even having a degree in electrical engineering, I always worked with software development.
I started my carreer as an intern in 2010. With this professional experience, I recognize software development as one of my passions.
By 2015, I got another passion: agility. And it really drives the way I work and and also how I live</description>
    </item>
    
    <item>
      <title></title>
      <link>http://waghetti.com/pages/aboutsite/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://waghetti.com/pages/aboutsite/</guid>
      <description>About Site Personal website of Jean Waghetti. Hosted at https://waghetti.com.
Thoughts on agility and software development (not restricted to only that).
Content is licensed via Creative Commons Attribution 4.0 International (CC-BY 4.0).
Copyright 2021 Jean Waghetti.
Content in English and Portuguese. Switch language version in the menu or in the article (you may see a link for the translation in the article header if it exists).
Discussion makes things more interesting and I would love to hear your opinion.</description>
    </item>
    
    <item>
      <title></title>
      <link>http://waghetti.com/pages/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>http://waghetti.com/pages/contact/</guid>
      <description>Contact For stuff related to the posts, best option is a comment in the post itself. Comments are powered by Utterances. You need to login to Github to comment.
You can also use the social links listed in the menu.</description>
    </item>
    
  </channel>
</rss>
