<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Trisha Gee on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/trisha-gee/</link><description>Articles written by Trisha Gee on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 24 Feb 2025 12:23:42 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/trisha-gee/index.xml" rel="self" type="application/rss+xml"/><item><title>Foojay Podcast #67: Writing a book and fame and fortune!</title><link>https://foojayio.github.io/website/today/foojay-podcast-67/</link><pubDate>Mon, 24 Feb 2025 12:23:42 +0000</pubDate><guid>https://foojayio.github.io/website/today/foojay-podcast-67/</guid><description>&lt;p&gt;Let me share a personal story. I started experimenting with Java on a Raspberry Pi about five years ago and blogged a few articles about it. But the more I experimented, the more I wrote down, and eventually, I had written a book&amp;hellip; I worked on it for six months in a row, every evening and a lot of weekends. But the moment I received the box with my author copies was an incredible feeling. Holding a paper book with your name is a special moment.&lt;/p&gt;</description></item><item><title>Find Undead Code in Your Java Environments</title><link>https://foojayio.github.io/website/today/webinar-find-undead-code-in-your-java-environments/</link><pubDate>Mon, 17 Feb 2025 09:36:55 +0000</pubDate><guid>https://foojayio.github.io/website/today/webinar-find-undead-code-in-your-java-environments/</guid><description>&lt;p&gt;&lt;strong&gt;10-30% of the custom code in applications is undead code and can just be deleted. Eliminating undead code can enhance the overall performance and maintainability of your applications. Time vampire (n) &amp;ndash; a service or application that is said to suck time from engineers by warming up and updating at preternaturally slow speeds.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;re on deadline to finish a project, and you open the application to do your work. The application informs you that it needs to update before it will open. Based on past experience, you have half an hour to burn before this time vampire is ready.&lt;/p&gt;</description></item><item><title>5 Ways to Identify and Manage Flaky Tests</title><link>https://foojayio.github.io/website/today/five-ways-to-use-gradle-enterprise-to-identify-and-manage-flaky-tests/</link><pubDate>Tue, 12 Sep 2023 03:57:12 +0000</pubDate><guid>https://foojayio.github.io/website/today/five-ways-to-use-gradle-enterprise-to-identify-and-manage-flaky-tests/</guid><description>&lt;p&gt;&lt;strong&gt;Dealing with flaky tests is a significant challenge in software development. These unpredictable and inconsistent tests can pass or fail without any changes in code, casting doubt on the reliability of your toolchain and ultimately on the application itself. The presence of flaky tests can significantly impact developer confidence and productivity. To better understand why you need to address these flaky tests, read &lt;a href="https://foojayio.github.io/website/today/seven-reasons-you-should-not-ignore-flaky-tests/"&gt;Seven Reasons You Should Not Ignore Flaky Tests&lt;/a&gt;
.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Three Key Elements for Your Flaky Test Remediation Approach</title><link>https://foojayio.github.io/website/today/three-key-elements-to-incorporate-into-your-flaky-test-remediation-approach/</link><pubDate>Tue, 29 Aug 2023 13:32:02 +0000</pubDate><guid>https://foojayio.github.io/website/today/three-key-elements-to-incorporate-into-your-flaky-test-remediation-approach/</guid><description>&lt;p&gt;&lt;strong&gt;Flaky tests pose substantial challenges due to their unpredictable and inconsistent nature. Effectively addressing them requires a multi-faceted approach that involves the effective integration of strategy, process and resource alignment, and a deep understanding of flaky test causality. This post will walk you through this approach.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Note! This post is part of a three-part series. If you&amp;rsquo;re not sure it&amp;rsquo;s worth remediating flaky tests, read &lt;a href="https://foojayio.github.io/website/today/seven-reasons-you-should-not-ignore-flaky-tests/"&gt;Part 1: Seven Reasons You Should Not Ignore Flaky Tests&lt;/a&gt;
. Read Part 2 to understand the keys to identifying and tracking flaky tests, called 5 Ways to Use Gradle Enterprise to Identify and Manage Flaky Tests. Now, let&amp;rsquo;s explore my multi-faceted approach to fixing flaky tests.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Seven Reasons You Should Not Ignore Flaky Tests</title><link>https://foojayio.github.io/website/today/seven-reasons-you-should-not-ignore-flaky-tests/</link><pubDate>Tue, 04 Jul 2023 07:02:44 +0000</pubDate><guid>https://foojayio.github.io/website/today/seven-reasons-you-should-not-ignore-flaky-tests/</guid><description>&lt;p&gt;Imagine the scenario: you have good automated test coverage of your application code; you run your tests locally; and you have a Continuous Integration (CI) environment which runs your tests regularly.&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;re doing everything right, right?&lt;/p&gt;
&lt;p&gt;Except&amp;hellip; sometimes tests fail, and you&amp;rsquo;re not sure why. When you run the test locally, or a second time in the same environment, they pass. Whether they pass or fail doesn&amp;rsquo;t seem to be related to any code changes.&lt;/p&gt;</description></item><item><title>Foojay Podcast #26: The Future of Source Control and CI/CD</title><link>https://foojayio.github.io/website/today/foojay-podcast-26/</link><pubDate>Mon, 26 Jun 2023 08:35:21 +0000</pubDate><guid>https://foojayio.github.io/website/today/foojay-podcast-26/</guid><description>&lt;p&gt;As developers, we like to automate the boring parts of our job. This automation includes the source control system, build pipelines, and code analysis tools.&lt;/p&gt;
&lt;p&gt;In recent decades, we have seen evolutions from CVS to Subversion to Git. Is this the endpoint? Did we find the holy grail in version control? Or what evolutions are waiting for us?&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s find out together with these fantastic guests&amp;hellip;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;This is the final episode of season 2 of the Foojay Podcast. See you in September for the start of our new season with more JUGs, the launch of Java 21, and much more!&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Why I prefer trunk-based development</title><link>https://foojayio.github.io/website/today/why-i-prefer-trunk-based-development/</link><pubDate>Fri, 23 Jun 2023 08:06:35 +0000</pubDate><guid>https://foojayio.github.io/website/today/why-i-prefer-trunk-based-development/</guid><description>&lt;p&gt;&lt;strong&gt;Trisha summarizes the advantages of trunk-based development (as opposed to branch-based development) in this article.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;These days, distributed version control systems like Git have &amp;ldquo;won the war&amp;rdquo; of version control. One of the arguments I used to hear when DVCSs were gaining traction was around how easy it is to branch and merge with a VCS like Git. However, I&amp;rsquo;m a big fan of &lt;a href="https://en.wikipedia.org/wiki/Trunk-based_development" target="_blank" rel="noopener noreferrer"&gt;Trunk-Based Development (TBD)&lt;/a&gt;
, and I want to tell you why.&lt;/p&gt;</description></item></channel></rss>