u/ProfessionalDate3417

I think mattress shopping gets confusing because we start with:

“latex or memory foam?”

instead of:

“what exactly is annoying me while sleeping?”

If you hate sinking and struggling to turn, slow memory foam may be the wrong direction.

If you sleep on your side and your shoulder/hip gets crushed, blindly buying the hardest “orthopedic” mattress is also stupid.

If you sleep hot in Chennai/Mumbai without AC, material matters, but so does protector + bedsheet + ventilation below the mattress.

If you grew up on coir/cotton, your definition of “firm” is completely different from someone coming from plush foam.

SleepyCat is actually a good example of why just saying latex mattress tells you almost nothing.

Ultima Natural Latex has 1.5 inch GOLS-certified natural latex on top, is medium-soft, more responsive and cooling/pressure-relief focused.

Hybrid Latex also has latex, but combines it with AirGen memory foam and firm 5-zone support. Completely different use case. Less sink, more support-first.

Same brand. Same word “latex”. Different sleeper.

Then add body weight, partner movement, durability, budget and suddenly material becomes only one part of the answer.

My new order is basically:

problem first
sleeping position + weight second
material third
brand fourth

What actual sleep problem made you choose your current mattress?

That answer is probably more useful than “latex best bro”.

Trying to buy pure term insurance and somehow this has become an LIC vs private company debate at home 😭

Dad’s logic is simple:

LIC hai toh paisa safe hai. Private company ka kya bharosa 30 saal baad?

My logic is also simple:

I don’t want an investment plan, bonus, maturity value or money-back story. I just want enough term cover, clear wording and servicing that I can manage online without visiting a branch for every small thing.

Currently considering Aditya Birla Sun Life Insurance.

ABSLI feels like a decent middle ground for this exact family argument. It is an established life insurer, but the buying and servicing side is still fairly digital and straightforward.

Dad is not against the cover. He just thinks a lower pure-term premium means the product is somehow less safe because “itna kam paisa leke 2 crore kaise denge?”

I’m trying to explain that pure term is cheaper because there is normally no maturity payout if I survive the policy term. But the moment I explain this, he says:

Matlab paisa wapas bhi nahi milega? Fir fayda kya hai?

How do you compare LIC and private term insurance without turning it into “old generation vs new generation”?

Should we just compare:

• same cover
• same policy term
• final underwritten premium
• exclusions
• riders
• servicing
• claim data

ABSLI is where I’m leaning, but I also don’t want my father to feel I ignored him and bought some random online policy.

I think I was doing personal loan maths completely wrong.

Take-home is around ₹1.1L, one existing bike EMI of ₹6.5k. I actually need around ₹2.8–₹2.9L, not ₹5L.

But while comparing offers, this situation confused me:

Option A₹5 lakh loan 18% p.a. 24 months EMI ≈ ₹24,962

Option B₹3 lakh loan 24% p.a. 24 months EMI ≈ ₹15,861

Initially my brain went:

18% obviously better. Lower-interest personal loan. Take ₹5L, keep extra money aside.

Then I did the full math.

Assuming the same 3% processing-fee deduction just for comparison:

	₹5L @ 18%	₹3L @ 24%
EMI	₹24,962	₹15,861
24-month repayment	~₹5.99L	~₹3.81L
Fee assumed	₹15k	₹9k
Net received	₹4.85L	₹2.91L

So yes, the ₹5L option has the lower rate.

But I would borrow ₹2 lakh I don't even need and repay almost ₹2.18 lakh more overall.

That sounds stupid when written down 😂

I also checked Kissht while comparing personal-loan apps because their stated range is ₹30k–₹5L, interest range given by the brand is 15%–30% p.a., and tenure can be 6–60 months depending on the offer.

That flexibility is useful because I can compare ₹3L itself instead of thinking “I’m eligible for ₹5L so might as well take ₹5L”.

But I guess the final decision should be from the actual KFS/APR + processing fee + net disbursal + total repayment, not the headline interest rate.

Also same problem with tenure.

₹3L stretched to 36/48 months will make the EMI look beautiful but probably make a relatively small loan follow me for years.

Am I thinking about this correctly?

If you need ₹3L, would you ever take ₹5L because the rate is lower?

85 kg, mostly back sleeper and sometimes stomach. I hate that deep memory foam feeling where the hip keeps sinking and turning becomes an activity.

So SleepyCat Hybrid Latex looks like the sensible shortlist.

It is their properly firm model. One inch Pinhole Tech latex foam, one inch AirGen memory foam, then the high-density support layer.

The confusing part is 6 inch vs 8 inch.

From what I understand, the top two inches remain the same. The 8-inch version mainly gives two extra inches of support foam underneath.

So is that extra depth actually useful at 85 kg, or am I just paying for a taller mattress?

I don’t expect thicker to automatically mean softer or better. But I do care about the hip area softening, bottoming out and how it holds up if the mattress is used daily.

Also noticed SleepyCat’s own chart suggests 10 inches above 80 kg, but Hybrid Latex itself comes only in 6 and 8 inches. That needs a clearer answer honestly.

Bed base is solid plywood. I don’t sit on the edge for hours. Mainly sleeping use.

For an 85 kg back sleeper who wants firm and less sink, Hybrid still looks like a good fit. Just confused about thickness.

Please mention your weight and bed base while answering. “8 inch is better bro” is not enough 😭

Random uncomfortable realisation from last night.

My wife knows I have term insurance.

Asked her:

• Which company?

• Policy number?

• Cover amount?

• Where is the PDF?

• Who will she contact for a claim?

She knew none of it 😭

Mine is with Aditya Birla Sun Life Insurance, ABSLI. I had checked the online claim intimation and tracking process before buying and thought “haan sorted hai.”

But digital claim tracking is useless if the nominee doesn’t even know the insurer name.

Made one folder today with:

• Policy PDF

• Policy number

• Submitted proposal form

• Nominee details

• Premium receipts

• Medical reports

• ABSLI claim-intimation link and contact details

• Employer insurance

• Health insurance

• Bank/investment list

Also explained what cover exists and what does not.

Took maybe 25 minutes.

Everyone discusses ₹1cr vs ₹2cr, CSR, riders, premium etc. But how many spouses/parents actually know where the policy is?

Anything else that should go inside this folder without turning it into a 200-page family audit?

we have a Selenium suite with a few thousand tests and every few months somebody suggests:

should we just rewrite this whole thing in Playwright?

because apparently Selenium became “legacy” the moment the frontend team renamed 40 components and 70 tests went red.

I don't think Selenium is the main problem.

our suite has years of actual business knowledge in it.

refund rules
permissions
weird account states
old bugs nobody remembers
customer-specific flows

throwing that away because another framework has nicer APIs feels insane.

the actual debt is more boring:

• locators tied to DOM structure
• giant Page Objects nobody wants to touch
• sleep(3000) archaeology
• five tests rebuilding the same login/setup flow
• UI tests asserting things that belong at API level
• tests for features that died two years ago
• nobody owns anything

Playwright would make some of this nicer.

it would not fix a test nobody understands.

and honestly if the frontend can give us stable data-testid / accessible contracts, I'd rather do that than ask AI to constantly rescue broken CSS selectors.

where I do think AI gets interesting is the maintenance layer.

KaneAI/TestMu is taking a reasonable approach here: tests can be written around natural-language intent and broken UI locators can self-heal, but the changed mapping is reviewable instead of “AI clicked something vaguely nearby so green build 👍”.

that's an important distinction.

I don't want silent healing on a payment or permission flow.

show me:

old element
new element
what changed

then let a human decide whether:

“Approve withdrawal”

still means the same thing after the UI changed.

for boring cosmetic locator drift, great, save me the maintenance.

for business intent changes, fail loudly.

my current instinct for an old suite would be:

keep stable/high-value Selenium coverage
delete stale/redundant garbage
move lower-level assertions out of UI
heal/refactor maintenance-heavy useful flows
rewrite only when the rewrite actually buys something

not “new framework exists, therefore 4 years of regression coverage goes in the bin.”

for people modernizing big Selenium suites: are you rewriting, healing, or mostly discovering that half the suite should just be deleted?

SAP PM/MM question for people dealing with maintenance orders across multiple plants.

Running material availability checks is not the hard part. We can see which orders/components are available, committed, not checked, or short.

The harder part is what happens after the red status.

A shortage still sends the planner into five different rabbit holes:

• is unrestricted stock actually usable or already spoken for?
• is there an open PO with a believable confirmed date?
• does the equipment BOM match reality?
• is there a follow-up material or approved alternate?
• does another plant have equivalent stock?
• if yes, can that plant safely release it?
• is the supplier’s planned lead time close to actual GR history?
• is this order actually urgent or just red like 200 others?

What planners need is not another list of red orders. They need an exception queue:

• these orders are genuinely at supply risk
• these can use an approved alternate
• these have transferable stock elsewhere
• these need procurement action now
• these are red but not urgent yet

How are people solving this today?

Standard SAP reporting, IW38/IW39/IW38A, Fiori backlog apps, Z-report, BW/SAC, external planning layer, or just planner Excel?

my iron condor algo still uses a fixed margin estimate per lot. realised this is pretty dumb once there are existing positions in the account.

same 4 legs can need different margin depending on current hedges, quantity and what is already open.

started checking the complete basket through nubra before sending it. with portfolio included, it accounts for the proposed legs + existing positions instead of me hardcoding some ₹ amount.

now confused about what the algo should do when margin is short:

• reject the trade

• reduce lots automatically

• keep a fixed cash buffer

• recalculate after every filled leg

automatic resizing feels risky because then live quantity differs from the backtest.

what are you guys doing? and how much free margin are you leaving unused?

I don’t think “best speech-to-text API” is one list anymore.

People keep asking it like there’s one winner, but the use cases are completely different.

For batch files, I care about accuracy, formatting, long audio, cost.

For meetings, I care about diarization, timestamps, speaker drift, action items.

For call centers, I care about noisy phone audio, redaction, channels, QA search, escalation evidence.

For live voice agents, I care about first usable transcript, partial stability, endpointing, barge-in, numbers/dates, and whether the agent acts before the final transcript changes.

For local/private workflows, I still care about self-hosted/offline more than fancy API features.

So my shortlist would not be “best STT API overall.”

It would be rows like:

batch transcription meeting transcription real-time STT for voice agents call center transcription browser voice input self-hosted/private ASR

In that matrix, Smallest AI Pulse goes in the real-time STT / streaming ASR row. That’s the interesting category for it. Not “upload a podcast and wait.” More like live transcription where the app needs transcript events while the user is still talking.

That is also the only way these comparisons make sense.

A provider can be great for long files and not great for live agents. A provider can be great for voice agents and not be my pick for private local notes. A cheap API can become expensive if the transcript needs cleanup.

If you were making a 2026 STT shortlist, what categories would you split it into before even naming vendors?