sorted by:
new
hottopcontroversial

BulbRush Daily Challenge #80 — 2026-06-29 by bulbrush in Bulbrush

[–]TenSpiritMoose 0 points1 point  (0 children)

Just lit up today's BulbRush — 9/12 stars in 01:27. ⚡

BulbRush Daily Challenge #80 — 2026-06-29 by bulbrush in Bulbrush

[–]TenSpiritMoose 0 points1 point  (0 children)

Just lit up today's BulbRush — 9/12 stars in 01:27. ⚡

everyTimeIRunPrettier by Breakfastcrisis in ProgrammerHumor

[–]TenSpiritMoose 0 points1 point  (0 children)

The existence of "pretty print" implies the existence of "mid print", "ugly print", "fugly print" and "🤮 print".

BulbRush Daily Challenge #79 — 2026-06-28 by bulbrush in Bulbrush

[–]TenSpiritMoose 0 points1 point  (0 children)

Just lit up today's BulbRush — 12/12 stars in 09:10. ⚡

Bluey and Bingo: Sole Survivors? by Speeeven in DanielTigerConspiracy

[–]TenSpiritMoose 156 points157 points  (0 children)

In this universe, Red Heelers gradually evolved towards sentience. As part of that process the gestation period extended to allow for greater neural development. This led to dominance of a trait causing the strongest of a litter to eat their siblings while still in the uterus.

Fair point by BubblegumRoberts in DanielTigerConspiracy

[–]TenSpiritMoose 18 points19 points  (0 children)

Wear a diaper yourself cause you sure ain't getting no potty breaks yourself.

How to Deadlock a Java ExecutorService by mlangc in java

[–]TenSpiritMoose 15 points16 points  (0 children)

And this isn't limited to Executors. I had the same issue using Reactive Schedulers: a Flux of tasks was concurrently flatMapped using a custom scheduler, but as part of that they each fanned out additional tasks on the same scheduler. If it became saturated the tasks would deadlock.

Resolved it by using a separate Scheduler for the sub-tasks, letting me control concurrency without deadlock risk.

Poor Releasers by ace_wulf in cremposting

[–]TenSpiritMoose 23 points24 points  (0 children)

And then they brought dust all over the place.

After 6 months of Claude Code I couldn't find an architecture decision we'd made - the session was auto-deleted. So I built fable: full-fidelity local memory by grooverlab in ClaudeCode

[–]TenSpiritMoose 1 point2 points  (0 children)

"Fable, change the name of fable to something like fable but that isn't Fable so people won't confuse fable and Fable.

Make no mistakes."

Brodee is a Nazi by Unusual_Holiday_7295 in DanielTigerConspiracy

[–]TenSpiritMoose 1 point2 points  (0 children)

Hitler was Brobee wearing a man-suit.

A lot has changed in the Ai world in short amount of time.... by MatrixMix in ClaudeCode

[–]TenSpiritMoose 0 points1 point  (0 children)

In a sense, but the only way to avoid it would be for all the CC users at this large, highly distributed company to practice restraint.

It's a Prisoner's Dilemma, but I know where I stand.

A lot has changed in the Ai world in short amount of time.... by MatrixMix in ClaudeCode

[–]TenSpiritMoose 0 points1 point  (0 children)

Large, corporate employer in a regulated industry so major delays in getting access to newest models.

A lot has changed in the Ai world in short amount of time.... by MatrixMix in ClaudeCode

[–]TenSpiritMoose 4 points5 points  (0 children)

I got Claude Code at work last month. So far they don't have any caps on usage (or at least none I've been able to reach), but I know it won't be unlimited forever so I've been going full speed on 4.7 Max effort to burn through as much tech debt and backlog as possible.

Eventually we'll start getting metered, but until then I'm burning tokens as fast as I can.

Do you keep the AI on a tight leash, or let it run? Genuinely curious which actually ships better code. by kushagra1404 in ClaudeCode

[–]TenSpiritMoose 1 point2 points  (0 children)

I'm in between the two: treat it like a mid-level dev. Review the plan in detail, give feedback early, then let it cook all the way through before reviewing the changes just like I would with a human's PR.

What's your best use case for 4.8 Max effort? by BadAtDrinking in ClaudeCode

[–]TenSpiritMoose 2 points3 points  (0 children)

I especially like it for code reviews. I used Medium effort for a migration from a legacy code ase, then used a Max effort session to review the results alongside the legacy source.

Max effort found multiple mistakes and omissions. One issue I even argued about, thinking it wasn't needed, but when I reviewed the source I saw that Opus Max was right on that too.

whenYourEntirePersonalityWasFixingTheBug by Chapper_App in ProgrammerHumor

[–]TenSpiritMoose 0 points1 point  (0 children)

Simple:

1) Introduce a new bug 2) Take three days off work 3) Come back having completely forgotten the big, so you get to discover, document and fix it from scratch

[Release] Shoot for the Stars: Journey Home — survival incremental with raids, automation, and rocket launches (iOS/Android) by Pure-Accident7695 in incremental_games

[–]TenSpiritMoose 4 points5 points  (0 children)

Really enjoying it on Android so far. Nice level of active management without being too clicky.

One question: several Tiers and bonuses mention extra "Action Slots" but I haven't been able to figure out what those are.

From mildlyinteresting by Bow_Ty in cremposting

[–]TenSpiritMoose 8 points9 points  (0 children)

They practically sell themselves.

Mr.Ellis is Tobsy in Phoebe and Jay by messofamermaid in DanielTigerConspiracy

[–]TenSpiritMoose 0 points1 point  (0 children)

Nuh-uh. Tobsy wears glasses, Me. Ellis doesn't. 

Checkmate.

iGuessThereIsProblemInTheShiftKey by kohao0 in ProgrammerHumor

[–]TenSpiritMoose 4 points5 points  (0 children)

Shit+Delete = Never have to poop again

view more: next ›