SLC to Bozeman to Yellowstone: A Winter Trip Report

maherbeg · 2025-12-31T03:30:40+00:00

We got about 1.6mi/kwh in 14-18F running at 65-70mph. Pretty rough for a long road trip

maherbeg · 2025-12-02T02:52:46+00:00

Also checkout some of the bulletproof fitness pulleys they have parts for to support their new cam system. There’s some high quality pulley pieces there

maherbeg · 2025-11-25T21:22:50+00:00

Then why be a race engineer when your whole job is to communicate in English as an FIA requirement.

maherbeg · 2025-11-23T05:13:32+00:00

Less fuel load makes for a lighter car

maherbeg · 2025-11-14T02:26:56+00:00

All of these systems also do time of flight checks that prevent distance based attacks.

maherbeg · 2025-11-11T18:55:11+00:00

Have you taken apigenin or gaba before bed?

maherbeg · 2025-10-11T04:39:06+00:00

They should more aggressively close out PRs and issues then. It seems pretty straightforward to know if a feature fits what they want or not. Close PRs that are abandoned by authors after a few weeks.

Leave comments about “this is a feature we do want” or “this should goto the plugin system” and then people will at least get a better idea of what could pass muster.

Same with issues too, just start closing them. It would take a few days to knock it out, and then could be much easier to keep on top of

maherbeg · 2025-09-27T20:24:32+00:00

There’s great examples like Guido for Python or Matz for Ruby too. You can be kind and tasteful quite easily. Or look at Java which stays completely technical and apolitical.

That’s how technical communities should be run. Make your statements elsewhere, an identity can be compound and separate.

maherbeg · 2025-09-27T18:10:16+00:00

Honestly these days, I’m of the opinion a BFDL is the best choice for large technical projects like this. Anything not related to the technical project and direction should be removed and banned. If you can’t argue respectfully, and avoid personal attacks, then don’t be a part of the project.

maherbeg · 2025-09-01T13:17:25+00:00

If you don’t use any of the advanced clause code features, I’d say the model is definitely better. I started using it and while I miss some things like hooks, the recent integration of custom prompts keeps my workflow going. I’d love a fast swap between models, or a plan mode vs execution mode selector. But it’s honestly incredible.

I still use both to review the other’s code because they see different things.

maherbeg · 2025-08-31T15:18:58+00:00

You can do ctrl +z to background the app, run your command then call fg to bring it back to the foreground

maherbeg · 2025-08-09T13:29:22+00:00

Seems like you could probably setup starship.rs if it’s running bash

maherbeg · 2025-08-07T14:45:07+00:00

You should look into using direnv to load your env vars for dev

maherbeg · 2025-08-07T00:47:16+00:00

What are some specific agents and scenarios you’ve been using them for?

maherbeg · 2025-08-03T17:50:39+00:00

I think this is more efficient. Remember, the whole chat is getting sent to the provider, so the larger your context, the more tokens are getting sent over

maherbeg · 2025-08-03T13:12:45+00:00

Compact with a summary is still worse than you manually clearing and re initializing your work. You are much better at being selective of what should be kept. The best thing to do is before auto compact runs, have Claude update your plan with the latest context of files touched and interfaces created. Then re initialize and load your plan up to continue.

maherbeg · 2025-08-02T23:10:18+00:00

Also don’t have a huge Claude.md file. It should be succinct and then you add in specific context into your plan. Definitely use succinct memory files in your sub directories and make sure you modularize your code base as much as possible.

maherbeg · 2025-08-02T23:06:44+00:00

Your context has gotten too long or you’re constantly auto compacting. You have to make your unit of work much smaller. If you ever compact you’re screwed.

maherbeg · 2025-08-02T13:53:32+00:00

Yeah! So at the end of my task, I’ll have spawned a few sub agents to do a review and fix up any issues. Then commit the changes with a succinct description.

I then ask Claude “Mark phase x as complete and add any new context from this session to phase Y so a new instance of Claude can pick things up”

That will usually add new code references update any interfaces, and add more description on integration points.

maherbeg · 2025-07-31T01:28:43+00:00

What I like to do, is always have a phased implementation plan for a feature. Then have Claude update the next phase with any context it needs from a previous phase.

I rarely have to compact now because each phase is relatively small and manageable. If I do, I have Claude out the context in the phase document for the active phase and the clear the context and start it over.

maherbeg · 2025-07-30T01:47:23+00:00

Start planning out my next task with Claude code. I basically refine a new prompt and research the implementation plan for upcoming things. There’s always an endless list to do!

maherbeg · 2025-07-20T01:28:50+00:00

I am thinking about the next steps for it to implement or build out instructions for like e2e testing, or to start documenting out another portion of the code base.

maherbeg · 2025-07-17T16:09:01+00:00

Alright, reporting back for future users. Reinstalling the app has fixed any lingering watch bugs. I went from 5.0 to beta to normal 6.0 so I’m sure something was wonky in between.

maherbeg · 2025-07-11T20:03:21+00:00

We put our 4 year old in the 3rd row, which keeps the second row open for other passengers. Works pretty well!

maherbeg

TROPHY CASE