101–110 of 906 posts
I’m reading the Raft paper: https://raft.github.io/raft.pdf
+ Jon Gjengset's writeup on some of the "gotcha"s: https://thesquareplanet.com/blog/students-guide-to-raft/
We had a gameboy as a kid, but the ZX Spectrum (also Z80 CPU-based) meant more to me so hope to take what I learn from the great articles from imrannazar.com and apply to writing a ZX Speccy emulator (the gameboy had dedicated-hardware for sprites etc so not everything will be transferable).
Yes both gameboy & spectrum emulators in javascript have been done already, but this is just for personal learning/fun/itch-scratching. It has been quite instructive both from a remembering-fundamental-cs-classes/how-computers-really-work perspective, as well as modern javascript
Reading: The General Theory of Employment, Interest, and Money by Keynes. Studying: The Molecular Biology of the Cell by Alberts et al and Advanced Macroeconomics by Romer.
https://www.versobooks.com/books/2499-the-general-theory-of-...
I am learning how to write. After seeing a few people with blog, I realize the importance of writing. It makes you think clearer and understand a subject deeper.
May I suggest setting yourself a fixed schedule (let's say, one article published every two weeks or so) and sticking through it? Your initial articles will probably suck, but you'll gradually improve in the upcoming months.
I figure it's gonna be a while before we get back to normal. People will continue to crave attention and video is a more scalable way to disseminate your knowledge vs traditional meetings or Zoom calls.
I'm specifically looking at doing more analytical video game streams and educational Machine Learning content for the advanced n00bs.
Who we view as charismatic will change quite a bit in the near future since we can endlessly edit and improve our message before we share it with others.
I've been trying to build real systems with Microsoft's Durable Functions. I've been utterly fascinated by the patterns that have emerged on some of them.
What are those patterns? I've used Azure functions a lot but never had (I think) a use case for durable ones.
Watchdog Pattern: A orchestration needs to succeed. A watchdog entity checks up on it to make sure that failures are reported and dealt with appropriately (ie, refunding a payment if it fails catastrophically)
Circuit Breakers: Polly has their own implementation, but I found it easy enough to implement my own (don’t recommend in production, just use Polly)
No database: it’s a bit slow to get things done, but it’s amazing to create entities that don’t need to store state in a database. Paired with the watch dog pattern or preloading, you can have entities running “in memory” which may be faster than a dB lookup or the data could be projected to a db for analysis. I’ve been exploring this most recently.
Aggregate entities: these just count things, or store references to important entities that they count. This works amazingly well instead of COUNT DISTINCT queries.
For me it looks like this, I'm working on a bootstrapped simple SaaS tool for devops (docker container monitoring):
- Clojure so I'm learning FP and Lisp
- Clojurescript/Reagent so I'm learning SPA/react
- MongoDB so I'm learning NoSQL
- Vim so I'm learning editing like a boss
- SaaS so I'm learning marketing (SEO/Blogging to start with)
So far I’m having success and fun with Pleroma and Matrix.