bizzleDawg

After the complete mind melting of 2 seasons of "the rehearsal", this was my exact path too

One can only assume the funding was needed to be able to afford K8s and postgres? /s

It's almost like there an implied "wait for part 7 guys and remember to like and subscribe"

My (and many others) normal workflow includes a planning phase, followed by an implementation phase. For me the most useful time for fast mode would be during that planning phase.

The current "clear context and execute plan" would be great to be joined by a, "clear context, switch to regular speed mode, and execute plan".

I even think I would not require fast mode for the explore agents etc - they have so much to do that I accept that takes a while. being able to rapidly iterate on the plan before setting it going would make it easier.

Please and thank you, Boris.

Only in the same way that the pixels displayed in a browser are not a tree structure that you can diff - the diffing happens at a higher level of abstraction than what's rendered.

Diffing and only updating the parts of the TUI which have changed does make sense if you consider the alternative is to rewrite the entire screen every "frame". There are other ways to abstract this, e.g. a library like tqmd for python may well have a significantly more simple abstraction than a tree for storing what it's going to update next for the progress bar widget than claude, but it also provides a much more simple interface.

To me it seems more fair game to attack it for being written in JS than for using a particular "rendering" technique to minimise updates sent to the terminal.

Max 5x ($100)

I have formal requirements for all implemented code. This is all on relatively greenfield solo developed codebases with tools I know inside out (Django, click based cli etc) so yes. Thanks so much for your concern, internet person!

I spent a whole day running 3x local CC sessions and about 7 Claude code web sessions over the day. This was the most heavy usage day ever for me, about 30 pull requests created and merged over 3 projects.

I got a lot done, but my brain was fried after that. Like wired but totally exhausted.

Has anyone else experienced this and did you find strategies to help (or find that it gets easier)?

I was thinking that on this, folks need a cron task to run a trivial prompt at 5-6am and get that 5hr timer running so that it the majority of the quota is available in the working day morning, and then a new 5hr block starts around lunch time. This should maximise use of included tokens by a standard work day spanning 3 blocks rather than 2

I'm in a similar position of never having found a use where memorising lots of facts would be useful. The main use I keep seeing is vocabulary building when learning a language. I'm sure people are using the system for learning other stuff too though?

Seeing this did make me wonder how I might be able to get better at memorising important parts of iso/iec standards at work, but I can't see how that maps to flashcards

I've been following 16hr fasts by skipping breakfast and eating my first meal at around 12:00 each day. Normally have an afternoon snack, then dinner at 18:00 with my young family. Perhaps a sweet treat by 20:00 after putting the little one to bed. Honestly, it's not that tricky if you bulk up lunch a bit.

Edit: As a sibling comment says quite rightly, you do feel hungry in the late morning, but reacting to that feeling is optional

Correct, thanks!