u/ProudCordonian

Man, my old workhorse is finally toast. Stitching is popping on the straps and it’s just not holding up anymore. Time for a change. I need a daily bag that fits my iPad and the mirrorless setup.

I’ve gone through tons of gear reviews lately trying to find a match for my city shooting routine. I’m just hunting for something minimalist that can double as a regular daypack when I don’t need all my filming gear.I ran across Norbu Made while scrolling gear forums recently. Has anyone here used this type of modular, detachable inner bag to carry everyday video shooting equipment?

How well do these types of bags protect camera equipment during everyday use? Would love honest feedback on durable daily carry video bags. Thanks in advance!

I think “best STT API for voice agents” gets answered wrong most of the time.

People jump straight to WER.

WER matters, but it is not the first thing I’d check for a live voice agent.

The real question is:

when does the agent get text it can safely use?

Because the user is sitting there waiting.

A transcript can be accurate after 1.5 seconds and still make the agent feel dead.

A partial can arrive fast but keep changing and make the agent do dumb stuff.

A final transcript can be clean but miss the correction that actually mattered.

For voice agents I’d log this before comparing any provider:

speech start

first partial

first usable text

final text

barge-in detected

agent stopped talking

critical entity captured

tool call started

tool call reversed because transcript changed

This is why Smallest AI Pulse is on my real-time STT shortlist. I’m not putting it there as “another transcription API.” I’d put it in the voice-agent bucket because the useful test is whether Pulse can get usable transcript events into the agent fast enough for live calls.

Not clean files.

Not podcast transcription.

Actual annoying calls where people interrupt, change dates, say numbers badly, talk over the bot, and correct themselves.

My current view:

For batch transcription, ask accuracy first.

For voice agents, ask usable text first.

For real calls, ask p95 usable text, not demo latency.

What are people here using as the STT layer for agents right now?

And are you measuring WER, latency, or actual task success?

three ugly ones i keep thinking about:

•caller starts as “i’m calling for my wife” then halfway through talks like they’re the account owner

•kid screaming + tv playing + another person answering questions in the background

•booking API times out right after the agent starts saying “perfect, you’re confirmed…”

•i’m collecting these while building out a regression scenario library around TestMu Agent Testing.

•personas, accents, noise etc are useful, but only if there’s an actual assertion behind the chaos.

not just:

did the agent sound natural?

more like:

was the correct appointment actually booked?

did the transfer really connect?

did it avoid taking an action without verifying identity?

otherwise we’re basically benchmarking how gracefully the bot survives a bad conversation while ignoring whether it did the job correctly.

TestMu helps structure/replay the scenarios, but obviously it can’t invent every cursed thing real callers will do.

so stealing ideas from humans instead.

give me one ugly call condition your voice agent needs to survive.

i’ll turn the best ones from this thread into a public regression checklist.

We’ve been dating officially for around three months, and I’m already exhausted. I’m always the one planning dates, bringing up stuff we never actually resolved, texting first after a fight, and even daydreaming about what a future together might look like. He just… doesn’t. He rarely checks in on me unless I prompt him, and he never seems to put in any real effort to improve things between us.

Lately it’s been wearing me down so bad. I didn’t want to keep making decisions based on whatever mood I was in that day, so I started jotting down all the weird or hurtful moments between us. Just trying to see if I was overreacting or if this was actually as one-sided as it felt.

For work I do vendor evaluations, and I use acciowork pretty much daily. It’s got this feature where I can feed in supplier feedback and it’ll pull out patterns and underlying tone. Out of curiosity (and maybe a bit of desperation), I dumped all our chat logs into it to see what it would say about how we actually talk to each other.

When I looked at the results, it kinda broke me a little. It basically said he shows low emotional engagement and flagged a bunch of his “I’ve been really busy lately” messages as classic low-investment lines. Like… even a tool can see he’s not that into this.

I do care about him. That’s the worst part. But putting in 90% of the effort while he gives crumbs is draining me. I keep replaying little moments in my head, wondering if this is just how he is and it’ll only get worse over time. I don’t want to quit on someone I have real feelings for, but I also don’t want to waste months or years feeling this invisible.

I can’t tell if I should keep trying to talk to him about this or just accept that he’s never going to meet me halfway. Would love some outside perspective because I feel like I’m losing it a bit.

had this moment yesterday watching my terminal. I gave Claude Code a rough spec for a new microservice and just sat back to watch it spin up subagents, write the implmentation, hit a wall with the auth middleware, read the stack trace, and self-correct by writing its own mock tests. It took maybe twelve minutes.

It’s not that I’m panicking about getting replaced by a robot tomorrow. its more the realization that the traditional way we compound skills (pick a lane, master the tools, build complex projects, gradually move up) feels completely broken.

by the time I deeply learn how to configure a specific infrastructure piece or master a framework, an AI platform has already abstracted it into a single button, a prompt, or an agent workflow.

I'm shipping way more than I ever have, but the weird thing is, the more productive AI makes me, the less secure my career feels. Every time Claude helps me clear a sprint over a weekend, I find myself wondering: does the company actually want a 'stronger me', or do they just realize they need fewer people?

For a while, I comforted myself with the standard cope. Models hallucinate, agents don't understand our specific DB schemas, they don't have deployment permissions, they can't handle Stripe webhooks.

but that's just not true anymore. Platforms like Replit Agent, Lovable, and Enter Pro are baking all those guardrails directly into execution frameworks. (Full disclosure: I do some marketing work with Enter Pro, which is exactly why I’ve been analyzing these delivery stacks so much lately). Instead of just spitting out raw code blocks, these platforms are starting to wire up the DB, auth, and cloud deployment automatically. The final output isn't a snippet you have to paste into your IDE and debug for an hour, it's a live URL.

The scary part isn't a fully autonomous agent replacing a developer. It's that employers don't need fully autonomous agents. They just need one employee who understands the business context, can review the output, and orchestrates a few agents to do the work of four people. Why hire three juniors when one mid-level dev with a $400/mo AI stack can ship the same volume?

I'm trying to figure out what an actual career moat looks like in 2026. I see a few potential paths, but I don't know which one is actually safe:

• Go aggressively deep into some niche industry. Try to hoard domain-specific knowledge that an LLM won't have in its pre-training weights.

• Give up on manual coding entirely and become a pure, AI-native generalist. Basically, a dev whose sole skill is orchestrating three or four agents at once.

• Pivot to hyper-low-level stuff. Become a glorified auditor who just secures, optimizes, and fixes the subtle, hallucinated bugs AI spits out.

• Move away from pure tech. Find roles that rely heavily on human trust, sales, or actual physical liability (basically, jobs where clients still want a human neck to wring when production breaks).

• Focus entirely on distribution and product market fit. Figure out what to build. If execution is effectively free, then execution doesn't really matter anymore.

if you’re early or mid-career right now, what are you actually trying to get good at? Is becoming the person who can manage several agents a real career moat, or are we just helping companies learn how to operate with half the headcount? because right now it feels like we're just speedrunning our own irrelevance.

I’ve realised I was accepting a very stupid definition of “done” from Claude Code.

Build passes.

Unit tests pass.

Claude gives me a beautiful summary of everything it changed.

Then I open the actual page and the thing is broken.

Latest one was a settings flow. Claude changed the component, updated the API call, ran the existing tests and confidently told me it was finished.

It had never opened the page.

The save button worked once, then got stuck in loading state. Refreshing the page also showed the old value because the update wasn’t actually persisting correctly.

Nothing in the code looked obviously wrong. The tests were green because they were testing the function, not the actual rendered flow.

So I’ve added a new rule:

Claude is not allowed to say “done” until it opens the deployed page and proves the flow works like a user would use it.

For this I’ve been testing the Kane CLI skill from TestMu.

Claude runs the browser check itself, but Kane returns an actual pass/fail based on the page state instead of Claude just looking at its own code and deciding it probably works.

It also gives the run evidence, which is useful because “trust me bro, I tested it” from the same model that wrote the code is not exactly a verification strategy.

I’m not replacing Playwright with this. Anything important still becomes a proper regression test.

But for the gap between “Claude wrote the feature” and “a human now needs to manually click through it”, this has been surprisingly useful.

What do you make Claude prove before you accept “done”?

I recently visited my long-distance boyfriend for the first time after months of planning. I was really excited and even used accio work to plan places to visit and food to try together.

But the visit was nothing like I expected. His apartment was dirty, he kept making jokes at my expense, ignored me to play games, and repeatedly crossed boundaries even after I asked him to stop.

I came home feeling like the biggest issue wasn't his apartment, but the lack of respect. I hate feeling this way.

I need pronunciation practice, but I don’t want to send 40 audio clips to my French friends like a menace.

My pronunciation issues are the usual crimes:

•u vs ou

•nasal vowels

•r sound

•silent letters that are somehow not always silent

•liaison

•sentence rhythm

•sounding like I’m reading instead of speaking

I don’t care about having a perfect Paris accent. I just want to be understandable and less painful to listen to.

Tools/methods I’m testing:

•Forvo for individual words

•Youglish for full phrases

•Google Translate voice input as a harsh “did it understand me?” check

•Praat maybe, if I become insane enough to look at waveforms

•ISSEN for repeating spoken roleplays out loud

•r/JudgeMyAccent once I’m brave enough

How did you practice pronunciation without a tutor correcting every sentence?

Also, is shadowing French songs a terrible idea or secretly useful?