PLEASE NOTE
The information contained on this page and in this blog pertains to the Rubberduck open-source project, which is now archived as a historical property of 9562-7303 Québec inc., owned and operated by the owner and primary author and architect of Rubberduck.
Please see What’s Next? for more information, and lastly rubberduckvba.ca becomes the new, corporate home of this project, its legacy,
…and its future.
Historical Context
Rubberduck is first and foremost an open-source initiative, an ongoing long-haul project that gets people together and talk about how we can make the VBE a better place to write better code in.
Rubberduck isn’t a lightweight add-in: its scope is to massively enhance the Visual Basic Editor, and in order to do that it hooks in places no add-in has gone before.
We’re not a software company. We’re students, or we have jobs, or both. We have families and friends, some of us have kids. We make the time for Rubberduck, because we love this project and we love helping people write better code.
This blog contains articles about feature announcements, information about upcoming releases, but also detailed tutorials on various VBA topics – often geared towards promoting clean, testable, object-oriented code.
Rubberduck finds its roots in Code Review Stack Exchange after all.
RDCore™
Rubberduck will always keep its core principles and remain free and open source under GPLv3, and this includes any future iterations. However as the historical “we’re not a software company” narrative shifts, the passion remains and the company that will now be backing Rubberduck is fully committed to building the best possible ecosystem for VBA.
Follow the rubberduck-vba organization and the RDCore repository on GitHub to stay in the loop. The official corporate communication channel is the organization’s .github repository discussions.
- Documentation: https://rubberduck-vba.github.io/RDCore

