lintbrush

Claude Code (Opus or Sonnet) via Herdr with probably 4 or 5 things going at once but at different levels of urgency. Mostly I'll be working on one thing (and maybe two git work trees of a project?) and then then have some other research or analytics task going.

We're a non-profit and Anthropic actually has quite nice pricing for teams licenses so I can do most of what I need in a day within the team "Nonprofit Premium" allowances without paying for extra usage.

I have MCPs connecting to Asana (for bug/task tracking) and Looker (for reporting and analytics) but otherwise the setup for each project is just its own GitHub repo and the occasional local skill (eg one that understands common Looker data patterns for our setup or the wacky history of our Archive).

For longer batch tasks or our automated systems we're using various models through Bedrock so I can track it with the rest of our AWS spend and that's been working quite well.

I'm experimenting with Opencode and Openrouter/Bedrock. If Claude Code didn't exist I would think Opencode was a miracle from heaven so it's a nice backup Anthropic pricing gets unweidy.

Just stumbled onto this and it's pretty great! I actually had claude use Marp to come up with some slides to insert INTO the video at moments I was jus ttalking, not demoing, worked great.

Yep, that's correct about the Juno 60. There are people still sharing WAV files of the original factory patches which is cool to be able to re-load now and again.

This is great work and a really nice take on the concept. As someone else said, midi output would be really cool as this is a great just doodley scratchpad but once you have something great it'd be awesome to build on it.

I agree that maps, looking up locations etc is the one ingrained Google-user pattern that always leads me to a weird dead end and has me popping back over to google for JUST that query.

I don't know if there's a toggle I just haven't found yet for just automatically using Google Maps for location based searches until their feature gets a little better.

Beyond that, Kagi has been an incredible breath of fresh air.

The idea of noodling around in the Fairlight UI is pretty fun. Always nice to get an insight on how various limitations or structures of older instruments led to the music they created.

Nothing beats just getting your hands dirty. This video actually does a great job of covering the basics that are common to 99% of synths, physical or virtual: https://www.youtube.com/watch?v=JfJ9Dbjz6cs