Deleted Comment
Most of the times the solution is not pre-aggregation but proper indexes on foreign key columns (missing fk indexes is one of the most common mistakes in RDB design).
> increase contention and harm scalability
Contention, concurrent connections, high-throughput and the associated race conditions are absolute table stakes for RDBMs. They just won't be taken seriously if they can't handle thousands of concurrent updates. So imho for 90% of projects this just won't be an issue.
> PostgreSQL you increase bloat as every update creates a new row version
This is true, but the complexity has to live somewhere. There will be as many rows added to a materialized view as there will be in the original table.
> Most of the times the solution is not pre-aggregation
This is wrong. Caching = pre-aggregation and is almost always either the solution or a part of the solution to scalability, latancy etc. Don't compute what you can retrieve.
That said, Gemini is very powerful for it's quality long-context capabilities: https://www.reddit.com/r/ClaudeAI/comments/1miweuv/comment/n...
Do you let juniors complete full features without asking questions or make them check in when they get flustered?
HTMX here is making it so the page works without doing a full HTTP form submission + page load for each stage of the "wizard". instead, you write some HTMX stuff in the page that submits the form asynchronously, then the server sends back the HTML to replace part of the page to move to you to the next step in the "wizard", and then HTMX replaces the relevant DOM nodes to make that so.
Go's templating is completely unrelated to any of this happening on the front end - it's just generating some HTML, both the "whole page loaded by the browser normally" and the "here's the new widget state code", and so obviously:
> just use Go’s HTML templating.
is incorrect.
When your Navy literally can't defeat the Houthis, you know for an ironclad 100% certainty that there's zero chance they're capable of beating China -- right off the coast of China!
You actually need a balance of power to prevent an armed political conflict, so the adults in the room will maintain one.
Both were completely safe. On both occasions I slid along the tarmac for about 10-15 meters, I was travelling at around 30-40 mph. I still wear the same leather jacket 30 years later (not for riding) but the synthetic jacket was a right-off.
On both occasions I really smacked my head: don't mess about with sub-standard crash helmets.
So even though leather is better, we're not racing the TT, we're just going from A-B and if you want to wear synthetic you'll be fine at normal speeds. So if you can't wear leather, for whatever reason, don't let that stop you.
I'd add 1 point for the pads, shoulder elbow and back for impact. Mine happen to be `D3o` and are comfortable
I've been thinking about getting a nice, full face helmet (helmets marketed for mountain biking seem like a good fit), but they seem like a pain to deal with at my destination. A lot of times I'll just loop my current helmet on my scooter completely unlocked, because it's cheap enough that I'm not really worried about it being stolen. The full face helmets I have been looking at are an order of magnitude more expensive though, and I wouldn't really feel comfortable just leaving it unlocked by my scooter. Does anyone have any recommendations on this? Or recommendations on other appropriate safety gear for my kind of riding?
The full-face mountain bike helmets sound exactly the ticket, and would protect your face from abrasion if you have an unexpected rapid dismount.
I used to use a small wire cord and padlock that you can store wrapped up tightly onboard. You're never going stop someone determined to get your old lid you just want to prevent opportunists and not be too cumbersome about it otherwise you won't actually do it.
I will say I have heard enough stories about 5k+ electric bikes getting scooped that I'd only ever store one behind locked doors rather than buying a huge bike lock setup.