I imagine teams will shared their principle lists on blog posts and put reflections there. Not all of it would appear on the principles.dev, as I think the ref

I imagine teams will shared their principle lists on blog posts and put reflections there. Not all of it would appear on the principles.dev, as I think the reflective nature would be best handled elsewhere. But acknowledging pros and cons on the website is very valuable. The next big piece of work I have to do is on principle lists ( https://github.com/PrinciplesDotDev/principles/discussions/20 https://github.com/PrinciplesDotDev/principles/discussions/2...) and figuring out what features to include and where to draw the line is going to be tricky... I need to find the principles behind it, really. It's interesting that you say they would be a valuable resource for a junior and mid-career engineers. I agree, it would. What I've found is it generally attracts people who are a) leaders (in some form or other) b) care about programming deeply.