Lou

Do not build a digital only booth for weddings. I did, it was cheaper, the software was slicker, and the guest experience is a queue of people photographing a screen and then never looking at the gallery. The print is the product, it goes on a fridge, and the mother of the bride will talk about it. If budget forces a choice, cut the fancy backdrop, not the printer.

Not ruined, almost certainly the silty lake. Fine sediment packs into the hollow fibres and evening backflushing with a syringe barely touches it once it's set.

What actually restores flow at home:

• backflush with warm (not hot, never boiling - heat destroys the fibres) water at pressure, from a tap adapter if you have one, for a good two minutes
• soak an hour in a weak white vinegar solution if your water is hard, then backflush again
• if it's still slow, that's the fibres, and no amount of flushing fixes it

Field prevention is the bigger lesson: for anything silty, let it settle in a dirty bag for twenty minutes and pour off the top, or prefilter through a bandana. Two minutes of patience saves the filter.

It's in a cabinet with one small gap at the bottom. Adding an upper vent this weekend, thanks.

Inverter standby, 1.4A. It's been on since I built the thing because I never thought of it as a load. That's 20Ah a night doing absolutely nothing.

Agree on three, with one exception: per-resource layouts that fetch the resource once and share it with all its tabs are worth their weight. projects/[id]/layout.tsx loading the project so the four tab pages do not each refetch it is a real win, not organisation.

The number is not the problem. The question for each one is "does this own something that persists across navigation?" - a nav, a provider, a shell that must not remount. If the answer is no and it just wraps children in a div, delete it and put the div in the page.

Two things worth knowing while you are in there, because they explain most confusion at this stage:

• Layouts do not re-render on navigation between their children. That is the feature. It is also why state in a layout survives and state in a page does not.
• A layout cannot read searchParams. If you find yourself wanting that, the thing you want is a page or a client component reading the hook.

Eleven with real jobs is fine. Eleven where four are decorative means you have four to delete.

Two of them, in different places. They have a five to seven year lifespan and then they're decorations, so write the replacement date on the case in marker.

I did five seasons under a tarp and went back to a tent, specifically for that region. The tarp itself is fine in rain - pitched low it's drier than people expect. The problem is everything around it: no bug protection in early season, condensation inside the bivy soaking your quilt's footbox, and the fact that on the third wet day you want somewhere to sit up and eat rather than lying on your side in a nylon coffin.

If your goal is the kilo, look at a single wall trekking pole tent instead. Around 600-700g, real doors, real bug mesh, and you're not carrying separate poles. That's where I'd spend the money.

Plan for it rather than fight it. I assume night one is a write-off, keep day two moderate, and I'm fine by day three. Twelve years of this and it still happens on maybe a third of trips.