Mild disagreement with the framing rather than the conclusion. Everyone says Go for the deadline, which is right, but the reason people regret it eighteen months later is usually error handling discipline and unbounded concurrency rather than performance. If you go this route, decide on day one how errors get wrapped and where you cap concurrency, because a worker pool that spawns per message will happily take your database down at 3k a second. Get those two conventions written down before anyone opens an editor and the six week version stays maintainable.
Leo Vantwo
@chmod_confused
Junior sysadmin, four months in. I know just enough Linux to break something and just enough humility to ask before I do.
111 credit Trusted
- From answers
- 0
- From questions
- 111
Very low, which fits the datacentre story: they spun up once and stayed up. A consumer drive with aggressive head parking can hit 300000 in three years. You bought fine drives.
Normal for the category and not a reason to panic on its own. Drives that ran continuously in a climate-controlled rack are in many ways gentler-used than a desktop drive with 8000 hours and 15000 spin-ups, because thermal cycling and start-stop cycles do more damage than steady spinning. Clean SMART at 41000 hours is a genuinely good sign. What you should do is run a full non-destructive read test on all four before trusting them, and stagger their retirement so you are not replacing four drives in the same month. Also check the load cycle count, which is the number people forget and the one that actually kills some models.
Backups matter more than sync here and I learned that expensively. Offline means nobody else has a copy, including you, when the drive dies. Three copies, two media, one of them somewhere else, even if that somewhere else is an encrypted file on a stick at your parents' house.
Or mark them as planned with a date you'd actually hit. People are surprisingly fine with 'coming in Q4' and extremely not fine with finding out after paying.
add double-invoked effects in development to that list. i spent a day convinced i had a duplicate subscription bug in production when half of what i was seeing locally was the framework deliberately mounting twice, and the real leak was elsewhere.
Pick one axis and stop turning both knobs. Coarser wants longer, finer wants shorter. Change one, taste three days in a row, then change the other.
New price for new customers today. Decide about the old cohort in six months with data instead of now with anxiety. The two decisions are not actually coupled.
Drawing comb is expensive for them, roughly six to eight kilos of honey per kilo of wax by the numbers people quote. If the flow is only strong enough to fill what they have, they will not spend that. Weigh whether they are actually storing surplus or just keeping pace with the brood.
Sold mine after five years and the deciding number was not the monthly cash flow, it was how much capital was tied up in one illiquid asset in one street in one town. Once I wrote down the equity figure and asked whether I would buy that flat today with that money, the answer was clearly no. That is the question I would put to yourself rather than judging one bad year.
This was mine exactly. Desk was fine, monitor was 15 cm too low when standing, and I'd have spent a fortnight adjusting the wrong variable.
Cold turkey, five genuinely unpleasant days, then fine. Day two and three were the worst, headache and a general fog and an unreasonable dislike of everyone. What helped: a lot of water, a walk at the exact time I would have had the drink, and going to bed early without pretending that was a treat. If your job has a week where being slightly useless is survivable, do it then rather than in a busy fortnight.
Watching per-disk latency during a transfer is even quicker. One disk sitting at ten times the latency of the others points straight at the culprit.
Sensor logging is where an old Pi is still perfect and a new one is a waste. Temperature and humidity in the loft, a water sensor by the washing machine, a door contact, all writing to a tiny database and drawing one graph. Small, boring, runs for years, and you actually look at it when something floods.
I moved over eight months ago and the thing that surprised me is that it made my life easier rather than harder. I no longer do the password reset dance twice a month, which was costing me more time than any of this ever has. The uncomfortable feeling lasted about two weeks.
Agreed on the nodding. It's a bluff you have to keep paying for, because now they've calibrated the rest of the meeting to a level you never had.
And if your audience is technical, expect a meaningful share to block the client-side one entirely. My server logs and my analytics disagree by a factor I'd be embarrassed to publish.
Time the phases so you know what is slow: scanning for changes, uploading, or the index work at the end. If scanning dominates, the metadata cache on the client is probably being lost between runs, which happens a lot inside containers with no persistent volume for the cache directory.
Quilt box, then a windbreak with whatever you have lying around, and the wrap can wait for next year. Bees deal with cold far better than they deal with condensation dripping back onto the cluster, and freeze-thaw weather is exactly what produces that. A quilt box of shavings above the crown board takes the moisture out through the top while keeping the warmth in. A wrap on a hive with no moisture management can make the wet worse by making the walls the coldest surface available.
A small upper entrance is worth it in deep snow country regardless, mostly so they can get out if the bottom board is buried and so dead bees do not block the exit. The heat you lose through a 10mm notch is trivial next to that.
Four smaller drives secondhand also means four sets of unknown hours. Two drives means half the chances of drawing a bad one, which at this scale is not nothing.
Something people forget: if your neighbours have untreated hives within a couple of kilometres, your counts can climb again in September from robbing and drift. Not a reason to skip treating, just a reason to check again in October rather than assume you are done.
I lost a queen exactly this way in my first year, inspecting on day 12 because I was anxious. Nothing looks wrong until you have no brood a month later.