universeodon.com is part of the decentralized social network powered by Mastodon.
Be one with the #fediverse. Join millions of humans building, creating, and collaborating on Mastodon Social Network. Supports 1000 character posts.

Administered by:

Server stats:

3.2K
active users

Learn more

#innersourcing

0 posts0 participants0 posts today
Jan Wildeboer 😷:krulorange:<p>It's a new version of <a href="https://social.wildeboer.net/tags/InnerSourcing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InnerSourcing</span></a>, that is starting to grow, IMHO. We will see more investments in bare metal, a modest growth of BYODC (Build Your Own Data Center). Hybrid cloud solutions. And smaller, self-owned and trained AI models. All of this will be based more on compliance and risk avoidance and not a big patriotic/nationalistic move as some like to promote. 2/4</p>
gittaca<p>From <a href="https://chaos.social/tags/InnerSourcing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InnerSourcing</span></a> to <a href="https://chaos.social/tags/InnerShittification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InnerShittification</span></a>: When org-internal software is being evolved to accommodate the whims of some rare few, instead of the needs of its daily users.</p><p>Oh, right! That's already called <a href="https://chaos.social/tags/EnterpriseSoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EnterpriseSoftware</span></a>.</p><p><a href="https://chaos.social/tags/enshittification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>enshittification</span></a> <a href="https://chaos.social/tags/e14n" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>e14n</span></a></p>
Dennis Doomen<p>that are individually releasable—provided you carefully design the <a href="https://mastodon.social/tags/dependencies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dependencies</span></a> between them. Even if you're not splitting your codebase for scalability, there will always be components that you may want to share with other teams.</p><p>I'm a big proponent of treating internal code the same way open-source developers do, often called <a href="https://mastodon.social/tags/innersourcing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>innersourcing</span></a>. This means anyone should be able to fork a repository, suggest improvements, and feel (cont'd)</p>
Dennis Doomen<p>As modern codebases heavily rely on <a href="https://mastodon.social/tags/NPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NPM</span></a>, <a href="https://mastodon.social/tags/NuGet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NuGet</span></a>, and other similar package managers, it's important to recognize the responsibility that comes with using them. Whether these packages are open-source or made available internally (e.g., through <a href="https://mastodon.social/tags/innersourcing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>innersourcing</span></a>), you must ensure they are kept up-to-date at all times.</p>