Go from curious to capable, wherever you start.
Learning, building and community for developers with no course budget, no network. Our writing and playbooks are free to read, open to reuse, and checked to still work.
Why the Rubberduck Foundation exists
Most of what makes a developer good is rarely said out loud.
It surfaces as an aside in a code review, as a habit one senior engineer never thinks to explain, as an answer in a private chat that someone learned the hard way, or as the part of a course that costs a month's rent. It stays unsaid because repeating it and keeping it current does not pay.
The Rubberduck Foundation builds the free alternative to all of it: learning, building and community. Here the unspoken gets said out loud, then tested and maintained so free never quietly means worse. Knowledge kept private stays small. Knowledge made public, tested and maintained compounds. We are building for the compounding.
Saying it out loud shows its shape.
Explaining a problem forces its structure into the open, often before you reach the end of the sentence.
The duck never makes you feel stupid.
No question is too small to ask. That is the kind of place we are building.
To help people learn, build and connect, by the easiest path that still leaves something worth keeping.
What the Foundation builds
Learn, build, connect. Each one feeds the next.
- Open now
Learn
Paths that say what they assume.
Maintained writing and playbooks that tell you what to know first, what you will be able to do after, and when they were last checked to still work.
- Published as trails you can read today
- What you need first, stated up front
- A last verified date on every trail
Build
Start building in one sitting.
Low ceremony entry, real scaffolding, and a sandbox where nothing is at stake while you find out whether the idea holds.
- Working starter code, not a slide deck
- A clear seam where your part begins
- A free sandbox you can throw away
Connect
Circles, not crowds.
Small groups around a topic, a technology or a city. Small enough that no one is anonymous, large enough that no one is a bottleneck.
- Open sessions and mentorship
- A public commons, answered within a day
- Answers that stay searchable afterwards
A path hands you off to a build that raises questions a Circle answers and the best answers become a path. The loop is meant to close by itself.
What we produce
Depth other people can stand on.
We would rather ship ten things a thousand people depend on than a thousand things nobody finishes. Everything carries a license that permits reuse without asking, and an owner who is a person, not just an org name.
Writing
Guides, articles and structured learning paths. Written for the reader's next hour, not for search engines.
Read it as trailsPlaybooks
End to end workflows and development processes. Each names the problem it solves, the steps in order, and where it stops applying.
Read it as trailsSoftware
Libraries, tools and abstractions. Judged by whether someone outside the Foundation depends on them, not by lines of code.
Models and data
Curated models and open evaluation datasets. Provenance and license stated up front, not discovered later.
Building with AI is one of the areas we actively support, and we expect it to be a busy one. It is not what defines the Foundation. Good practice, openly maintained, is.
Trails · How our writing and playbooks are published
Writers explain it to the duck.
Every writer here treats the platform as their rubber duck, explaining each idea until it holds up. A trail turns that writing into one path that ends at a proof project, for the curious beginner and the busy professional alike.
Pick a trail
Each trail leads to one proof project, named in a single sentence.
Follow the trail maps
The big skills on the way, laid out in the order you need them.
Take one article at a time
Each teaches one small skill in about 2 minutes, then gives you 10 to practise it.
Build the proof project
Put the skills together in a small project worth showing. It is the goal of the whole trail.
Open trails, ready today
Go to the trailsMastering Kafka
Run Kafka, produce and consume messages reliably, and build a small event pipeline you can explain in an interview.
6 trail maps · 12 articles · 44 min reading
Verified
Git Essentials
Track your work with Git, branch and merge safely, undo mistakes, and share changes through a pull request.
5 trail maps · 9 articles · 24 min reading
Verified
Sorting Techniques
Write the classic sorting algorithms, explain their speed and stability, and pick the right one for a job.
4 trail maps · 8 articles · 25 min reading
Verified
The community
Built for people who never had the shortcut.
Not for those who already have a paid course, a mentor or great onboarding docs. For whoever shows up without them, on a slow connection, without admin rights, in any language.
The newcomer
Knows enough to be dangerous, not enough to know what to search for.
Finds here
A path that says what to know first, and never punishes a question.
The self taught builder
Has an idea and momentum, but no team and no budget.
Finds here
A way from zero to a working thing in one sitting.
The developer without a network
Solved this problem before, somewhere nobody saw it.
Finds here
A place to write it down once, and a Circle of peers who respect your time.
The maintainer
Wrote something useful and cannot sustain it alone.
Finds here
Collaborators who can find the work and trust that it is real.
Open to anyone, whatever your background. For any role.
Track record is shown in public work.
- Contributor
- Mentor
- Circle organiser
- Maintainer
How far this goes
A promise of a direction, not a date.
Stated plainly so it can be checked later. Are we closer this year than last, and can anyone outside the Foundation verify that?
- 01
A learning path for anything worth learning
Including what is locked behind one employer, one country's universities, or a niche too small for any course platform.
- 02
A sandbox that scales with the learner
A first hello world and a first distributed system, both free. Limits get renegotiated in public, never quietly.
- 03
A commons that outlives any single answer
Dense enough that most questions are already answered before they are asked twice.
- 04
A Circle within reach of anywhere
Forming in places that never had a scene, run by people the Foundation did not hand pick.
- 05
Independence from any one funder
No funding with editorial strings, and a core that keeps working if any single revenue line disappears.
Bring a question. Leave with something worth keeping.
Success here is someone leaving with something built or understood. Start with our writing and playbooks: your first trail article takes about two minutes, and the duck is listening.