A batch of the best highlights from what Tristan's read, .
Private: Only accessible within the existing scope (defined by curly brackets) or extensions in the same file.
Swift Cookbook
Keith Moon and Chris Barker
Passion: teams focused on delighting customers, being the best at getting better, embrace failure and get stronger because of it. Selflessness: collaborate and share knowledge and code across organization, innersourcing, making space for others’ voices and helping others win. Accountability: own the outcomes even when they’re hard; how you do something is as important as what you do.
The DevOps Handbook
Gene Kim, Jez Humble, Patrick Debois, John Willis, and Nicole Forsgren
If you apply this technique to your own tasks, don't be afraid to experiment with customizing the instruction. `Let's think step by step` is rather generic, so you may find better performance with instructions that hew to a stricter format customized to your use case. For example, if you were you can try more structured variants like `First, think step by step about why X might be true. Second, think step by step about why Y might be true. Third, think step by step about whether X or Y makes more sense.`. And you can even give the model an example format to help keep it on track, e.g.: