u/EnoughGrade1906

My kids have had devices for a few years now and the reality is, even the best parental controls can be a bit of a letdown if you do not double check everything yourself. We set up the Amazon Kids+ app on our daughter's tablet and it's been solid in terms of no ads, no chat features, just books and a few learning games. The timeline for getting them used to it was not instant, took about a month for her to quit asking for YouTube, but now it's just normal. One mistake I made was trusting the default app store recommendations, which led to some sketchy stuff slipping through. To the age where they are asking for their own devices and I am trying to be thoughtful about what they have access to.
I made the mistake of assuming kids mode meant something. Found out the hard way that a lot of apps marketed at children still have stuff buried in them I was not comfortable with. Ads, recommendation algorithms pulling them toward longer sessions, comment sections. Not what I signed up for.
Some parents at pickup were talking about their kids reading more instead of just scrolling and I got curious what they were doing differently. A few of them mentioned apps with no social layer at all. No messaging, no feeds, nothing to chase except the reading itself. What can I do now?

My 8 year old and books do not get along. Never really have. We read together when he was little and it was fine but somewhere along the way screens took over and now suggesting a book gets a full reaction out of him.

I have been hearing from a few parents about reading apps that make it less of a battle. Something with progress tracking and small challenges that give kids a reason to open a book besides being told to.

Tried letting him pick one yesterday. He opened it, poked around, got interested for maybe ten minutes, then asked for his ipad games. Not a win exactly but it's more than I usually get.

I am not expecting a transformation. I just don't want him writing off reading completely before he's old enough to appreciate it. Anyone turned a kid around who started out this resistant and what changed things for them was it the book, the format, something else entirely.

We have an error detection setup in production that's supposed to catch issues, but it's noisy. A lot of false positives, and it still misses things that end up causing outages.

Right now its mostly log patterns and metric thresholds, tuning it is difficult. Lower sensitivity and we miss real problems, raise it and alerts lose meaning.

We tried sampling and some ML based filtering, but it hasn't held up well at our scale.

How are you tuning error detection so it catches real issues without turning into noise?

We used to do storytime every night without a fight. Somewhere in the last year that completely flipped. Now it's a battle every single time. He pushes back on everything, wants his tablet, picks a fight over which book, stalls until I give up.

I have tried no screens before bed, earlier start times, letting him pick whatever he wants to read. None of it is consistent. Some nights it clicks and we get through a whole chapter. Most nights it's a standoff.

I cut his tablet time and that helped a little but now he's just more wound up by the time we get to reading. Like the frustration carries over.

Curious what shifted things for other families???

This is starting to feel like a pattern and I don't know how to break it.

Deploy goes out. ci passed, staging clean, diff looked reasonable. Prod holds for a bit then something starts behaving wrong. Not crashing, not throwing errors, just not doing what it's supposed to do. Wrong calculations, unexpected branching, edge cases hitting paths that should never get hit.

The problem is all my observability is pointed at infrastructure. I know when cpu spikes, when memory climbs, when error rates move. I have no visibility into which paths the code actually takes in prod unless I manually add instrumentation, and by then I'm adding it after the fact to debug something that already happened.

Feels like there's a gap between the system is healthy and the code is behaving correctly. Metrics cover the first one. Nothing I have covers the second.

What are you using for this in prod? Is this just better tracing or is there a different category of tool that actually shows you what your functions are doing with real traffic?

We have a bug that has now reproduced in prod three times and zero times in staging. Same code, same config as far as I can tell, completely different behavior.

The error only shows up under real concurrency with real user data hitting specific edge cases in our validation logic. Staging just doesn't have the traffic shape or data variety to trigger it. By the time I've set up any kind of repro it's already resolved itself in prod and I'm back to guessing.

I have added more logging but that just means more noise to dig through next time without knowing which execution path triggered the error. I have tried load testing in staging but synthetic traffic doesn't replicate the actual patterns.

Production error detection feels impossible when the error only exists under real conditions. Feels like the only way to catch this class of error is to observe it happening in prod in real time, but I don't know what that tooling looks like beyond just cranking up log verbosity and hoping.

How are you handling this for bugs that simply won't show anywhere else. Is there a smarter approach than logging everything and digging through it after the fact?