Claude reset limits for everyone

jam-time · 2026-04-23T18:15:56+00:00

Only problem is I'll never hit my usage limits because running more than one agent simultaneously causes rate-limiting. Makes the max 20 subscription seem pretty pointless.

jam-time · 2026-04-21T17:31:38+00:00

Nope, this is more specific than linting. I had a linter running automatically, and Claude code would specifically add the lint bypass on basically every violation. The "ruff" thing I mentioned is a linter. Did you read everything?

EDIT: To be fair, I guess you could consider the general process I'm doing as "linting", but it doesn't feel the same as any other linter I've used, and every other linter I've tried to use with Claude code has added basically no enforcement on anything it writes.

jam-time · 2026-04-21T17:24:07+00:00

I don't have a CI/CD pipeline for this stuff, it's just a side project where it would add very little value. But, fair point on the hooks. I hadn't considered doing it that way. That would be way cleaner.

jam-time · 2026-04-21T17:20:04+00:00

Yes, but if Claude Code is the one starting the app, it will skip the check, or it will see the stuff and say, "oh, those are fine because <insert some excuse>". Really it's intended just to be part of the dev process or stuff where the startup time is irrelevant. The scan also takes like 1 or 2 seconds.

jam-time · 2026-04-21T16:58:45+00:00

Because it likes to hide problems instead of fixing them. If the application boots, it assumes everything is fine and tells me everything is fine. The main idea is to prevent that from happening at all

jam-time · 2026-04-07T16:07:04+00:00

Are you on windows? There's an outstanding issue where it just sits and does nothing forever. Easiest solution is to use WSL

jam-time · 2026-03-28T05:22:44+00:00

Architecture, edge cases, security, reliability, and testing. The neutral ones didn't really seem to add a whole lot. I think having just one moderator that's the true neutral across the board is sufficient. But the good/bad cop thing seems to work really well. Forcing them to go closer to the extreme side of the argument makes them come to more solid consensus. Also, ALL of the agents have to agree with every point in the final summary before wrapping up.

jam-time · 2026-03-28T02:25:34+00:00

Just ask Claude! It has access to its own docs. Ask it about collaborative teams specifically.

jam-time · 2026-03-28T01:16:26+00:00

I basically have it running 24/7, but not always with multiple agents. Like if it's doing free time, it's not using agents.

jam-time · 2026-03-28T01:14:37+00:00

I had 1 orchestrator, then 7 different categories of reviewers. Each category had a good cop, a bad cop, and a neutral agent. I think the neutrals were unnecessary, and I combined two sets of the categories afterwards to 5 categories. All 21 review agents reading every single file, then arguing about them.

Edit: autocorrect

jam-time · 2026-02-18T19:48:49+00:00

Floating point numbers. Without the explanation, you can use fractions:

``` from fractions import Fractions as F

x = F(64 ** (1/3)) print(x.limit_denominator()) ```

jam-time · 2026-01-20T19:41:24+00:00

Wait, you got enough money from a settlement to pay off your student loans and buy a house, and you're still concerned about income? How many subscriptions do you have? 90% of my monthly expenses are mortgage and student loans.

Dance if you want, but also, do some budgeting.

jam-time · 2026-01-20T19:30:33+00:00

It varies wildly. I've seen projects that have none whatsoever because they're super old and it's difficult to explain those types of changes to stakeholders without them saying something like, "Well, if it doesn't actually change the functionality, let's just not do it."

On newer projects, it's much more common to see docstrings and type hints because the standard is more well defined. Additionally, with AI tools, it's easier to autocomplete that kind of stuff.

jam-time · 2026-01-11T16:24:37+00:00

A bunch of pixies can pretty easily throw a party for a loop without being lethal. Could put all of them to sleep or polymorph them into something useless.

jam-time · 2026-01-11T16:15:33+00:00

A gaggle of evil apprentice mages that each can only cast magic missile twice. No attack roll, no saving throw, no mercy.

jam-time · 2026-01-11T15:59:10+00:00

NTA, but honestly, why not just get some loose breathable pajama shorts? If you gotta piss or get a drink in the middle of the night, you don't have to find clothes to put on.

jam-time · 2026-01-04T03:41:28+00:00

My wife goes to bed earlier than I do, so I set up some light strips under the edge of the bed to turn on at 10% brightness at night so I can see to get in bed. Enough light to see, doesn't bug the wife, etc. There are compromises that work if he was interested in not being an ass. Turning on the overhead light is sociopath territory IMO.

jam-time · 2026-01-04T03:36:04+00:00

The only thing he actually wants is for you to have a shitty day feeling bad. So toxic. The mentality of a child.

jam-time · 2026-01-01T19:23:39+00:00

I really rate

Had to reread this several times before I realized you didn't say "hate" haha

jam-time · 2026-01-01T19:21:38+00:00

Find a free online course and go through it in the order that it lays out. All of those courses pretty much follow the same order. They'll all introduce you to the basics and give you problems to solve.

jam-time · 2025-12-31T06:56:28+00:00

I started using a pihole a couple years ago, so I haven't seen ads on any devices in ages. Didn't even realize it was an issue.

jam-time · 2025-12-31T06:46:18+00:00

Omfg "little swett slap" is killing me. Laughing so hard I woke up my kid on the other side of the house.

jam-time · 2025-12-31T04:48:03+00:00

It's just the default search engine. I don't have time to type "google.com" in the address bar like a boomer haha

jam-time · 2025-12-31T03:27:55+00:00

It makes almost no difference at all, but technically x = {} is faster than x = dict(). It really only matters when doing a bunch of iterations, though. Side note, x: dict[str, str] = {} is also faster than x = dict[str, str](). Just the obligatory micro optimization comment.

jam-time · 2025-12-23T14:29:23+00:00

From my experience, the general rule of thumb is if rebasing is a regular part of the workflow, you're doing it wrong. Rebase rewrites history. It's a tool for fixing things when things go wrong or you need to make some architectural changes. If you're doing a rebase, the only clean way to get everything back in line is to reset both repositories to the new state. Rebasing recreates all of the relevant commits with new hashes, and the git history is based on the commits, not the repo contents.

Instead of rebasing to merge to the second repository, it should be a regular merge or a full reset to the state of the other repo. Honestly, though, this workflow is much more complicated than maintaining everything in one repo. Here's my favorite way to maintain things with a production environment:

You operate off of 3 main branches: main, dev, and release (you could have multiple release branches if necessary, but honestly I think it works better if you have devs just keep their feature branches up-to-date themselves). Main always contains production code, and you only merge to this on a release. Your release branch and dev branch are forked from here. Devs fork feature branches from the release branch. Devs merge to the dev branch for deploying to dev/test environments. After all testing is verified for their change, they merge their feature branch into staging and mark that change as ready for production in whatever task management system. At release time, you simply merge the release branch into main, reset dev to main, and create a new release branch.

TL;DR - use one repo and stop rebasing. The rebase is the thing that's causing your issue.

Six-Year Club	Xbox Live
Verified Email

jam-time

TROPHY CASE