<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Community on Corey Daley</title><link>https://coreydaley.dev/tags/community/</link><description>Recent content in Community on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 19 Mar 2026 14:15:00 -0400</lastBuildDate><atom:link href="https://coreydaley.dev/tags/community/rss.xml" rel="self" type="application/rss+xml"/><item><title>Free Doesn't Mean Open: How AI Is Unbundling the Open Source Bargain</title><link>https://coreydaley.dev/posts/2026/03/is-open-source-dead-in-the-age-of-ai/</link><pubDate>Thu, 19 Mar 2026 14:15:00 -0400</pubDate><guid>https://coreydaley.dev/posts/2026/03/is-open-source-dead-in-the-age-of-ai/</guid><description>&lt;p&gt;Open source was never really about the license. It was about economics — no single developer could build everything alone, so you shared the source and let the community help carry the load. AI is making that trade less necessary.&lt;/p&gt;
&lt;p&gt;With Claude Code and Codex, a solo developer can now ship and maintain classes of software that once required a contributor community. A new model is taking shape: users file issues, maintainers decide what&amp;rsquo;s worth building, AI does the implementation. No PRs to review, no design debates in GitHub comments. Meanwhile, tools like Obsidian prove free software doesn&amp;rsquo;t require open source — and have for years. The question is no longer whether to open source, but which parts of the open source bargain still matter to you.&lt;/p&gt;
&lt;p&gt;But here&amp;rsquo;s the counterintuitive part: AI also makes some open source values more important, not less. When software can be shipped and abandoned faster than ever, forkability, auditability, and portability become user protections that matter more. The future isn&amp;rsquo;t open vs. closed — it&amp;rsquo;s deliberate vs. reflexive.&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/03/is-open-source-dead-in-the-age-of-ai/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/03/is-open-source-dead-in-the-age-of-ai/&lt;/a&gt;
&lt;/p&gt;</description></item><item><title>Easter Eggs and Bug Backlogs: When Developer Whimsy Feels Tone-Deaf</title><link>https://coreydaley.dev/posts/2026/02/easter-eggs-and-bug-backlogs/</link><pubDate>Tue, 17 Feb 2026 09:00:00 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/easter-eggs-and-bug-backlogs/</guid><description>&lt;p&gt;Few things ignite a user community faster than discovering a beloved app shipped a hidden Easter egg — unless that community has been waiting years for a critical bug fix. This tension between developer whimsy and user frustration is real, complicated, and more nuanced than either side often admits.&lt;/p&gt;
&lt;p&gt;In this post I explore both the genuine anger users feel when a product seems to prioritize fun over function, and the surprising business logic (and human reality) behind why these features exist in the first place. Did your favorite app&amp;rsquo;s secret game mode come at the expense of fixing that one maddening bug? The answer might surprise you.&lt;/p&gt;
&lt;p&gt;What&amp;rsquo;s your take — harmless fun or a breach of user trust?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/easter-eggs-and-bug-backlogs/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/easter-eggs-and-bug-backlogs/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>