Tweet
Academic research often seems disconnected from building real products. Dense papers, theoretical concepts, months or years behind practical application. But occasionally research directly informs what you can build right now.
This is where we discuss research papers, academic work, and technical publications that matter for builders. Not everything published—just the research that's actually relevant to building products.
Why Research Matters
Academic research explores possibilities before they're practical. Understanding cutting-edge research shows you what's coming 1-2 years before it hits production.
Papers document what works and what doesn't. Someone already tried that approach, measured results, published findings. Learn from their experiments instead of repeating them.
Research provides theoretical foundation. Understanding why something works helps you apply it effectively and adapt it to your specific needs.
Types of Useful Research
Algorithm papers: New approaches to common problems. Better sorting, searching, compression, optimization.
System design papers: How to build scalable, reliable, performant systems. Google's MapReduce, Amazon's Dynamo, Meta's TAO.
Machine learning papers: New architectures, training techniques, model designs. Transformers, ResNet, BERT—all started as papers.
HCI research: How people interact with interfaces. What works, what doesn't, why.
Security research: Vulnerabilities, attack vectors, defense mechanisms. Often directly applicable to protecting your systems.
Where to Find Research
arXiv - Preprint server, especially strong in CS, ML, physics Papers With Code - Research papers with implementation code Google Scholar - Academic search engine Semantic Scholar - AI-powered research tool ACM Digital Library - Computer science publications
Conferences to follow: ICML, NeurIPS, ICLR - Machine learning SIGMOD, VLDB - Databases CHI, UIST - Human-computer interaction USENIX, OSDI, SOSP - Systems
Reading Research Papers
Don't read linearly. Research papers aren't written to be read start-to-finish.
Reading strategy:
How to Read a Paper by S. Keshav - Three-pass approach to reading research
From Paper to Practice
Most papers include novel ideas but also lots of specific details that matter for their specific context. Extract the core insight and adapt it.
Look for accompanying code. Papers With Code links papers to implementations.
Check if someone's already packaged this as a library. Don't reimplement from scratch if you don't have to.
Start simple. Papers often show maximally sophisticated version. Begin with minimal viable implementation.
Influential Papers Worth Knowing
These shaped modern computing and are surprisingly readable:
MapReduce (Google, 2004) - Distributed data processing Dynamo (Amazon, 2007) - Highly available key-value store Attention Is All You Need (2017) - Transformer architecture, basis for GPT/BERT Bitcoin (Nakamoto, 2008) - Cryptocurrency and blockchain
Staying Current
Follow researchers on Twitter/X - they often share and discuss new papers
Subscribe to newsletters: Papers We Love - Community celebrating academic CS papers Import AI - AI research newsletter Morning Paper - Daily paper summaries (archived but valuable)
Join reading groups. Many companies and communities run paper reading clubs. Discussing papers with others aids understanding.
Sharing Research Findings
Found a paper relevant to builders? Share it with context:
What problem does it solve? Key insight or technique Why it matters for builders Links to paper and any implementations Your take on practical applicability
Don't just post links. Add commentary about relevance and how to apply it.
Research isn't just for PhDs. It's for anyone who wants to understand what's possible, learn from others' experiments, and build on the frontiers of what technology can do.
This is where we discuss research papers, academic work, and technical publications that matter for builders. Not everything published—just the research that's actually relevant to building products.
Why Research Matters
Academic research explores possibilities before they're practical. Understanding cutting-edge research shows you what's coming 1-2 years before it hits production.
Papers document what works and what doesn't. Someone already tried that approach, measured results, published findings. Learn from their experiments instead of repeating them.
Research provides theoretical foundation. Understanding why something works helps you apply it effectively and adapt it to your specific needs.
Types of Useful Research
Algorithm papers: New approaches to common problems. Better sorting, searching, compression, optimization.
System design papers: How to build scalable, reliable, performant systems. Google's MapReduce, Amazon's Dynamo, Meta's TAO.
Machine learning papers: New architectures, training techniques, model designs. Transformers, ResNet, BERT—all started as papers.
HCI research: How people interact with interfaces. What works, what doesn't, why.
Security research: Vulnerabilities, attack vectors, defense mechanisms. Often directly applicable to protecting your systems.
Where to Find Research
arXiv - Preprint server, especially strong in CS, ML, physics Papers With Code - Research papers with implementation code Google Scholar - Academic search engine Semantic Scholar - AI-powered research tool ACM Digital Library - Computer science publications
Conferences to follow: ICML, NeurIPS, ICLR - Machine learning SIGMOD, VLDB - Databases CHI, UIST - Human-computer interaction USENIX, OSDI, SOSP - Systems
Reading Research Papers
Don't read linearly. Research papers aren't written to be read start-to-finish.
Reading strategy:
- Read abstract and conclusion first - understand what they did and what they found
- Look at figures and tables - visual summaries often clearest
- Read introduction - understand problem and why it matters
- Skim related work - see how this fits with existing research
- Read methodology if you need implementation details
- Dive into results and discussion for the interesting bits
How to Read a Paper by S. Keshav - Three-pass approach to reading research
From Paper to Practice
Most papers include novel ideas but also lots of specific details that matter for their specific context. Extract the core insight and adapt it.
Look for accompanying code. Papers With Code links papers to implementations.
Check if someone's already packaged this as a library. Don't reimplement from scratch if you don't have to.
Start simple. Papers often show maximally sophisticated version. Begin with minimal viable implementation.
Influential Papers Worth Knowing
These shaped modern computing and are surprisingly readable:
MapReduce (Google, 2004) - Distributed data processing Dynamo (Amazon, 2007) - Highly available key-value store Attention Is All You Need (2017) - Transformer architecture, basis for GPT/BERT Bitcoin (Nakamoto, 2008) - Cryptocurrency and blockchain
Staying Current
Follow researchers on Twitter/X - they often share and discuss new papers
Subscribe to newsletters: Papers We Love - Community celebrating academic CS papers Import AI - AI research newsletter Morning Paper - Daily paper summaries (archived but valuable)
Join reading groups. Many companies and communities run paper reading clubs. Discussing papers with others aids understanding.
Sharing Research Findings
Found a paper relevant to builders? Share it with context:
What problem does it solve? Key insight or technique Why it matters for builders Links to paper and any implementations Your take on practical applicability
Don't just post links. Add commentary about relevance and how to apply it.
Research isn't just for PhDs. It's for anyone who wants to understand what's possible, learn from others' experiments, and build on the frontiers of what technology can do.