explaingit

hwayne/awesome-cold-showers

7,341Audience · developerComplexity · 1/5Setup · easy

TLDR

A curated reading list of articles, papers, and videos that examine the limitations and failure cases of overhyped ideas in software development, with each entry including caveats to keep the counterargument honest.

Mindmap

mindmap
  root((Awesome Cold Showers))
    What it does
      Curated reading list
      Counters tech hype
      Balanced evidence
    Topics Covered
      Microservices
      Blockchain
      Type systems
      Machine learning
      Agile and TDD
    Entry Format
      Hype claim
      Counterargument
      Caveats
    Audience
      Developers
      Tech decision makers
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Find rigorously sourced reading material to balance your view before adopting a hyped technology like microservices, blockchain, or formal verification.

USE CASE 2

Share a specific entry with a team arguing for a trendy approach to show the evidence is more mixed than conference talks suggest.

USE CASE 3

Explore academic papers and benchmark studies on topics like type systems, TDD, and big data tools to inform architecture decisions.

Getting it running

Difficulty · easy Time to first run · 5min

Plain Markdown file, just read it on GitHub, no install needed.

The explanation does not mention the license.

In plain English

Awesome Cold Showers is a curated list of articles, papers, and videos that push back on overhyped ideas in software development and technology. The premise is simple: when the tech community gets very excited about a concept, it helps to have rigorously sourced reading material that examines the limitations, failure cases, or inconclusive evidence behind that enthusiasm. The list is not trying to dismiss any topic entirely, just to add balance. Each entry follows a consistent format. It names a piece of hype, a common confident claim you might encounter in conference talks or blog posts. It then describes the shower, which is what the linked resource actually shows. Finally, each entry notes caveats so you understand the limits of the counterargument too. The topics covered are wide-ranging. Entries address formal verification of software, microservices architecture, type systems, big data tools, Agile development methodology, blockchain, machine learning, test-driven development, open-source sustainability, and naming conventions in code. Some entries point to academic papers, some to benchmark studies, some to experienced practitioners writing up what went wrong in practice. For example, one entry covers a benchmark showing that a laptop running optimized single-threaded code consistently outperforms large distributed computing clusters on graph-processing tasks. Another points to literature reviews finding that research on static typing's effect on bug rates is inconclusive. Another covers eye-tracking studies on code identifier styles that produced unexpected results. The repository itself is a plain Markdown file with no code. It is maintained by its author, who reads every submission and makes judgment calls about what to include. The goal is to keep the list rigorous and respectful, not cynical.

Copy-paste prompts

Prompt 1
My team wants to adopt microservices for our small startup. Find me the relevant entries in awesome-cold-showers and summarize what the evidence actually says about microservices at small scale.
Prompt 2
We're evaluating whether to add TypeScript strict typing to our project for bug prevention. What does awesome-cold-showers say the research shows about static typing and bug rates?
Prompt 3
I'm preparing a conference talk on blockchain and want to include honest limitations. Find me the cold-shower entries on blockchain and summarize the key counterarguments with their caveats.
Prompt 4
My team is debating whether to adopt test-driven development. What does this list say about the actual evidence for TDD's effectiveness?
Open on GitHub → Explain another repo

← hwayne on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.