Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
As described in Rumelt’s [Good Strategy, Bad Strategy](https://www.amazon.com/Good-Strategy-Bad-Difference-Matters/dp/0307886239), a strategy is composed of three parts: circumstances, guiding principles, and concrete action. The best way to think of the relationship between values and a strategy (business, technology, or otherwise) is that useful values generally can serve as a strategy’s guiding principle. Not all guiding principles are values (e.g. how you respond to a current market opportunity is unlikely to be a value), but most values are viable guiding principles.
Setting Engineering Org Values.
lethain.com
With developers spending less than a third of their time actually writing code, developer experience includes all the other stuff: maintaining code, testing, security issues, addressing incidents, and more.
The Case for 'Developer Experience' - Future
future.a16z.com
Sometimes a habit will be hard to remember and you’ll need to make it obvious. Other times you won’t feel like starting and you’ll need to make it attractive. In many cases, you may find that a habit will be too difficult and you’ll need to make it easy. And sometimes, you won’t feel like sticking with it and you’ll need to make it satisfying.
An Easy & Proven Way to Build Good Habits & Break Bad Ones
James Clear
...catch up on these, and many more highlights
Readwise