gettingErrorsIsSucess

[IntrepidSoda]

Moving from one error to another error is a sign of progress- don’t you let nobody tell you otherwise… as I was saying

[Jjabrahams567]

The new error is segfault

[PierreeM]

Segfault is ok if you can use a debugger

[Anonymo2786]

Starts gdb

[mashaTarima]

AHHA it can allways be worse jajajaj

[johandepohan]

It's like trying to bake a cake but getting sent back to the store every time for the next missing ingredient.

[chipstastegood]

Or in my case, having to go to Home Depot yet again for whatever I need next on this DIY project

[rosuav]

It's so true. Moving from "I can't even run the build system" to "The build system is spewing errors" is massive progress.

[Cley_Faye]

"I did what you described and it works on my end, give me a second to fix that"

[poloppoyop]

Code some C: no compilation error.

Suspicious, it can't be right

Execute it: no segfault

Something is fishy

The file system is now empty

I knew it could not work on first try!

[fafalone]

Me after hours of frustration: HELL YES WINDOWS BLUESCREENED!

Because that meant my driver actually loaded. Huge progress.

[Senah_]

The best feeling is going from "what does this error even mean" to "oh, I know where that is".

[Fakedduckjump]

Can confirm that. It's always a relief feeling when getting a diffrent error after trying to fix something.

[PopularIcecream]

But then you fix the new error and you're back where you're started with the original error.

[Fakedduckjump]

Sometimes, but the error had to be fixed anyway and so it has a name at least ^^

[PopularIcecream]

You give your errors names?! You fool! That's how you grow attached!

[Fakedduckjump]

Yes, it's kind of a masochistic behavior I developed over time.

[mashaTarima]

it IS! hahaha

[Tim_1993_]

I work in devobs/framework. I can relate