<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Daniel Witkowski on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/daniel-witkowski/</link><description>Articles written by Daniel Witkowski on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 01 Dec 2025 06:43:36 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/daniel-witkowski/index.xml" rel="self" type="application/rss+xml"/><item><title>Foojay Podcast #84: Developing Performant, Cost Efficient, and Eco-friendly Code</title><link>https://foojayio.github.io/website/today/foojay-podcast-84/</link><pubDate>Mon, 01 Dec 2025 06:43:36 +0000</pubDate><guid>https://foojayio.github.io/website/today/foojay-podcast-84/</guid><description>&lt;p&gt;In this Foojay Podcast, we&amp;rsquo;re exploring a critical topic that&amp;rsquo;s becoming increasingly important in our industry: developing sustainable software that is both performant and environmentally friendly.&lt;/p&gt;
&lt;p&gt;At the Devoxx and JFall conferences, I had fascinating conversations about how we as Java developers can make a real impact on both our cloud costs and our carbon footprint. And it&amp;rsquo;s interesting to learn how these two goals are often perfectly aligned: what&amp;rsquo;s good for your budget is usually good for the planet too.&lt;/p&gt;</description></item><item><title>The Art of Performance Tuning: Why Saving 30% in the Cloud Means Nothing if Your Code Wastes 1000× More</title><link>https://foojayio.github.io/website/today/the-art-of-performance-tuning-why-saving-30-in-the-cloud-means-nothing-if-your-code-wastes-1000x-more/</link><pubDate>Tue, 25 Nov 2025 06:46:00 +0000</pubDate><guid>https://foojayio.github.io/website/today/the-art-of-performance-tuning-why-saving-30-in-the-cloud-means-nothing-if-your-code-wastes-1000x-more/</guid><description>&lt;h2 id="h2-0-the-hidden-cost-of-good-enough-code"&gt;The Hidden Cost of &amp;ldquo;Good Enough&amp;rdquo; Code&lt;/h2&gt;
&lt;p&gt;A few weeks ago, Kirk Pepperdine published a fascinating performance challenge &amp;mdash; a small Java code snippet that appeared trivial but produced puzzling runtime behavior.&lt;/p&gt;
&lt;p&gt;He invited readers to take a shot at solving it. If you haven&amp;rsquo;t seen it yet, stop here for a moment and try it yourself &amp;mdash; and when you&amp;rsquo;re done, check his Kirk&amp;rsquo;s official solution&lt;/p&gt;
&lt;p&gt;When I saw it, I thought it would be a fun exercise to revisit some fundamentals &amp;mdash; but the deeper I went, the more I realized it wasn&amp;rsquo;t just about performance. It was about how we think.&lt;/p&gt;</description></item></channel></rss>