HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
EternityForest
AnyoneCanDoIt
Learning & Reference2022–2024
EternityForest / AnyoneCanDoIt

AnyoneCanDoIt

An open source guide to mistake-resistant engineering(Work in progress)

3Distinct people
11Mentions
0Explicit recommenders
142GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An open source guide to mistake-resistant engineering(Work in progress)

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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:49:33 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 month11 dated mentions

Observed mentions: 2022-01-13 12:09:43 UTC to 2024-03-29 10:52:05 UTC.

01232022-01-01 00:00:00 UTC to 2022-02-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 20222022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 20232023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2024

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
Jan 20222022-01-01 00:00:00 UTC2022-02-01 00:00:00 UTC202
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC000
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC312
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC000
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC202
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC000
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC000
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC211
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC000
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC101
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC000
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC101

What Hacker News says

3 sources
I've done this extensively and have compiled a lot of data because of how many mistakes I make, and am working on this document, an ongoing set of strategies for decoupling success from natural talent: https://github.com/EternityForest/AnyoneCanDoIt My most important rules: 1. There is no later. I assume that time is a concept only machines can process. If someone tells me to do something when X happens or check something in an hour or so, I immediately set reminders. I don't even consider trying to just remember as an option, I know my failure rate will be well over 80%. 2. Absolutely no mental rotation. Learn to recognize any thought process that involves a rotation, and assume results are invalid. I check the map after after every turn. I never compare objects in different orientations. 3. The verbal machine gun strategy When someone i
Read the rest
s trying to get me to do something dangerous, and starts talking fast, I assume it's basically suppressive fire for thought. If I were to explain why it's a bad idea in their pitch and tone I'd sound like a maniac, but they can talk as fast as they want because they are relying on tradition and intuition, not complicated reasoning. "Come on, it will be fun" is easier to say fast then "I literally know a guy who was very experienced, who tried this, and died". The only defense I know of is to not care what they think or how you look, and have nothing to prove, especially not to yourself. 4. Never assume any task is too simple and easy to need a plan. If you give me a bucket of balls and ask me to count them, I'm going to pull out a counter app. That 10% of the time I lose count before getting to 10 is embarrassing enough to be worth the trouble to avoid.
In Document your mistakes and then try to block them in the future
I am literally working on exactly that, as an project I'm calling Math: ELI5, all open source on GitHub: https://github.com/EternityForest/AnyoneCanDoIt/blob/master/... The catch is that I myself don't actually understand this well. It's just "What I learned googling stuff while working as a programmer. I've had help reviewing it but there could be errors. I'm trying to cover all areas of math that a nontechnical person, or typical non math focused programmer would need to know, but I treat actually doing any of it by hand on paper as an arcane thing for the really dedicated, so there's not really any excercises. Instead of actually teaching a real understanding of math, which I can't do, because I don't know it well, I just explain what people who do understand it use it for and why you might want to go actually learn it. I also have an
Read the rest
y historical math related stuff that I find interesting. I can't tell you how to derive or prove Euler's equation , but you don't need to know math to understand the emotional impact from a humanities perspective, and be amazed that all those constants fit together like that, and that someone could discover it. Ultimately, I think traditional math education has it totally right. My life would be so much better if I knew it, because there's jobs that seem to require exactly what they tech in math class. It's not directly useful for non STEM types, but the idea seems to be give everyone a head start since so many do want STEM jobs. I think you really do have to get to the being able to do proofs level to make use of it in the real innovative applications. The common everyday applications math people like to cite can usually have a dedicated software package. It's not like we still need to add two numbers on paper. If you want to build something, we have RealThunder's FreeCAD. Excel's Goal Seek and CAS systems do the stuff people say we will use algebra for. But if your in tech eventually you run into the wall and need to do something like a Kalman filter or calculate stresses in a bridge and you're screwed.
In So you want to study mathematics

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.