Live data from Hacker News

The UX on this small child is terrible

mcsweeneys.net

81–90 of 366 posts

Re: The UX on this small child is terrible

#81
post #55
post #36

Earlier quoted context omitted.

We put everything on a plate and offer it to the child(ren). Then, if they become hungry later on, they can return to said plate and continue eating. Dessert is considered "equal", so we place it on their plate. However, that also means that they can't raid the pantry for snacks afterward. It seems to be working. Our oldest ate celery and peanut butter the other day, which is pretty unexpected to us.

In the US most peanut butters include added sugar so your kid may have hacked your system.

Shout-out to Adams peanut butter which is delicious and has zero sugar.

Re: The UX on this small child is terrible

#82

The things children are born not knowing is crazy. The pre-programming is limited ! You have to teach them how to blow their nose. "Don't eat your boogers." Holds finger out to me. I wipe it off. "Don't pick your nose, blow it instead. No, don't pick my nose either."

Reminds me of this old Onion story: http://vaviper.blogspot.com/2019/06/from-onion-study-reveals... Sorry about the copy link, but it seems that The Onion has removed the original story.

Mousing over that link shows the URL is "Study reveals babies are HTML."

I guess that explains a lot.

Re: The UX on this small child is terrible

#83
post #69

Earlier quoted context omitted.

Can somebody explain the "won't eat vegetables" thing? The only place I've heard about this being in issue is in America.

If everything is saturated with salt/sugar/artificial ehnahced flavors/refined everything/fried/etc with "instant hook"-overcranked-at-11 taste, and it's all targeting the lowest common denominator palette, good luck then trying to teach a person to appreciate tomoatoes, brocolli, asparagus, mushrooms, cheeses, and so on...

This is a very good summary of my culinary experience visiting the US. This is not to say that good restaurants don't exist, it's just that cheap/everyday restaurants had everything cranked up to 11. The Cheesecake Factory menu was basically butter and sugar in different ratios.

Re: The UX on this small child is terrible

#85

Earlier quoted context omitted.

Hang on, genuine question - do some people consider blowing their nose vs. picking their nose to be an all-or-nothing choice? If it's dry, I can't blow my nose... Unless there is some method I am not aware of.

I think the lesson learned is really, "don't let people see you picking your nose because... reasons"

File this under "things to re-learn as we emerge from covid and start spending more time in public".

Re: The UX on this small child is terrible

#86

Earlier quoted context omitted.

>who is asking for these features?? The project managers have had a look at some of the competing products, and felt that matching features would be more competitive vs fixing existing bugs.

Yeah, but look at puppy for example - it just eats what you give it. (If anything, the makers of that product should introduce a bit of pickiness tbh). The small child makers should really take an example from puppy - AI is a nice way to get some behaviors trained up, but over-doing it (e.g. in the "what to eat" module) can be just as bad as not enough (compare brine shrimp for the problems of a no AI approach).

Puppy also happily rolls in excrement if you don't run the Leash plugin.

I have the 2017 Small Child Pro and mine tried to eat a cigarette butt that she found in a mud puddle but at least she doesn't roll in goose shit.

Re: The UX on this small child is terrible

#87

I do not recommend VMs or Containers, Small Child requires direct hardware access.

Containerization is actually a valid strategy to help induce the sleep states necessary for both parent and child process functionality, especially since prolonged operations outside the containerized environment may result in the parent process(es) not passing even the simplest sanity testing.

Also remote monitoring as available.

Re: The UX on this small child is terrible

#89
I have a slightly ageing model (my co-developer is adamant there will be no upgrades, please do not suggest) and my problem is that it appears to have defaulted to ICT time (we are at GMT +11). I hear it performing operations well into the early morning, but booting from a cold start any earlier than 9am leads to all sorts of unexpected behaviour and system errors.
Post reply on HN