The latest articles on DEV Community by Tunde Adetunji (@tundeadetunji2017). https://dev.to/tundeadetunji2017 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2491459%2Fbb54b55e-9285-436d-a78c-69de369d360c.jpg https://dev.to/tundeadetunji2017 en Tunde Adetunji Sun, 18 Oct 2026 23:19:49 +0000 https://dev.to/tundeadetunji2017/looking-for-contributors-can-we-build-a-net-toolkit-developers-love-to-use-2oep https://dev.to/tundeadetunji2017/looking-for-contributors-can-we-build-a-net-toolkit-developers-love-to-use-2oep <p>I've been working on a project called <strong>Code Repertoire</strong>, a lightweight programmer's toolkit intended to simplify everyday .NET programming tasks and make repetitive work less tedious.</p> <p>The project has grown beyond an initial idea. My NuGet/.NET packages have collectively passed 100,000 downloads, and I can only imagine what might be possible with more developers involved.</p> <p>The codebase is currently almost entirely VB.NET. I also want to explore C# support, while keeping compatibility, maintainability, and the project's existing users in mind.</p> <h2> The bigger ambition </h2> <p>I'd love to see Code Repertoire become more than a collection of utilities — something .NET developers find genuinely useful, trust, and return to as part of their normal workflow.</p> <p>My view is that projects can begin with a modest scope and grow into widely used pieces of the developer ecosystem. I'm not promising a particular outcome, but who knows? Building something useful enough to earn that kind of adoption is an ambition I believe worth pursuing.</p> <p>I'd like contributors to have a say in how we get there.</p> <h2> Who can get involved? </h2> <p>You don't need to be a long-time open-source contributor. You might be interested in:</p> <ul> <li>Improving or extending existing VB.NET utilities.</li> <li>Exploring how C# support could fit into the project.</li> <li>Fixing bugs or adding automated tests.</li> <li>Improving documentation and examples.</li> <li>Proposing new utilities that solve recurring .NET development problems.</li> <li>Reviewing design decisions and helping set priorities.</li> </ul> <p>Small contributions are welcome. We can discuss larger changes before implementation so that people aren't investing time in work that doesn't fit the project's direction.</p> <h2> Take a look </h2> <p>Repository: <a href="https://github.com/tundeadetunji/api-dot_net-all_modules" rel="noopener noreferrer">https://github.com/tundeadetunji/api-dot_net-all_modules</a></p> <p>If this sounds interesting, explore the code, look at the open issues, or share an idea for something you'd like the toolkit to do.</p> <p>I'd love to hear what you think — and perhaps build something useful together.</p> contributorswanted