Chat GPT is great at writing comments. Usually writes better comments than I do. I’m using copilot which uses Chat GPT so it’s also repo aware.

Between the legs right?

I’ve been using copilot and find it’s suggestions are perfectly cromulent.

Php: magic quotes?

Haven’t used PHP in a while eh?

Check out PHP 8, it’s pretty nice.

Grey beards merge and increment (ie: senior devs unite and rise up)

This is the reason for me. Sometimes I don’t want to step through the code and just want to scan through a giant list of output.

It’s probably happening during atmospheric reentry considering they’re shipped in from the outer edges of the solar system.

Hollywood hacking or updating packages?

1000000% agree

The speaker of the house is the defacto boss of the parliament and that’s who invited the nazi. Even if they knew the history of everyone who enters the building, the PM couldn’t have prevented the speaker from inviting this guy. Had ANYONE known this guy’s history, this wouldn’t have happened.

The PM isn’t a dictator with total control over who gets to invite people to Parliament

Obviously because the current zero is upside down!

What? You can’t afford 0.60 cents?

I don’t know personally, but a commenter above wrote:

I appreciate that they help stomp out fascist, racist, and anti-trans rhetoric on Lemmy.

So if there’s any truth in that, the backlash could be a bunch of whiney butthurt Nazis.

I think it’s more a case of the tool being used, not because it’s the best tool for the job, but because it’s the tool the dev knows how to use. SSR allows frontend devs to become full-stack devs.

We squash when merging. Final git history is super clean and linear.

Rebase all of your work branches onto HEAD so that conflicts require refactoring the first commit where things don’t match up. This can make conflicts easier to deal with (in my humble opinion) since you deal with conflicts earlier in your commit history as opposed to at the end after ALL of your changes are made.

Plus a linear history is super nice to work with later on.