Lol I went through the exact same process.

Damn okay well if the hackers are at that level I guess you’re just screwed.

Let’s see the hackers figure that one out!

Damn great username btw 👌

Okay but how does starting a secure shell help?

Err… Is your team doing planning during standup? I’ve never heard of that, from either people who are on teams that use standups, or from any of the Agile/Scrum literature that I’ve seen. In my experience, standups are typically about either a) coordinating the execution of work that has already been committed to, or b) whoops just a status meeting and everybody’s tuned out.

s/“a god”/“finished for the day”

Yeah but you get a nice ramp-up period where you’re allowed to be bewildered and unproductive. In that time, you can probably pick out two or three grandiose changes (ideally with hot new technologies) to throw on the pile before that period ends, and use them as resume padding and interview stories for the next job.

Unlike the old developers, you aren’t complicit in the mess until a few years go by.

There’s a second-order thing going on though with tech debt that makes it different than just maintenance: Tech debt is when you address a problem in a way that makes future problems more difficult to address. So if the wire-and-tape fix is actually robust, easy to work around, and/or easy to reverse, then it wouldn’t be tech debt. But if it made it harder to unclog/clean the tap, or to fix the next leak, or install/remove things around it, then it would be like tech debt.

What the hell kind of second-rate DBMS doesn’t encode gender into its primary keys SMDH!!

No podium finish for them :(

Maybe there’s a specific person who keeps doing this and they wrote this error specifically for him.

Hell yeah monetized validation! 🤲

I believe it predates Lemmy and isn’t particularly associated with it. I would endorse adopting it either formally or informally, though.

Have an updoot anyway, for good vibes.

But is he rewriting in Rust?

Yeah, I’m wondering about how they characterize “bot activity.” It seems like “any traffic not proximally related to a user’s synchronous activity” is a little too broad.

I’m not sure if fediverse syncing is bot activity. Or my laptop checking for software updates while I’m sleeping. Or my autopay transactions for utility bills.

Ah, you’ve never worked somewhere where people regularly rebase and force-push to master. Lucky :)

I have no issue with rebasing on a local branch that no other repository knows about yet. I think that’s great. As soon as the code leaves local though, things proceed at least to “exercise caution.” If the branch is actively shared (like master, or a release branch if that’s a thing, or a branch where people are collaborating), IMO rebasing is more of a footgun than it’s worth.

You can mitigate that with good processes and well-informed engineers, but that’s kinda true of all sorts of dubious ideas.

You can get in some pretty serious messes, though. Any workflow that involves force-pushing or rebasing has the potential for data loss… Either in a literally destructive way, or in a “Seriously my keys must be somewhere but I have no idea where” kind of way.

When most people talk about rebase (for example) being reversible, what they’re usually saying is “you can always reverse the operation in the reflog.” Well yes, but the reflog is local, so if Alice messes something up with her rebase-force-push and realizes she destroyed some of Bob’s changes, Alice can’t recover Bob’s changes from her machine-- She needs to collaborate with Bob to recover them.

I gotta say, I was with you for most of this thread, but looking through old commits is definitely something that I do on a regular basis… Like not even just because of problems, but because that’s part of how I figure out what’s going on.

The whole reason I keep my git history clean and my commit messages thoughtful is so that future-me (or future-someone-else) will have an easier time walking through it later, because that happens all the time.

I’ll still almost always choose merge instead of rebase, but not because I don’t care about the git history-- quite the opposite, it’s really important to me in a very practical way.