1. Get an idea, write it down in Notes, mull over it for 2-3 weeks, do research and create an outline, write the article
2. I had something to get out there, so I wrote something on Friday. Committed to myself that I'd do the same next week and I'm now 4 weeks in.
3. I think of it as sharpening my writing muscle, especially with regard to what topics I choose and how I tell that story. I'm willing to consider a lot of my current work as a "throwaway" until I get better at my craft. Eventually, I'll develop a proper audience and hopefully, something will go viral.
4. Perfectionism was a big one, previously I would always put things off until they're perfect. Now I have to ship every Friday so I'm less focused on getting it perfect. Another was that the story I want to tell shifts while writing it, hopefully, I get better at this over time.
> The unanimous 23-to-0 vote ratified a proposal put forward last month by UC President Janet Napolitano to phase out the exams over the next five years until the sprawling UC system can develop its own test.
Hey, I'm currently writing a newsletter on reframing ideas from pop culture using first principles, would appreciate if you could take a look: https://reframing.substack.com/.
You're processing an average of 1.33 million trades/hour. Let's double that and round up for peak traffic, that's 3 million trades/hour or 833.33 trades/second.
Unless I'm missing something, you only need 1 line. What's the problem here?
You can use different technologies based on your use case, but you probably need all the pieces outlined above. As someone else has mentioned, if you're looking for trade-offs between different technologies, I'd recommend "Designing Data-Intensive Applications" by Kleppmann.
Curious to know what the differences are vis-a-vis big data tools like Hadoop or Spark; as a user of those tools I recognized a lot of common failure patterns in the example above. Thanks!