Great write up!

Of course, I never stopped editing my code in vi so I missed some of the editor frustrations.

I have shared that frustration, trying to find that alance.

I try to get some basic wisdom through to them to help prevent something horrible happening later, but I don’t want to cause them pain now, either.

I have taken to asking them to take my hand in theirs, when I think they aren’t listening.

The younger kid appreciates the connection. The older kid practices their active listening skills to make me leave them alone sooner.

“We can’t all be robots, Truman. Because if we were all lying to you, I would be. I’m not a Robot, Truman.”

Paraphrased from Noah Emmerich’s fantastic delivery in “The Truman Show”.

Damn. I love this community. Lemmy goes hard.

“My kid can read now.”

“It’s never too early to teach them regular expressions.”

Edit: To be clear, I agree. It’s just great to be among like minded folks, here.

You can make an image of the / drive so it’s easier to restore if they break the system.

That’s good advice. I always meant to do that with computers my kids access.

Although I haven’t ever had my kids break a Linux Mint install. I set them up as non-sudo users and that was enough.

Of course, they grew older and have sudo now, so I should actually think about taking a drive image, now.

Teach them to launch Vim, and they can spend their remaining computer use time using Vim.

Unless they figure out how to exit vim, then please have them come teach me how.

Sorry. I will see myself out.

If they are ready to move beyond block code, Pyxel looks like a fun way to learn some Python.

You could do what my dad did and accidently delete some of the system files, leaving it for your kid to fix.

Now I assume this thread is full of folks trying to figure out if we found our siblings Lemmy account…

My kid was all in on Tux Paint for a good while.

He eventually settled in to make cars and cats, but at first he just enjoyed making abstract art with all the colors and paintbrushes.

This is for me.

I love open hardware and the modern 8-bit game scene.

Good point. With the specs fully open, hopefully we get a portable of this, at some point.

We do always squash merge, which certainly helps.

I was not aware of cliff.toml. Thank you!

Oh, nice.

I’m always looking for another ChangeLog tool.

That said, I never leave my ChamgeLogs up to automation.

My git logs are open to my users for full details, but my ChangeLogs are how I communicate which changes my users probably need to be aware of.

So far, this hasn’t yielded well to automation. But my team is still considering standardizing our commit log messages enough to allow it someday.

We are actually watching Brooklyn 99 right now!

I hope you’re having fun. Because I specifically requested it.

(and Blackboard Monitor)

Still gets me every time. The best Dwarfs call each-other as each introduces themselves. And that Vimes introduced himself this way in an un-filtered moment implies it matters to him, deep inside.

That’s a fair point. I enjoyed the game later out of curiosity - but it wasn’t a “this is your only Christmas gift” kick in the gut, for me.

they’re all some random platformer which sometimes alluded to they had a movie name.

That’s a good point. E.T. was not alone in this, and had more to do with it’s movie that many games that followed.

I played E.T. relatively recently to remind myself what the fuss was about.

The game plays fine (with average Atari bugginess).

It just stands out as an early huge miss for a movie tie in. Almost nothing about the game feels like the movie, or is particularly anything a fan of the movie would seem likely to enjoy.

I say “almost” because the exploring kind of fits. The same exploring that is constantly frustratingly interrupted by pit falls.

It’s really not that bad of a game, though.

I’d argue Superman 64 for the N64 is a worse game by all measures.

I’ve spent some unfortunate time with both, and can confirm. Superman 64 is worse by a pretty large margin.

E.T. is genuinely playable, after a needlessly awful learning curve. Superman 64 still continues to suck even for (shudder) players who have put in the necessary time to learn to play it.

Edit: As others have said before: E.T. is a decent game, it’s just a lousy choice for an E.T. tie-in.

Fans of a beloved highly polished film masterpiece about gentle communication and wide eyed exploration discovered the Atari game was a nearly unfinished punishing high stress race against a merciless clock - which frequently abruptly ended any aspiration a player had of discovering anything beyond the same pit they fell into many times before.

I’m mainly interested in making code reviews a little easier to manage.

One thing I haven’t seen mentioned yet, here: All future diffs become much easier to read if the team agrees to use a very strict lint tool.

I know, I know. “Code changes should be small.” I’ve already voiced that to my team, yet here we are.

I understand from another Lemmy thread that the tradition is to toss the offending team members’ laptop into the nearest large body of water.