MajorHavoc @ MajorHavoc @programming.dev

Posts

14

Comments

3,371

Joined

2 yr. ago

Moderating

---

"Everything printed by Tabloid is automatically capitalized, and an exclamation point is added. Why would you want anything else?"

Finally an opinionated programming language with the right priorities.

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.

I intend to leave a complex and detailed inheritance plan for my Hot wheels.

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.

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.

This gets better the more I notice. Bravo.

I want to spend Christmas at Lance's house.

Very nice. What frameworks are you considering binding your game in?

We are actually watching Brooklyn 99 right now!

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

If a bit too bold in the presence of his Imzadi.

I figure Riker stopped holding things of that nature back in front of Troi, after he realized that between her empathy and knowing him well, he wasn't fooling her, anyway.

One could argue Tetris could carry the whole competition alone, but it is joined by Mario Brothers, Duck Hunt, Spy Hunter, and Gauntlet in 1985

I would leave it at that, except Pac-Man, Frogger, Galaga, Defender, and Donkey Kong make 1981 a contender

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.

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.