Principal Engineer for Accumulate
Programming @programming.dev The Curse of Knowing How, or; Fixing Everything | Blog
Experienced Devs @programming.dev Is GitHub Copilot worth it to you?
.NET @programming.dev What am I losing by not using the C# Dev Kit?
Programming @programming.dev Why is
crypto.subtle.digestasync?Programming @programming.dev What search engine do you use?
Programming @programming.dev What scientific journals do you recommend?
Experienced Devs @programming.dev Self taught = no imposter syndrome?
Experienced Devs @programming.dev Systems engineering in the software industry
Programming @programming.dev What languages are well suited for testing SDKs written in multiple other languages?
Programming @programming.dev Why should I use rust (as a Go enthusiast)?
Programming @programming.dev How often does branchless programming actually matter?
Experienced Devs @programming.dev How do you organize miscellaneous tasks?
If the squash merge is too big to review then that change should have been broken up into multiple separate changes. Regardless whether you’re using pull requests or some equivalent or directly merging feature branches, if “one unit of work” is too much to review when squashed, then your unit of work is too big and needs to be split up. A unit of work should always be reviewable as a whole.