@nateberkopec Nice! I have to check out pitchfork - been using process compose for the last few months along with my https://t.co/sdQdcgvyR2 CLI tool that does the port orchestration part. Spin up worktrees and have all your ports dynamically assigned AND computed into .env files.
The most important thing to add to your CLAUDE.md file since Opus 4.7/4.8. So freaking sick and tired of Claude's ambiguous "worth noting" at the end of every turn.
@josevalim I use the Outport port orchestration tool to make it easy to assign dynamic ports and wire up all the .env files for me. https://t.co/SfTYjdpjDU
@brynary@ohbarye@nateberkopec I recently optimized an 11k example rspec suite from 9 minutes to just over 1 minute. I kept rspec and factorybot but switced to parallel rspec and made extensive use of TestProf let_it_be and optimized factories.
I absolutely hate collaborating with the new Opus 4.7 model. I thought I had trouble before getting it to put things into conceptual language before technical details. Now it just gives walls of technical explanations for simple questions. It's not that I can't understand the technical explanations - I just don't NEED them. Give me simple explanations and I can ask for more detail if needed. Claude, can you just shut up?!
@anthdm 4.7 is absolutely horrible. I just can't even put into words how terrible it is to work with today. It just rambles with extreme technical detail and very poor phrasing. It's like talking to someone who's hyper focused on technical details and doesn't know how to simplify that.
I absolutely hate collaborating with the new Opus 4.7 model. I thought I had trouble before getting it to put things into conceptual language before technical details. Now it just gives walls of technical explanations for simple questions. It's not that I can't understand the technical explanations - I just don't NEED them. Give me simple explanations and I can ask for more detail if needed. Claude, can you just shut up?!
@BeLikeBumblebee@arvidkahl Check out my Outport project. I've achieved the goal of creating worktrees for a project with multiple docker services, an API and 2 web frontends all completely isolated with just a single bin/dev. https://t.co/XMcO29bIq8
@arvidkahl I wrote Outport so I could do this. Just create a worktree and run 'outport up'. Then run your entire stack on fully orchestrated ports. https://t.co/SfTYjdoLOm
"What ports does this worktree use again?"
I built a tool that makes this question disappear.
> "outport up" gives every service deterministic ports
> ".test" hostnames with real HTTPS, no warnings
> Cross-service env wiring β CORS, API URLs, all automatic
> Worktrees get isolated ports and hostnames
Try it out β
https://t.co/VNR9UVaEjg
I've been building Outport β port orchestration for local dev.
One config file gives every service a .test hostname with HTTPS, deterministic ports, and cross-service env wiring. Worktrees get isolated ports automatically.
https://t.co/IviNHnx6ZQ