<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Management - Tag - Nuno Sousa&#39;s Corner</title>
        <link>https://www.nunomtsousa.com/tags/management/</link>
        <description>Management - Tag - Nuno Sousa&#39;s Corner</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>nuno.mt.sousa@gmail.com (Nuno Sousa)</managingEditor>
            <webMaster>nuno.mt.sousa@gmail.com (Nuno Sousa)</webMaster><lastBuildDate>Mon, 01 Apr 2024 18:31:18 &#43;0000</lastBuildDate><atom:link href="https://www.nunomtsousa.com/tags/management/" rel="self" type="application/rss+xml" /><item>
    <title>Growing a Software Development Team</title>
    <link>https://www.nunomtsousa.com/posts/2024-04-01-growingsoftwareteam/</link>
    <pubDate>Mon, 01 Apr 2024 18:31:18 &#43;0000</pubDate>
    <author>nuno.mt.sousa@gmail.com (Nuno Sousa)</author>
    <guid>https://www.nunomtsousa.com/posts/2024-04-01-growingsoftwareteam/</guid>
    <description><![CDATA[<h2 id="a-view-of-many-years-in-the-trenches">A View Of Many Years In The Trenches</h2>
<p>Have you thought about how to grow a Software Development Team? How do you get juniors into seniors? How do you keep seniors motivated and engaged, not feeling the need to look for jobs elsewhere or afraid of becoming obsolete? This is not an easy subject, but a question on my last day of work at my last company got me thinking about it, and I will add my two cents to the discussion. Take this with a grain of salt; after all, I am no expert, and I am most likely wrong. Sorry!</p>]]></description>
</item>
<item>
    <title>Defending The Case for Test Driven Development</title>
    <link>https://www.nunomtsousa.com/posts/2024-02-14-defendingtdd/</link>
    <pubDate>Sat, 24 Feb 2024 18:26:22 &#43;0000</pubDate>
    <author>nuno.mt.sousa@gmail.com (Nuno Sousa)</author>
    <guid>https://www.nunomtsousa.com/posts/2024-02-14-defendingtdd/</guid>
    <description><![CDATA[<p>Have you ever heard of Test Driven Development? You probably have. You have also probably seen people advocate for it and against it. I believe it has come the time for us to own it as a technique that enables us to make better software. Just remember not to go too dogmatic on it, to introduce some key performance indicators (a.k.a. code coverage), and to turn it into a bottleneck and an impediment to your progress. After all, we have to use the right tool and technique for each job, so don’t go on the radical side.</p>]]></description>
</item>
</channel>
</rss>
