Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OpenDoor

An open research project exploring why so many aspiring developers struggle to move from learning technology to contributing with confidence.


Table of Contents


🚧 Status

OpenDoor is currently in its research phase.

Right now, this isn't a product or a community. It's an attempt to understand a problem before trying to solve it.

The goal is simple:

Understand why so many people who genuinely want to learn technology never make it to their first meaningful contribution.

Why I'm Exploring This

Over the years, I've noticed a pattern.

People start learning to code with excitement. They complete tutorials, follow courses, join communities, and genuinely want to become developers.

Then, somewhere along the way, many quietly disappear.

It doesn't always seem to be because they aren't capable.

Sometimes they're overwhelmed.

Sometimes they're afraid of asking "basic" questions.

Sometimes they don't know what to do after finishing another tutorial.

And sometimes they simply don't feel like they belong.

I want to understand why that happens.

What I'm Trying to Learn

Rather than jumping straight into building a solution, I'm using this repository to investigate questions like:

  • Where do beginners get stuck?
  • What happens between learning and contributing?
  • Why do some people keep going while others quietly stop?
  • What role do communities, mentorship, and confidence play?
  • What can existing initiatives teach us?

If the research eventually points toward a product, community, or new approach, great.

If it proves my assumptions wrong, that's just as valuable.

Current Focus

For now, this repository is being used to:

  • Document research findings.
  • Challenge assumptions.
  • Study existing communities and initiatives.
  • Talk to beginners about their experiences.
  • Build an evidence-based understanding of the problem.

Guiding Principle

I don't want to build something simply because it sounds like a good idea.

I want to build something because the research shows it's needed.

If you'd like to contribute ideas, research, or challenge my thinking, you're very welcome.

Explore the Repository

If you're new to OpenDoor, here's where to start:

File Purpose
README.md An overview of OpenDoor, what it is, and why it exists.
NOW.md What I'm currently working on and where the project is today.
MANIFESTO.md The principles and values guiding the project.
QUESTIONS.md The questions driving this research journey.
ASSUMPTIONS.md The assumptions I'm actively testing rather than treating as facts.
research/ Research findings, working hypotheses, interview materials, and future insights.
research/interviews/ Interview guide, templates, and conversations with beginner developers.

Getting Started

If you're exploring OpenDoor for the first time, here's a suggested path:

  1. Read the README for an overview of the project.
  2. Explore the MANIFESTO to understand the project's guiding principles.
  3. Review the QUESTIONS driving the research.
  4. Read the ASSUMPTIONS being tested.
  5. Explore the research directory to follow current findings.
  6. Check NOW.md to see the project's current focus.

Follow the Journey

This repository is being built in public.

As the research progresses, I'll continue documenting new findings, interviews, and changes in thinking.

If you're interested in beginner developer experiences or open source onboarding, I'd love for you to follow along.

About

A beginner-first open-source community exploring how to make technology more welcoming.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors