ꌗꉓꃅ꒒ꍟꀎ𝔻ꍟℜ𝕊𝕋𝕌ℝℤ

South African, living in Germany, left-leaning, deeply aligned with the opening lines of the Grundgesetz that declare all people to have inherent worth. Nerdy of nature and short of stature, I bend code and words to my purposes yet revel in my sports and thrive in the hills and high places.

  • 3 Posts
  • 8 Comments
Joined 17 days ago
cake
Cake day: December 2nd, 2024

help-circle



  • I do like putting task-cards in columns and dragging them from left to right but I’m explicitly not going the Kanban route nor the Scrum route. I reject the prescriptivism that inevitably accompanies those “brand name” methodologies, even while I acknowledge that both methodologies do encompass several excellent ideas one might usefully borrow.

    In fact, I always rather liked Trello simply because one could do whatever the heck one wanted with its boards – and the hotkeys were brilliant. (If I test out Planka, hotkeys will be evaluated for sure!)

    Sadly, Trello devolved into and, yeah, I wouldn’t touch any Atlassian[1] product with a barge pole, today, nor have I in years.


    1. Do they still charge for dark-mode in some of their products? Anyone who has managed a large team that includes neuro-diverse developers knows that dark-mode is tantamount to an accessibility feature and charging for it is just a dic•-move. ↩︎




  • I’m fairly certain that the original authors recommended using another generator – like split-mix-64 – to extrapolate low-entropy seeds to the required state width. Using high-resolution time as a seed is common practice throughout software development and I think they were envisioning split-mix-64 to be adequate to get decent seed entropy from a linearly increasing timestamp. I’m certain it would be adequate to widen 32-bit seeds to the required width.

    If my memory is correct, the reasoning was that split-mix-64 – although not as robust a PRNG as the XO*SHIRO family – is trivial to compute and reaches a reasonable level of entropy without needing many iterations.

    It looks like[1] the state width is 256-bits, anyway – not 64 bits.


    1. I’ve lost my references and don’t have time to go digging through archives right at the moment but I pulled up my Rust library that implements my PRNGs (which is a port of a C++ re-implementation that exploited learnings from implementing a C# library to replace Microsoft’s original, slow .NET PRNG, which was based on the research paper’s reference implementation, and ran in production for years and years…) ↩︎