惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
腾讯CDC
宝玉的分享
宝玉的分享
量子位
Recent Announcements
Recent Announcements
Martin Fowler
Martin Fowler
J
Java Code Geeks
V
Visual Studio Blog
阮一峰的网络日志
阮一峰的网络日志
Blog — PlanetScale
Blog — PlanetScale
大猫的无限游戏
大猫的无限游戏
博客园 - 叶小钗
S
SegmentFault 最新的问题
B
Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 【当耐特】
小众软件
小众软件
The Cloudflare Blog
Y
Y Combinator Blog
I
InfoQ
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
GbyAI
GbyAI
IT之家
IT之家

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why I Publish Research in Public
根本卓哉 Takuya Nemoto · 2026-06-20 · via DEV Community

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.