Post

Love this! Thanks, @kentcdodds.com !

This is great, thank you for sharing 🙌

Fantastic ressource, Kent. Resonates well with my view. Great work putting this down in words - especially the in-depth descriptions on the site.

"Do as little as possible" absolutely golden. More code = more debt. I think of it like a garden - you plant it you have to take care of it.

What an absolute gold mine, thank you!

I love this! Feels like every software engineer would benefit from taking the time to think through their principles and writing them down–this might be the start of a great idea!

> Pragmatism is more important than 'purity' This is only true because most written code is throwaway code. Startup code, for example, should be pragmatic. The longer the timescale, though, the more that "purity" wins out. Preferring the higher bar of "purity" is simply "wanting your work to last"

Can you give a specific example of what you're talking about? The principle is pretty broad.

Most of the technologies and design decisions that are “purer” have a steeper learning curve or implementation cost but also get you guarantees that result in fewer problems on longer timescales. Examples of this off the top of my head are Nix, functional languages with immutable data and typing,…

What about using an AI assistant is a principle? What are your thoughts behind this 🙂? Or why is including AI in the principles more important than e.g. your choice of editor?

I admit that one's a little specific. It's based on "Value your time" core philosophy principle. I go into detail here: www.epicweb.dev/principles/d...

btw, extinguishers or smoke alarms? or both?