Join 📚 Josh Beckman's Highlights
A batch of the best highlights from what Josh's read, .
I make a practice of regularly checking in about whether I have a dutiful stance towards some aspect of my research. Once I notice, I can usually summon curiosity by asking lots of questions, imagining potential implications, and so on. Michael Nielsen has some great notes on tactics for this in his [Notes on creative contexts](https://michaelnotebook.com/creative_context/index.html).. Often I need to improve the framing, to find one which better expresses what I’m deeply excited about. If I can’t find a problem statement which captures my curiosity, it’s best to drop the project for now.
Cultivating Depth and Stillness in Research
Andy Matuschak
To write about something hard to explain, write a detailed letter to a friend about why it is so hard to explain, and then remove the initial “Dear Friend” part and you’ll have a great first draft.
Why You Need a Project, a Phrase I Will 100% Use, and a Great List of the Best People in PR
startupy
Examples of things that happen that might not be suitable to model as Domain Events: Something technical (a ButtonClicked, ExceptionThrown etc) happened that we want to record or handle, but it is not described in the ubiquitous language of our domain. Something that happened outside of our bounded context. This could a Domain Event in another system or a different bounded context. Requests to your system. These we define as Commands rather than events, since they can be rejected by our system.
What Are Domain Events? | DDD | Serialized
serialized.io
...catch up on these, and many more highlights
Readwise