←back to thread

1972 Unix V2 "Beta" Resurrected

(www.tuhs.org)
414 points henry_flower | 2 comments | 19 Feb 25 21:41 UTC | HN request time: 0.001s | source
Show context
m4r1k ◴[20 Feb 25 07:27 UTC] No.43112034[source]▶
I once saw a talk from Brian Kernighan who made a joke about how in three weeks Ken Thompson wrote a text editor, the B compiler, and the skeleton for managing input/output files, which turned out to be UNIX. The joke was that nowadays we're a bit less efficient :-D
replies(7): >>43112150 #>>43112344 #>>43112772 #>>43114120 #>>43117365 #>>43118374 #>>43118624 #
pinoy420 ◴[20 Feb 25 07:50 UTC] No.43112150[source]▶
Otoh: I got react to run my tests without any warnings today.
replies(1): >>43112683 #
9dev ◴[20 Feb 25 09:13 UTC] No.43112683[source]▶
If I write a bunch of tests for new code, and all of them pass on the first attempt, I'm immediately suspicious of a far more egregious bug hiding somewhere…
replies(3): >>43114300 #>>43114644 #>>43120829 #
throwanem ◴[20 Feb 25 13:55 UTC] No.43114644[source]▶
Where feasible, I like to start a suite with a unit test that validates the unit's intended side effects actually occur, as visible in their mocks being exercised.
replies(1): >>43117900 #
1. pinoy420 ◴[20 Feb 25 17:54 UTC] No.43117900{3}[source]▶
I laughed. Thank you for that
replies(1): >>43123491 #
2. throwanem ◴[21 Feb 25 02:57 UTC] No.43123491[source]▶
Sure. For Patreon subscribers at the $5/month tier and up, I also have a course on making integration ("e2e", "functional") tests more maintainable by eliminating side effects.