Playing around with a Kent Beck-inspired prompt today:
Before implementation, look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."
@southpolesteve@zebassembly I almost have this down
https://t.co/TnWnhDhFZB
I used to use ~, but harnesses have opinions on how to treat it.
With hooks, you can enforce behavior like โonly read from /repos, always make worktrees when writingโ
Oh, and โmise pullโ prunes merged worktrees
โ I love all of that
Personally, I don't get any value from the "social" aspect of GitHub myself.
But, think optional public Issues/Discussions would remove the need dual-hosting OSS on GitHub too.
VoidZero, the team behind Vite, Vitest, Rolldown, Oxc, and Vite+, is joining Cloudflare. Vite stays open source, vendor-agnostic, and built for everyone. https://t.co/DJTpX4Q9Xt
VoidZero is joining Cloudflare.
Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.
Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflareโs platform even closer together.
@marb4n Me too! I saw one today in Workers Builds and started fixing it ๐
There are a LOT of details being paid attention to, and some make more sense to not do the little thing but do the better thing instead ๐
Cloudflare now supports self-managed OAuth clients. Build third-party apps that integrate securely with Wrangler and granular scopes.
https://t.co/khO8inrmOL
If npm is for packaged code, a registry is for open code.
Packages are great for dependencies. Registries are great for code you want users and agents to read, inspect, modify and own.
Learn more: https://t.co/tUoHgMtAMp