pifs VS principles

This is actually a thing: https://github.com/ajeetdsouza/pifs

> I've always found the "hey Twitter friends, I wrote a guide, buy it for $90 now!" stuff super unethical anyways. First of all, the information they sell that way is 100% available for free somewhere else or is useless. They're usually mediocre in their fields, but have chops for social media marketing.

true.

but the fact that every and all information is be encoded within pi[1] does somehow not slience the intellectual property debate.

probably because arrangement and presentation also have value.

[1] https://github.com/ajeetdsouza/pifs

Theoretically, not depending on the content, nearly 0: https://github.com/ajeetdsouza/pifs

- Nice repository of tips and info for software engineering teams, made by a burnt out team leader: https://principles.dev/

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/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.