HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
97-things
97-things-every-programmer-should-know
OPEN SOURCE2023–2026
97-things / 97-things-every-programmer-should-know

97-things-every-programmer-should-know

Pearls of wisdom for programmers collected from leading practitioners.

4Distinct people
7Mentions
0Explicit recommenders
3.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Pearls of wisdom for programmers collected from leading practitioners.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2023-03-23 14:03:15 UTC to 2026-04-06 17:40:10 UTC.

01232023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC312
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC211
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

7 sources
I recently re-read parts of this book thst I haven’t read in years. https://github.com/97-things/97-things-every-programmer-shou... I think it originally came out in 2013. If I were just introduced to it today, I would think some of the articles were AI written with only slight prompting. It’s sad that if I write something from scratch, without any writing assistance besides spell checking, mostly for internal company consumption I now review it to see if it smells like AI. (Just like I would have used a dash above. But I don’t anymore because it has an AI smell and I had to get out of the habit)
In Why do LMMs overuse these patterns of speech that aren't overused in the wild?
Does it work? If it works then you have to think twice before any changes. The irony is, poorly written often also means unintended consequences if once you refactor. Balloon grabs are the worst. The business doesn't care about "aesthetics". It cares about results. I'm certainly not going to defend poorly written software, only that it all depends on your POV. So unless un-poorly can deliver significant value to the business it's best to consider other ways to deliver value. https://github.com/97-things/97-things-every-programmer-shou...
In Ask HN: Senior engineers, how do you deal with poorly written software?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.