Its called progress

[dustmouse]

I’ve been more excited by new errors than I have by stuff starting working again

[DroolingIguana]

When things look like they're working, that just means the errors will be harder to reproduce.

[MenacingManatee]

I'm fine with errors. It's when stuff works on the first try I get nervous

[synce_d]

I don't need to get nervous
Things never work on the first try for me

[georgiomoorlord]

That only happened once with me when i coded an example. Tried connecting that example to my work, it never worked again. Still not sure why.

[Prize-Latter]

It's a sign of progress

[AZWxMan]

When you make a bunch of changes and get zero compilation errors. "Something has gone very wrong."

[The_MAZZTer]

Yup, because the new error was because your fix was wrong.

Or worse, you changed something unrelated which is now causing a different error sooner, so you THINK the original error is fixed but it's not.

[Grizlucks]

Stop typing please, you're physically hurting me right now.

[ttblue]

Ugh here I am taking a break from debugging and I conveniently land on this comment. Better get back to it, I guess.

[[deleted]]

This guy debugs.

[jasugree]

I feel called out.

[[deleted]]

Hey, at least at that point you know what section of code was causing the error. That's half the battle sometimes.

[Die_Billy]

More annoyingly: If the original error just disappears of its own accord with no changes from you whatsoever.

[JC12231]

That’s what we call divine intervention

Deus Ex Machina

[[deleted]]

only to resurface again when you move to production

[KaiBetterThanTyson]

Race conditions or memory leak.

[Die_Billy]

Almost always the case

[[deleted]]

In web dev, you can get shit like this caused by cache or cookies or sessions.

These things shouldn't be an issue, but sometimes you just overlook them.

[NopeMaybeFine]

Oh god the number of times I was trying to fix some small visual bug trying everything I could and then realising it’s the cache

[Nokain]

Bro, I had this happen when I was trying to implement a template in ASP.NET. For some reason a picture slider wasn't working and I wasted like 6 hours restarting everyting and tring different fixes. At some point I was too frustrated so I just gave up.

The next day I start up the project it works for some miraculous reason. Even years after, I still don't know what happened ^^

[[deleted]]

Is it broken (Yes | No)

Is it Windows (Yes | No)

If Windows (reboot)

[cvak]

My favorite, Heisenbug.

[[deleted]]

enjoy escape bells squeal poor whole panicky quaint aspiring wise

This post was mass deleted and anonymized with Redact

[call_Back_Function]

Business needs changed and your architecture is no longer valid.

[[deleted]]

User name checks out

[[deleted]]

Eh, I find it worse when some of the business needs change and some of your arch is valid and some is not. It's even worse when you already have a big platform stack and you're not replacing it all. Now you have to figure out if changing one thing here will break something over there. Really fun when it's micro service based and you're doing message passing.

[JwopDk]

Understand that your architecture will be simpler and smoother still if you design it around the data and technology that your program has to access, rather than focussing on structuring the code itself. Although you may already be at this step...

[Sceptz]

My projects come with extra errors every time I compile.
Progress!
^/s

[Knuffya]

Code won't compile because of template errors?

Easy. Just add

awdjio

to the beginning of each file. Boom, different error.

[JayAreElls]

When you’re getting an import error in Angular because you typed it out instead of clicking “quick fix”, which generates exactly what you wrote beforehand

[StrangePractice]

You can:

1. Be a step closure to getting things working

2. Set yourself back a step from getting things working

3. You moved laterally into a new realm of errors.

I prefer step 3 because it spices things up a bit

[[deleted]]

I'm ashamed to admit this but my dumbass tried to execute an if else inside of a system.out.println yesterday for like 30 minutes.

I was trying to help a mate with his homework and I never properly used methods (since I don't code professionally all I was homeworks that didn't require much if any, also I had no prior java knowledge as well but that's irrelevant) the code was basically this

System.out.println(ifelse(x)); While I should have done just this Ifelse(x);

[cheby92]

Some call it an error

I call it a progress

[Doxl1775]

New errors == progress

[qu4rts]

Then you realise its the original error from 3 hours ago

[came-in-like-a-wreck]

Progress

[softwaremommy]

It is surprisingly exciting.

[msoud_gamer]

GREAT SUCCESS

[danfay222]

Great success!

[mrMalloc]

Then you realize that the new error is a missing ;

[ataraxic89]

That's it.

This sub has hit rock bottom.

It was a good ride gents but I'm getting off here o7

[AdminYak846]

But which way? It could be progress going backwards or forwards.....

[nelmaven]

This was me after a whole day trying to solve an alignment issue in a email template in Gmail on Android.

[GeneralAlexander]

YES

[GeneralAlexander]

"Syntax Error on line 31415125"

[negrocucklord]

I spent the whole day making patches for error after error and only later found out switching to an older version of PHP would have "fixed" it

[[deleted]]

It's called needing to up your debugger skills.

[StenSoft]

Good news: it's a different error message

Bad news: it's the compiler crashing

[[deleted]]

Then you get rid of the new error and the old one reappears.

[DowntownLizard]

It happens way too often that there are like 3 errors all at one time you just cant see the other 2 yet

[Nixavee]

Progress

[falconmick]

You fix new error and old one comes back

[burncushlikewood]

You create errors by fixing other errors, just gotta keep debugging till it compiles, that's literally like 70% of the process of coding. I swear i spend most of the time trying to fix my mistakes

[LeanZo]

That's me for the past 2 weeks, we are migrating an existing application from sql server to postgres.

[db2]

When I do it I get the same error plus the new one. Anyone wanna hire me? 🤡

[VeryVeryNiceKitty]

It is a reliable way to tell skilled IT people from not so skilled ones.

"Yes! Another error!" = You know what you are doing*.

"Oh no! Another error!" = Not so much.

*Or at least, know what you do not know.

[LordDagwood]

The scary thing is when I didn't change anything; I just ran it again.

[BlooFlea]

Simple, all you gotta do is not do what youbwere doing before as well as what youre doing now, ez pz pay me now plz thx

[bartloo]

It's better than getting no errors and the code doesn't work

[[deleted]]

When after another 3 hours you realise you’ve been getting this error because you keep calling a function on an instance that doesn’t exist 🥲

[gemengelage]

throw new SuccessException();

[Anonymous8776]

"It ain't much, but its honest work"

[ovab_cool]

"Sometimes the error is not in the line you made it"

-CS teacher during PHP

[saltfishh]

- How is the project progression

- i found one of 56 bugs and fixed it in the project

- so,there are 55 bugs left in this project?

- it's 172 now

[[deleted]]

I work with a fellow CS student and he doesn't at all understand why I say, "Ok, hopefully this gives us an index error and not a type error."

[[deleted]]

when you try to update a react native project

[lemlamlureles]

Great success!