Christopher Little-Savage

A really interesting piece from an old supervisor of mine. Lots of interesting threads to pull and ideas to explore! cacm.acm.org/opinion/ai-s...

just put everything in one place. never serve more than one person at a time. if they gotta wait they gotta wait. can we do that

I've learned a lot of new stuff in my field from ChatGPT, but personally nothing beats books for exploring totally new fields. I think it's because authors know what you need to know, and explain exactly that. Whereas AI explains what you ask it to - and I'm often asking the wrong questions.

me: I wish baby got sick less. Nursery is such a germ pit. also me: isn't it cute how he shares his spoon with the dog?

Has anyone tried something like code splitting but for your backend? The idea being to let different parts of your monolith scale independently and stave off microservices a little longer

Have you ever tried just reading the docs? TIL I learned about `.git/info/exclude`. It works exactly like .gitignore, except it’s not tracked by Git so it only applies to your machine. Great for excluding tooling config that your team haven't adopted yet! git-scm.com/docs/gitigno...