1,115 karma · joined January 11, 2013
I write a bunch of features. Most are pretty boring. A junior isn't going to learn much by pairing. But occasionally, I do big architecture changes. Those ones are perfect for early collaborative design, pairing, and discussion. The whole team benefits from understanding the architecture better and juniors get to see how seniors think about it. Then you can pair with juniors on the prompting or, more likely, the implementation plan to hand to the agents. That's maybe once a week.
I've led building an EHR totally from scratch at one company and currently advising another as they build their EHR, both totally integrated approaches in industries where you usually have lots of disconnected care (adolescent serious mental illness and ABA/autism care). The state-by-state regulatory challenges are very real! If you want to chat, my email is in my profile!
[0] https://www.kcra.com/article/new-bedford-police-officer-on-l...
Are LLMs better at writing Rust than Zig? I'd assume so, there's way more Rust open source code than Zig. And if so, that's a very solid reason to switch IMO.
I can do most of this with Claude Code, but there's definitely a cost in maintaining it for the whole team.
The WI constitution enshrines the ability to vote. So you may think it's silly and for 99% of people it may be silly, but if anyone is prevented from voting because there's not a reasonable way for them to get a license, their rights are being infringed.
This seems like it'd be great for solo projects but starts to fall apart for a team with a lot more PRs and distributed state. Heck, I run almost everything in a worktree, so even there the state is distributed. Maybe moving some of the state/plans/etc to Linear et al solves that though.