Reminds me of the o-ring on the challenger

Yeah, fuck that. English is bs enough.

Edit: yeah, that “feeling” is knowing it so well, you don’t totally understand it, and also means it’s hard to convey

This is giving me stress daymares about Spanish in high school.

Still, it’s an interesting point you make.

But then again, with definitive articles you have a bunch of things that are not supposed to convey gender conveying gender. Like a toaster… It would suck to have to remember the gender of a toaster, or, well toasters in general.

Also, a way to never have to work again!

I hear what you’re saying.

First, I hard disagree with you. Overwriting my local version of code is a parachute - not an ideal landing, but better than merging by hand.

Also, my comment was not an attempt to teach everything about git, just to explain what is happening in simple terms, since git requires a lot of experience to understand what those messages mean.

Great meme, and I’m sure op knows this, but for anyone else who is curious…

007 in theory means:

• 00: you have already committed your code to your local code base
• 7: When you try to merge your code with everyone else’s there are 7 files that others have worked on since you last refreshed your local code base.

To resolve this, you need to go file by file and compare your changes with the changes on the remote code. You need to keep the changes others have made and incorporate your own.

You can use git diff file_name to see the differences.

If you have made small changes, it’s easier to pull and force an overwrite of your local code and make changes again.

However multiple people working on the same files is usually a sign of organizational issues with management. Ie, typically you don’t want multiple people working on the same files at the same time, to avoid stuff like this.

If you’re not sure, ask someone that knows what they’re doing before you follow any advice on Lemmy.

If you don’t have apt backups, that is a failure of the process, not yours.

You can also do this by forgetting a WHERE clause. I know this because I ruined a production database in my early years.

Always write your where before your insert, kids.

Speaking of Java RipS. How annoying is it the JS has left Java in the dust as far as looser standards?

Developing in Java: YOU FORGOT A SEMI-COLON ARE YOU CRAZY?! HOW IS THE COMPILER SUPPOSED TO KNOW WHAT TO DO?!

Developing in JS: Who gives a fuck about semi-colons?

I love js. But the date object has always been a total pain. Moment.js is a good package to deal with it, but yeah, it’s currently deprecated, but it would be nice if it or something like it became part of ECMAScript.

I have no idea why it hasn’t yet, except that it might be that js needs to work for everyone, not just the us. So time is not standard.

The place I work decided to name all tables in all caps. So now every day I have to decide if I want to be consistent or I want to have an easy life.

Even using absolute best prackies, developers are gonna find a bunch of stuff to complain about.

As a person who victimizes coworkers like this, I apologize. Thank you for pointing it out, and I will stop doing it.

No offense, but I know how to read a stack trace, and yes locate a familiar file - if you’re lucky enough to have one listed therein.

My point is, there is no excuse for them being so terrible except that they’ve always been that way.

The important information should be brief and at the top. This is design 101. The same ideas that have driven newspaper articles and websites for as long as the two have been a thing.

You put the important stuff in big letters at the top, and the rest, if you need it, is beneath the fold.

Edit: just to drive the point home: I’m sure it’s not the packages I’ve downloaded that are causing the error, I am positive it is my code, so show me where my code had a mistake first. Then you can show me the horrible “wall of text” that is the stack trace so I can understand it better later, but 99% of the time, just seeing the line that caused the error is enough to know what the problem is.

Hey hey. JavaScript is easy. It’s when you get into virtual doms that debugging becomes a nightmare.

Can you give us an eli5 on sourcemaps?

It is 2023 my brother in christ! We deserve better error outputs than a stack trace.

1. Tell me what line in my file caused the error,
2. Tell me the values of the variables involved,
3. Then you can have the stack trace.

Why are we pretending like these error messages are acceptable in 2023?!

Yeah, but that’s some bullshit. I want to know what line in my file is causing the error.

And they know! They know what line in your file caused the error! They know the value of all the variables when the error hit. But do they show that? Fuck no.

Also the part where someone else wrote the code 20 years ago, and they haven’t worked for the co for 19 years. And now you have to find a bug that makes no sense, with no idea how he even compiled the code. You work on it for 3 months and every day someone’s riding your ass about it till they finally say well, let’s put it in the backburner.

Speaking of slasher films, does anybody know of any movies that have terrible everything except a really good plot?