scottgg

5 ms·

1. 31.▲
   by scottgg 1y ago

   This seems cool! I’ve had success giving Claude Code the ability to reflect on runtime performance by making it write rust perf benchmarks and then reflect on the results; this seems like a nice generalization
2. 32.▲
   by scottgg 1y ago

   You can do it to any change in the repo and everything gets automatically rebased downstream of it - so if you three nicely structured changes you can go change the first one if you need and it just works. I’m selling it short a bit - it do
3. 33.▲
   by scottgg 1y ago

   I reckon that nice commits breaking up a big PR that can be merged straight to main is the best outcome. But - I also think that always squashing is a natural reaction to "twiddling with the past" being difficult (but possible!) w
4. 34.▲
   by scottgg 1y ago

   Since moving to jj[1] as a git-compatible alternative, I’ve found it so easy to make clean commits I do it by default for everything - usually 1/ refactor 2/impl, 3/ docs. Because you can always just “jj new” on top of an exi
5. 35.▲
   by scottgg 3y ago

   you get _a_ strong credential, or you get _strong credentials_ , probably There's a lot going on in there!
6. 36.▲
   by scottgg 3y ago

   I recently did the same thing with AWS, using the CDK to make it easy to add and remove regions [1]. I use it to hop my traffic around as required. [1] https://blog.scottgerring.com/automating-tailscale-exit-node...
7. 37.▲
   by scottgg 4y ago

   There’s also DN42 [1] if you want to mess around with a bigish BGP network for free 1. https://dn42.eu/Home