HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
globalcitizen
taoup
Ruby2014–2026
globalcitizen / taoup

taoup

The Tao of Unix Programming (Ruby-powered ANSI colored fortunes)

4Distinct people
228Mentions
1Explicit recommenders
445GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Tao of Unix Programming (Ruby-powered ANSI colored fortunes)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

This made me think of my favorite quote attributed to Einstein: Nationalismus ist eine Kinderkrankheit. Er ist die Masern der Menschheit. "Nationalism is an infantile disease.…

contingencies used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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 year228 dated mentions

Observed mentions: 2014-05-29 07:10:05 UTC to 2026-09-29 19:05:04 UTC.

0102030402014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 13 mentions; 0 submissions, 13 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 31 mentions; 0 submissions, 31 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 20 mentions; 0 submissions, 20 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 29 mentions; 0 submissions, 29 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 24 mentions; 0 submissions, 24 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 21 mentions; 1 submissions, 20 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 39 mentions; 0 submissions, 39 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 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
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC1019
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC13013
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC808
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC31031
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC20020
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC29029
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC24024
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC21120
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC39039
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC12012
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC808
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC11110

What Hacker News says

20 sources
Technological progress was much faster than political progress. - Joseph Henry Condon, Bell Labs A generation before, with the telephone: This 'telephone' has too many shortcomings to be seriously considered as a practical form of communication. The device is inherently of no value to us. What use could this company make of an electrical toy? - Western Union (1878) Two generations before, with printing: The invention of printing, though ingenious, compared with the invention of letters is no great matter. - Thomas Hobbes (17th century) Thus... A little bit of history, repeating... - Alex Gifford (1997) .. via http://github.com/globalcitizen/taoup
In Larry Roberts has died
Yeah, 500+ upvotes on HN apparently think otherwise, but I also dare to disagree... it's not clear, despite claims to the contrary. Comprehending this code relies on reading a long series of verbosely referenced assumptions around an implicit state machine with numerous error conditions and edge cases. The author's argument is that extreme verbosity in control structures assists with ensuring no such conditions escape an explicit code block - ie. they admit that they are (ab)using code to deal with their personal challenge of achieving a rigorous and precise conception of the problem. I would posit that approach is the wrong tool for the job, and further that they have simply failed to clearly articulate the problem, and are writing illegible code and documentation as a result. A clear symptom of the resulting fragility is the title / ope
Read the rest
ning plea to others not to change their carefully constructed house of cards. Fragility does not good code make. If I were to rewrite this, the implicit state machine and its valid transitions would be documented first and foremost, eg. with a railroad diagram or ABNF. The benefit of using [a formal specification language] is that it teaches you to think rigorously, to think precisely, and the important point is the precise thinking. So what you need to avoid at all costs is any language that's all syntax and no semantics. - Leslie Lamport ... via http://github.com/globalcitizen/taoup
In Please do not attempt to simplify this code
you can’t easily identify filters I'm not often SQL wrangling these days, so you are probably more aware than I am on intricacies, but often you can wrap subqueries like: SELECT stuff FROM tables WHERE conditions AND table.field IN ( SELECT othertable.otherfield FROM othertables WHERE more_conditions...) ); IMHO this reads far more easily and both depth and order of execution are clear. I guess at this point in my career (20 years in) my bias is toward code I can walk away from for years and come back to easily. Clarity is better than cleverness. - Eric S. Raymond, The Art of Unix Programming (2003) He's got a point. Quote via http://github.com/globalcitizen/taoup
In You Can Do It in SQL, Stop Writing Extra Code for That
Niven's First Law of Writing: Writers who write for other writers should write letters. - Larry Niven, science fiction author (1989) The writer is that person who, embarking upon her task, does not know what to do. - Donald Barthelme Summary of advice from writers: Advice from writers is useful, and not only about naming. Writers have been at it for centuries; programming is merely decades old. Also, their advice is better written. And funnier. - Peter Hilton ... via http://github.com/globalcitizen/taoup
In You’re Not Managing a Team of Software Engineers, You’re Managing Writers
Requirements are almost never perfectly specified. One of the most substantial and hard-learned parts of good systems design is automatically pre-empting, as far as reasonably possible, the probable range and depth of requirements scope shifts over the project lifetime. (Critically, that includes the 90% of a project's lifetime which is post-development maintenance.) In short: if you have good people it shouldn't matter! Experienced people will extend the assumed scope beyond the stated requirements without being asked, and either do so efficiently within the resources available to the project or bring an appropriate level of attention to the limitation before it becomes an issue. The somewhat less PC and far snarkier explanation, in the immortal words of twitter: Don't pick the right tool for the job, pick the right framework which secur
Read the rest
es you extra work for being a tool. - @iamdevloper (via http://github.com/globalcitizen/taoup)
In Ask HN: Better tools for the software requirements / scoping phase?
You're not really doing something very revolutionary if you're not running into some dead ends. You don't have a clear idea of what it's going to be when you start, you have an inkling and then, each step tells you what the next step is but you don't know what the next step is until you've gotten to a certain point. We thought we were making an exquisite product, the best possible thing at the time but then, we figured, in a few years we'd make something a lot better, completely different. We didn't realize the architecture we were putting in place could last five years, let alone 10, 20, 30 years. I think the essential way to do anything great, you have to have some incremental development philosophy because you're just going to be wrong with your grand design that you don't iterate on. Added to https://github.com/globalcitizen/taoup ;)
In An Interview with Andy Hertzfeld
Most sites can do this - eg. I believe HN is scaled vertically. Over-engineering is rife within the industry! Design up front for reuse is, in essence, premature optimization. - @AnimalMuppet Pike's 2nd Rule: Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest. - Rob Pike, Notes on C Programming (1989) ... quotes from http://github.com/globalcitizen/taoup
In Distributed architecture concepts I learned when building a large payment system

Showing the 15 most recent of 20 sources. Enable JavaScript to search and browse every indexed mention.

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.