34 points | by b_llc 3 days ago
4 comments
A stateless pattern I use to batch telemetry at the edge while driving Cloudflare write costs to zero.
Cool pattern. Critics will say “falsehoods programmers believe about time” but it’s a cloud service, any time oddity that would break this would also break a lot more important stuff, so it’s fine.
Ugly code though.
// env QUEUES = [EVEN_QUEUE, ODD_QUEUE] // producers env.QUEUES[hour % 2].send … // consumer env.QUEUES[1 + hour % 2]
> env.QUEUES[1 + hour % 2]
// results in index 1 or 2 as js has precedence for */% over +-
So something like the following, for your desired visual succinctness? ...
env.QUEUES[hour % 2 ^ 1]
// results in desired js index 0 or 1
I wonder if any of you using AI code assistance regularly might tell an old hack like me if your code review tools would have caught such a bug?
Can you explain the pricing here?
A stateless pattern I use to batch telemetry at the edge while driving Cloudflare write costs to zero.
Cool pattern. Critics will say “falsehoods programmers believe about time” but it’s a cloud service, any time oddity that would break this would also break a lot more important stuff, so it’s fine.
Ugly code though.
> env.QUEUES[1 + hour % 2]
// results in index 1 or 2 as js has precedence for */% over +-
So something like the following, for your desired visual succinctness? ...
env.QUEUES[hour % 2 ^ 1]
// results in desired js index 0 or 1
I wonder if any of you using AI code assistance regularly might tell an old hack like me if your code review tools would have caught such a bug?
Can you explain the pricing here?