samwho

15 ms·

1. 211.▲
   Designing Better Target Sizes(ishadeed.com)

   1 points by samwho 3y ago|0 comments
2. 212.▲
   I quit my job to work full time on my open source project(ellie.wtf)

   7 points by samwho 3y ago|2 comments
3. 213.▲
   Better Git Conflicts with Zdiff3(ductile.systems)

   1 points by samwho 3y ago|0 comments
4. 214.▲
   by samwho 3y ago

   Same, but writing. I’m very deliberately avoiding things that might not be relevant 10 years from now. This means rarely writing about specific technologies / languages / implementations, and instead focusing on concepts.
5. 215.▲
   by samwho 3y ago

   This looks so cool. I’m extremely excited to get my hands on one of these next year.
6. 216.▲
   by samwho 3y ago

   Maybe a silly question but what are you hoping to achieve by investing time in becoming an expert in a specific container technology?
7. 217.▲
   A Whirlwind Tutorial on Creating Teensy ELF Executables for Linux(muppetlabs.com)

   4 points by samwho 3y ago|1 comments
8. 218.▲
   by samwho 3y ago

   I know you said you have a preference for fresh stuff but I just have to post my all-time faves: - Pushing Through Friction by Dan Na: https://youtu.be/8bxZuzDKoI0?si=FRVYc-XAK_HuRNs3 . Great talk about how ideas get stalled
9. 219.▲
   Journey to the Stack (2014)(manybutfinite.com)

   1 points by samwho 3y ago|0 comments
10. 220.▲
    by samwho 3y ago

    Merry Christmas :)
11. 221.▲
    Interactive code examples for fun and profit(antonz.org)

    4 points by samwho 3y ago|0 comments
12. 222.▲
    by samwho 3y ago

    Thank you! <3
13. 223.▲
    by samwho 3y ago

    It doesn’t apply to successful requests, that’s right. The simulation retries failed requests using various retry strategies, and then after a successful request will wait a configured amount before sending the next request.
14. 224.▲
    by samwho 3y ago

    I've uploaded the code for all of my visualisation posts here: https://github.com/samwho/visualisations . Enjoy! :)
15. 225.▲
    by samwho 3y ago

    I think I've misunderstood what circuit breakers are for years! I did indeed think they were a server-side mechanism. The original commenter's description of them is great, you can essentially create a heuristic based on the obser
16. 226.▲
    by samwho 3y ago

    I think what they mean is something that would cause client to do something at the same time (could be all sorts, some synchronised crash, aligning timers to clock-time, etc.). If the requests aren't user-driven then yes, you likely wo
17. 227.▲
    by samwho 3y ago

    Throttling, tarpitting, and circuit-breakers are something I'd love to visualise in future, too. Throttling on its own is such a massive topic!
18. 228.▲
    by samwho 3y ago

    Not a newsletter as such but I do have an email list where I post whenever I write something new. You can find it here: https://buttondown.email/samwho
19. 229.▲
    by samwho 3y ago

    It uses PixiJS ( https://pixijs.com/ ) for the 2D rendering and GSAP3 ( https://gsap.com/ ) for the animation. The <traffic-simulation /> blocks are custom HTMl elements ( https://developer
20. 230.▲
    by samwho 3y ago

    You know, I hadn't actually considered mentioning it. Another commenter brought it up, too. It's so second nature I forgot about it entirely. I'll look about giving it a nod in the text, thank you for the feedback. :)
21. 231.▲
    by samwho 3y ago

    Totally! Thanks for bringing those up. I tried to keep the scope specifically on retries and client-side mitigation. There's a whole bunch of cool stuff to visualise on the server-side, and I'm hoping to get to it in the future.
22. 232.▲
    by samwho 3y ago

    Yeah! An insidious problem that’s not obvious when you’re picking a retry interval. I had fun with the details of the explosion animation. When it explodes, the number of requests that come out is the actual number of in-progress requests.
23. 233.▲
    by samwho 3y ago

    Thanks for sharing! I’m the author of this post, and happy to answer any questions :)
24. 234.▲
    Retries – An interactive study of common retry methods(encore.dev)

    4 points by samwho 3y ago|0 comments
25. 235.▲
    by samwho 3y ago

    Thanks for the shout out! Funnily, the article in the original post covers the most requested algorithm I never covered: power of two choices.
26. 236.▲
    by samwho 3y ago

    You're welcome! I deliberately didn't go in to that for a few reasons. 1. It would have made this article very, very long. 2. It's a bit out of scope for an article on hashing. 3. I think I might give hash maps their own arti
27. 237.▲
    by samwho 3y ago

    I saw this during the writing of the post! Extremely cool, I mention it a little in my behind-the-scenes post.
28. 238.▲
    by samwho 3y ago

    I agonised over this. I did originally have a version that used 2-element arrays instead, but the resulting code felt more dense and hard to follow. I figured that people who know enough to point this out already know what's up. People
29. 239.▲
    by samwho 3y ago

    This is my eternal struggle: be correct, or be simple. I wrote a version that used 2-element arrays but the code became more dense and I worried about losing people. I was hoping that how easy it would be to translate it to not use objects
30. 240.▲
    by samwho 3y ago

    I didn't know this. I created Haskie during the writing of my Memory Allocation post because I found myself trying to pre-empt reader questions a lot and it was weird to read. Creating a proxy for the reader in Haskie made it flow a lo