DEV Community: Scrap Labs

Gig app deactivation is an occupational hazard. Price it like one.

Scrap Labs — Tue, 08 Sep 2026 11:48:52 +0000

Gig app deactivation is an occupational hazard. Price it like one.

Every gig app worker has heard the story: account deactivated, appeal filed, six weeks of silence while the rent comes due. The usual advice is to file a better appeal. The useful advice is to price deactivation into your hourly rate before it happens, and stack apps so it cannot zero your income.

Start with the real number. If a deactivation typically costs six weeks of pay on that app, and you earn $18 an hour there, the expected annual cost is that six-week pot multiplied by your yearly deactivation probability. Even a modest 10 percent chance means roughly $460 a year on a part-time schedule, which comes straight out of your headline rate. A gig that pays $18 with deactivation risk can be worth less than one paying $15 with none.

The stack changes the math completely. Two apps with staggered onboarding mean a deactivation is an inconvenience instead of a crisis: you shift hours to the second app within a day, and your six-week loss shrinks to the gap between rates. Multi-apping has its own costs in attention and vehicle wear, but those are calculable. A single point of failure is not a pay rate, it is a gamble with your calendar as the stake.

The 72-hour rule matters more than any appeal template. The first three days after deactivation decide most outcomes: pull your last 90 days of job history and payment records while access still works, screenshot everything, and file once with complete documentation rather than five times with fragments. Appeals succeed on paperwork density, not passion.

None of this is defeatist. It is the same math any contractor applies to dry spells, and gig work is contracting with a dashboard. Workers who price the risk stack apps, keep records current, and treat every platform as replaceable, because to their income statement it is.

The full deactivation playbook: https://extrahustles.com/gigs/gig-app-deactivation-income-risk/

One active request: the subscription dev constraint nobody argues with

Scrap Labs — Tue, 08 Sep 2026 11:47:27 +0000

One active request: the subscription dev constraint nobody argues with

Subscription development services sell on the word unlimited. Unlimited requests, unlimited brands, unlimited revisions. The part that actually makes the model work is the opposite word: one. One active request on the board at a time.

The economics are simple once you see them. A senior engineer costs more than most founders expect once you load benefits and taxes, which is why an agency quote for a full-time-equivalent build starts around a quarter million a year. Unlimited-request subscriptions sit far below that because the queue is the throttle. You can stack fifty cards in Trello, but delivery happens one card at a time, and that single constraint is what keeps the flat fee flat.

For the buyer, the one-at-a-time rule changes how you should write tickets. When everything is urgent, the queue becomes a lottery. When the board has one active slot, you are forced to order work by what ships value first, and the substance of each request goes up. Teams that thrive on this model write smaller, sharper cards: one endpoint, one scraper, one migration. Delivered, reviewed, next.

The comparison people miss is context switching. A developer juggling six clients' simultaneous emergencies loses meaningful time per switch, and you pay for that tax whether or not it appears on an invoice. A serial queue eliminates it: full focus on your card, then the next one. Turnaround claims like 72 hours are credible precisely because nothing else is competing for the same hours.

Unlimited is the marketing. One is the mechanism. Pick services that are honest about both.

Pricing and the full workflow: https://www.poketdev.com/

The home sauna breaks even around session 340

Scrap Labs — Tue, 08 Sep 2026 11:46:07 +0000

The home sauna breaks even around session 340. Here is the actual math

Home sauna people and gym people argue about temperature and timers. Almost nobody runs the numbers on what a session actually costs, which is strange, because that math decides the whole argument.

The honest comparison is not sauna versus nothing. It is a home unit versus the gym lounge you already pay for. The gym membership is a sunk cost either way, so the home sauna competes against zero marginal cost per session, and it starts deep in a hole: a decent 2-person electric unit runs a few thousand dollars installed, plus electricity per session, which for a 6 kW heater at 60 minutes lands near a dollar depending on your rates.

Spread that capital over the warranty window and the per-session cost declines with every use. The break-even against paid sauna access, where it exists, lands in the low hundreds of sessions, not the thousands most people guess. The real question is your session frequency, because the unit prices in bulk: three sessions a week pays the unit off in a couple of years, one session a month never does. A sauna that gets used twice and then holds laundry is the most expensive sauna ever built.

Two practical corrections to the brochure math. First, preheat time is not free; a 40-minute warmup on a weak heater can double the electricity per usable minute, so heater sizing matters more than brand. Second, maintenance is real but small: a heater element replacement every several years is the only line item that moves the total.

If you already train at a gym with a good lounge, your answer is probably gym. If your sessions are frequent and your local access is a spa charging per visit, the home unit wins and keeps winning after session few hundred.

The full break-even breakdown: https://hackedself.com/recovery/sauna-cardiovascular-protocol/

The expected value of a $997 course is usually negative

Scrap Labs — Tue, 08 Sep 2026 11:37:25 +0000

The expected value of a $997 course is usually negative, and the math is simple

Guru course pricing survives on one trick: it makes you price the outcome instead of the product. "The course pays for itself with one client!" Sometimes true. The way to check is expected value, and the inputs are not mysterious.

Take a $997 course teaching freelancing. To price it honestly you need three numbers the sales page never gives you: what fraction of buyers finish the material, what fraction of finishers land paying work, and what that work actually pays in year one. Multiply it through and most courses need a completion-to-income rate north of 20 percent just to break even against a free alternative, and completion rates for self-paced online material hover in the single digits.

The comparison I use: the same $997 spent on used equipment, software, or a freelance listing budget produces guaranteed capability, while the course produces the possibility of capability. That difference is the whole argument. You are not buying knowledge, which is mostly free in 2026. You are buying structure and accountability, and you should price those accordingly.

None of this means courses are scams. The good ones compress a real practitioner's years into a weekend. It means the price is only justified when your honest estimate of follow-through survives contact with your calendar. The people who finish courses would mostly have succeeded without them, and the people who do not finish would have spent the $997 better on literally anything else.

Price your own follow-through first. The course is the cheap part.

The full expected-value math: https://firenomics.com/income/are-guru-courses-worth-it/

Lifetime guaranteed socks are a warranty arbitrage, and the math is not close

Scrap Labs — Tue, 08 Sep 2026 11:33:03 +0000

Sock makers now advertise lifetime guarantees the way mattress stores advertise sales. Darn Tough, Smartwool, Icebreaker: send in the worn pair, get a new pair. Most people read that as marketing fluff. It is closer to a pricing error in your favor, if you actually walk the socks back to the store.

The comparison that matters is cost per decade, not price per pair. A $4 pack of gas-station socks runs about $32 a decade once you count replacements. A $20 guaranteed merino pair runs $20 for the same decade, and the second decade is free, because the guarantee does not expire.

The part nobody says out loud: the guarantee only pays if you mail the socks in. Almost nobody does. The manufacturers know this. The expected cost of a lifetime-guarantee program is a rounding error when 90 percent of buyers never claim it, which is exactly why the offer exists. You beat the system by being the customer who claims it.

Warranty fine print worth checking before you buy: whether the replacement covers wear-through or only manufacturing defects (Darn Tough covers wear; some brands do not), whether you need a receipt (Darn Tough does not), and whether shipping is on you (usually yes, about $5, which still leaves the math lopsided).

The boring conclusion is the right one: buy fewer pairs of the guaranteed kind, actually send back the dead ones, and stop buying socks as an impulse category. Your sock drawer gets smaller and your cost per decade drops by more than half.

The full cost-per-decade ranking with per-pair math: https://durablepicks.com/apparel/lifetime-guaranteed-socks-compared/

Why your AI agent's retry loop is a silent tax

Scrap Labs — Tue, 08 Sep 2026 11:28:47 +0000

Your agent failed a task. It retried. It failed again. By the fourth attempt you have paid four times for work that produced nothing.

Retries feel free because nobody puts them on an invoice. They show up in your monthly token bill as background noise, mixed in with the runs that worked. When we audited real agent workloads, the pattern that stood out was not the cost per successful run. It was the cost of the attempts that never shipped anything.

Three numbers to track before you scale a workflow:

Retries per task, not per session. A session hides the loop.
Token spend on failed runs as its own line. It is rarely small.
The failure reason distribution. If half your retries are schema validation, that is a prompt problem wearing a retry costume.

The math that stings: at a 30% first-attempt failure rate, a workflow that "costs" $2 per task actually costs closer to $2.60 once you count the failed attempts feeding it. Teams that instrument this watch the rate climb as they add tools, because every new tool is a new way to fail.

Fix the failure, not the retry budget.

Full breakdown with audit numbers: https://pastagi.com/engineering/kv-cache-decode-cost/

Flat-rate unlimited development is a pricing bet on your clients. Here's the math.

Scrap Labs — Tue, 08 Sep 2026 08:13:33 +0000

Flat-rate unlimited development is a pricing bet on your clients. Here's the math.

Unlimited dev subscriptions get dismissed as a gimmick, usually by people pricing agency work by the hour. The model only works because of how client request patterns actually behave, and the math is worth understanding whether you're buying or selling development.

The distribution of client requests is not normal

Agencies price hourly because they assume work arrives uniformly. It doesn't. A typical product month looks like: two weeks of small tweaks and bug fixes that take an hour each, then one week where everything freezes for a launch, then a burst of real feature work.

Flat-rate pricing bets on that distribution. The subscription fee prices the median month, the client sends everything without approval friction (because each request doesn't need a quote), and the queue does the pacing. The client's real cost control is priority ordering, not budget approvals.

What actually breaks the model

Three things, from watching this play out: clients who treat unlimited as a staff augmentation contract and send 40 hours a week of requirements, work that needs dedicated specialists rather than full-stack generalists, and clients who need guaranteed response times. Good flat-rate shops handle this with queue limits and fair-use terms instead of hourly meters.

The interesting part for engineering buyers: the model transfers estimation risk from you to the vendor. With hourly billing, a badly scoped three-hour task costs five. With flat rate, it costs the vendor. Their incentive is to scope well and ship, not to bill the ambiguity.

The full breakdown of how flat-rate development pricing works, including when it's the wrong choice, is at Poket Dev.

Cross-posted from Poket Dev's blog on flat-rate software development.

What actually wears out on a guided knife sharpener

Scrap Labs — Tue, 08 Sep 2026 08:09:38 +0000

What actually wears out on a guided knife sharpener

The fastest way to ruin a guided sharpening setup looks the same on a $40 clamp and a $500 one: crank the vise until the handle stops. On a thin kitchen blade, that torque bows the steel between the jaws, the edge reference shifts a degree between passes, and the angle repeatability you paid for quietly disappears.

Every system can apex an edge when new. Day-one sharpness is table stakes, and a review scoring week-one cutting performance tells you nothing about decade value. What separates a ten-year workhorse from a drawer ornament is whether the precision interfaces still agree with each other after years of clamping cycles.

The wear points, system by system

Five guided systems, five different first-to-fail parts:

Lansky: the angle fork develops play first. Cheap fix, but it takes the system's accuracy with it until you notice.

KME: rods and bearings go next. The clamp stays true longer than the budget systems, which is most of what you're paying for.

Edge Pro: the stones wear before the fixture does. Good design, but budget for abrasives as a running cost, not a one-time buy.

Wicked Edge: the most precise of the bunch, with a discipline tax. The newer vise guidance amounts to a confession: tighten to contact plus half a turn, because jaws built to flex will deform under old-school torque.

Tormek: slow wear by design. The tradeoff is speed, and the consumable math gets interesting over a decade.

That last point deserves its own mention: consumable cost per decade can beat the machine price. A system with cheap fixtures and expensive stones can cost more over ten years than its sticker suggests, and vice versa.

The full ranking with failure modes, thin-blade clamping technique, and the decade cost math is at Durable Picks.

Cross-posted from Durable Picks, where gear gets judged on cost per decade, not week-one impressions.

I logged every rideshare shift for two weeks. The saturation numbers settled the argument.

Scrap Labs — Tue, 08 Sep 2026 08:09:07 +0000

I logged every rideshare shift for two weeks. The saturation numbers settled the argument.

The airport lot fills up by noon. The surge map goes quiet. The group chat blames Uber driver saturation. None of that separates a genuinely flooded market from a seasonal dip or a badly built schedule.

Saturation is a measurement problem, and the numbers that solve it are already in your possession. Every shift produces requests, idle minutes, unpaid miles, and queue waits. Log two weeks of shifts, apply a real vehicle cost, and you can rank your options by effective hourly pay instead of arguing about vibes.

Saturation is driver-hours, not driver headcount

The unit matters. Supply is not the number of drivers registered in your metro. It's the number of driver-hours competitors pour into the blocks you actually work. A city can carry 20,000 registered drivers and still pay well on Friday nights if only a few hundred are online then.

Slow weeks have three distinct causes, and only one is oversupply. Seasonality drags demand down everywhere for a known reason. Schedule drift puts you online at hours that were never strong for your market. Only a across-the-board drop in requests per driver-hour, measured over weeks, points at real saturation.

The five stats that expose an oversaturated market

From two weeks of logs you can compute: requests per online hour, busy-time share, dead mile ratio, queue wait at your regular airport runs, and effective hourly rate after the real vehicle cost. The article walks through thresholds for each and what they mean together, because one weak number with four strong ones usually means a schedule fix, not a market problem.

The worked example in the full piece ends with a driver discovering his Tuesday daytime block was dragging his weekly average below minimum wage while his weekend nights were fine. The market wasn't saturated. His schedule was.

The complete logging protocol, the five-stat scorecard, and the ranked list of standard fixes by effective hourly rate are at Extra Hustles.

Cross-posted from Extra Hustles, where side hustles get priced by true hourly rate, receipts first.

Your cold plunge costs more than the sticker says. Here's the per-session math.

Scrap Labs — Tue, 08 Sep 2026 08:08:35 +0000

Your cold plunge costs more than the sticker says. Here's the per-session math.

The local news playbook for home recovery lab costs goes: multiply heater wattage by your electricity rate, gasp at the chiller bill, done. That produces the wrong purchase decision every time, because the kilowatt math is real and also the smallest number on the page.

Priced honestly, per session at the frequency you actually train, the dominant cost of a home recovery setup is the purchase price amortized over how long the thing lives.

Where the trap actually lives

Of the three big purchases (sauna, cold plunge, red light panel), the chiller-based cold plunge is the only one where running costs can rival hardware cost inside five years. A chiller pulls 300 to 700 watts basically around the clock if you keep the water cold, which adds up fast at typical electricity rates.

The sauna's heater only runs during sessions. The red light panel draws less than a gaming PC. The plunge never stops working.

Then there's the part first-time buyers miss entirely: water chemistry. Sanitizer, test strips, filter replacements, and periodic full water changes. It's not a lot per month, but it's never zero, and it applies every week whether you train or not.

Break-even at your actual frequency

The honest comparison is against a recovery lounge membership, and the break-even depends almost entirely on weekly sessions:

Red light panels pay for themselves in months at almost any usage
A home sauna takes a couple of years at two to three sessions a week
At two sessions a week, the chiller plunge often never pays off at all

That last one surprises people. Run the numbers with a realistic five-year hardware life and honest electricity pricing, and the plunge only wins if you're in it four or more times a week, every week, for years.

The full model uses four inputs (purchase price, expected life, electricity rate, and sessions per week) and prices each modality per session. The complete walkthrough, including the exact break-even frequencies, is at Hacked Self.

Cross-posted from Hacked Self, where I write about self-experimentation with real failure rates and n=1 caveats.

The 4% rule just survived its first real decade. Barely.

Scrap Labs — Tue, 08 Sep 2026 08:07:37 +0000

The 4% rule just survived its first real decade. Barely.

The first big FIRE cohort quit their jobs in the mid-2010s with one instruction taped to the portfolio: withdraw 4% the first year, adjust for inflation, done. That cohort has now lived through the decade everyone warned them about, and the results are in.

The headline says the rule survived. The details say anyone retiring in 2026 should be nervous rather than comfortable.

What the decade actually looked like

A violent bull market ran roughly five years before the first real stress arrived. That ordering matters more than most people understand. The 2020 COVID crash looked terrifying on a daily chart and recovered too fast to threaten a 40-year plan. The genuine stress test was 2022, when stocks fell, high-quality bonds fell, and inflation ate the withdrawal dollars all in the same year.

That joint shock is the scenario the 4% rule research always worried about, with one wrinkle: it landed in years five to ten of retirement rather than year one. A retiree from 2016 had already banked five years of strong returns when it hit, and those early gains are what carried the plan through.

Which means the decade was a demonstration of sequence luck, not rule robustness. A 2021 retiree got the same 2022 crash with no buffer, and their math looks very different.

What the survivors are doing differently now

The retirees who lived through this decade mostly changed their withdrawal behavior, not their portfolios. The patterns that showed up in retrospectives: skipping inflation adjustments in down years, keeping one or two years of spending in cash so a crash never forces a sale, and treating the 4% number as a starting point rather than a promise.

None of that is glamorous. All of it is arithmetic.

If you retired in 2016 with a million dollars, you took $40,000 the first year. After the inflation adjustments of 2021 and 2022, you were withdrawing around $48,000 by 2023 from a portfolio that had taken a real beating. The people still on plan are the ones who cut back to $43,000 in 2023 and let the portfolio heal.

The checklist worth running

Before trusting any withdrawal rate for a 40-plus year retirement, stress it against: a 2022-style joint stock and bond and inflation shock in years five to ten, a lost decade with zero real returns, and inflation running double the planning number for three straight years.

The full year-by-year walkthrough of the 2016 to 2026 path, with the actual portfolio numbers, is at Firenomics.

Cross-posted from Firenomics, where I write about FIRE math and withdrawal rate stress tests.

Why your million token agent run costs what it costs

Scrap Labs — Tue, 08 Sep 2026 08:01:52 +0000

Why your million token agent run costs what it costs

Every token a long-context agent generates gets billed against the whole conversation behind it. That sounds like an accounting quirk until you look at what the hardware is actually doing during decode. Then the bill makes sense, and so do the tactics that shrink it.

I went through the full math on the PastAGI blog this week and wanted to pull out the parts that matter if you're running agents at any real scale.

The uncomfortable arithmetic

To produce each token, the model scores a fresh query vector against the key of every cached token, then blends the cached value vectors based on those scores. The compute is trivial. The reads are not.

Every key and value for every earlier token moves from GPU memory into the compute units on every step. The KV cache size per token comes down to:

bytes per token = 2 x layers x KV heads x head dim x bytes per element

The part that gets people: attention cannot skip a read. The weight that would justify skipping a token is computed from reading that token. If attention ends up caring about one paragraph out of four hundred thousand tokens, the hardware still read all four hundred thousand to find it.

The original piece calls this "peaked attention paying for flat reads" and that's the right way to think about it. Your bottleneck is memory bandwidth, not model capability.

What you can do today

The full article works through a scoreboard of tactics ranked by how much of the theoretical skip each one captures. The short version:

Eviction methods (StreamingLLM with attention sinks, H2O heavy hitters, SnapKV observation windows) throw away cache entries the model is unlikely to attend to again. Each makes a bet about which tokens matter, and each loses a little accuracy when the bet is wrong.

Quantization (fp8, int4) shrinks the bytes per element rather than the token count. Often the cheapest win because nothing about the context changes, just its storage precision.

Prompt compression shortens the text itself before it ever becomes cache. Highest ceiling, most effort, and it interacts with everything downstream.

The honest answer on which to pick: measure your own sparsity first. The article lays out how to do that, and the answer varies a lot by workload. An agent doing retrieval-heavy work has very different attention patterns from one doing long code edits.

The full breakdown with the worked million-token ledger is at PastAGI, including the attention-control research that would change these economics if it ever ships in production models.

Cross-posted from PastAGI, where I write about LLM serving costs and agent economics.