Why I Publish Research in Public

Many research projects begin in private.

Notes remain on personal computers.

Drafts stay hidden.

Ideas circulate only among a small number of people.

I have chosen a different approach.

Whenever possible, I prefer to develop research in public.

What Does “Research in Public” Mean?

Publishing research in public does not necessarily mean publishing finished work.

Instead, it means making parts of the research process visible.

Examples include:

• Preprints


• Research notes


• Documentation


• GitHub repositories


• Technical articles


• Conceptual discussions

The goal is not perfection.

The goal is transparency.

The Traditional Model

Historically, research often followed a simple path:

Research → Journal Submission → Publication

The public usually saw only the final result.

Years of development remained hidden.

This model still plays an important role.

However, modern technology has created additional possibilities.

The Open Science Alternative

Today, researchers can share work at many stages.

A project may appear as:

• An idea


• A draft


• A preprint


• A repository


• A technical implementation


• A peer-reviewed publication

Instead of a single publication event, research becomes an evolving process.

Why I Prefer Public Development

One reason is simple:

Knowledge grows through interaction.

Ideas become stronger when exposed to criticism, questions, and alternative perspectives.

Public development creates opportunities for feedback that would otherwise never occur.

Not every comment is useful.

But useful comments can significantly improve a project.

Documentation as Research

Many researchers underestimate documentation.

Documentation is often treated as an afterthought.

I see it differently.

Writing explanations forces researchers to clarify assumptions.

Ambiguous concepts become visible.

Weak arguments become easier to identify.

In many cases, documentation improves the research itself.

GitHub and Research

GitHub is commonly associated with software development.

However, many of its principles apply equally well to research.

Version control.

Transparency.

Revision history.

Public discussion.

These tools make long-term projects easier to manage.

Research is often iterative.

GitHub embraces iteration.

Visibility and Accountability

Public work creates visibility.

It also creates accountability.

Once ideas are published, they can be examined by others.

Mistakes become easier to detect.

Claims become easier to verify.

While this can feel uncomfortable, it also encourages greater rigor.

Independent Research in the Digital Era

The internet has dramatically expanded opportunities for independent researchers.

Repositories.

Persistent identifiers.

Open-access platforms.

Collaborative tools.

Together, these technologies reduce barriers that previously limited participation.

Research remains difficult.

But access to infrastructure is increasingly available.

Research as an Ongoing Process

One of the biggest misconceptions about research is that it progresses in a straight line.

In reality, most projects evolve through:

• Revisions


• Dead ends


• New evidence


• Unexpected discoveries

Public development makes this process visible.

Instead of presenting only conclusions, it reveals part of the journey.

Final Thoughts

Publishing research in public is not about attracting attention.

It is about participating in an open process of knowledge development.

Ideas improve through exposure.

Documentation improves through revision.

Research improves through discussion.

Modern scholarly infrastructure makes public development easier than ever before.

For that reason, I believe research should be viewed not only as a final product, but also as an ongoing conversation.