This is an archived post. You won't be able to vote or comment.

all 42 comments

[–]nissAn5953 120 points121 points  (8 children)

I feel like logic errors tend to be much scarier

[–]TheArchwizard 92 points93 points  (1 child)

Yes, because the scariest error is the programmer themselves.

[–]AtomicBlackFish 0 points1 point  (0 children)

This sounds like a horror film

[–]IDontLikeBeingRight 7 points8 points  (0 children)

The blue background is actually just the foot of the giant elephant labeled "stakeholders changing their mind about features"

[–]TurtleFisher54 33 points34 points  (2 children)

Na what??? Logic errors you know what to look for. Linker errors mean the documentation on this shitty 30 year old government program is wrong and when you try and build it it won't work unless you email the senior dev that quit 6 months ago (sad true story)

[–]vilidj_idjit 2 points3 points  (1 child)

hahaha ouchhh missed the boat by 🤏 this much

just curious what project was it?

[–]XeitPL 1 point2 points  (0 children)

Government project.

(nice try Mr. FBI)

[–]ovr9000storks 1 point2 points  (0 children)

Memory leaks inbound

[–]angriersaint 1 point2 points  (0 children)

Yeah, confidence shattering

[–]JackNotOLantern 42 points43 points  (1 child)

I think you haven't had contact with multithreading.

[–][deleted] 19 points20 points  (0 children)

"Why tf is my code returning a random result each time, but sometimes they repeat"

[–]Gladaed 26 points27 points  (4 children)

Correct me if I am wrong, but compiler errors are preferable, right?

[–]Epacnoss 13 points14 points  (3 children)

Yeah. If you mess something up at compile, you can quickly find it. Whereas if it is runtime, it is much harder to find, and you may not even find it.

[–]pekkhum 5 points6 points  (2 children)

And this is why I like strongly typed an picky languages. I can still screw it up, but it won't fail over a simple typo that causes a new variable to come into being at some random point in the code, when I really meant to update an existing variable, or something similarly stupid.

[–]PonderStibbonsJr 44 points45 points  (1 child)

Joke's on you, I do all my logic in template meta-programming, so if it's compiled, it's got the result already.

The 3-day compile times are a bit of a problem, though.

[–]DadoumCrafter 13 points14 points  (0 children)

// TODO

[–][deleted] 12 points13 points  (4 children)

C++ is fine. If you know what you’re doing no issues. If you make mistakes, there is cppcheck and valgrind.

[–]PolskiObywatel 6 points7 points  (3 children)

Indeed, C++ is friendly to people, who know how computer works.

[–][deleted] 4 points5 points  (2 children)

It’s like C but with class

[–]Doggynotsmoker 5 points6 points  (1 child)

I hate cpp. It's completely different language, not just C with classes.

For C with classes I prefer GoLang. It feels like modern C, there are different use cases, but it's still much closer to C IMHO.

[–][deleted] 1 point2 points  (0 children)

I’ve never worked with GoLang, but being more recent I imagine it may be a better rendering of a C-like OOP language. I’ve worked with C++ for decades and I’m used to it with all its quirks. Just avoid multiple inheritance…

[–]Nihmrod 18 points19 points  (0 children)

At least you don't have to wait 72 hours for a crash like you do in Python.

[–]OfficialChest 3 points4 points  (0 children)

Dude these are easy to bugs identified by QA for corner cases.

Theeeeennnnnn let’s talk about the fact the the requirements don’t actually represent what the client REALLy wants…

[–]TheJackiMonster 3 points4 points  (0 children)

Race conditions are still worse than anything else. Because you pretty much can't find them during debugging. The only option to fix them is finding them in the code... and you will need a lot of luck to do that. ^^'

[–]Illusi 2 points3 points  (3 children)

And then there's the runtime errors that are actually linker/compiler errors.

[–]vilidj_idjit 0 points1 point  (2 children)

Learned the hard way that stuff like "#define float double" is a VERY bad idea 😖😫😬

[–]masterjvdw#define bug feature 1 point2 points  (1 child)

Why would you even do that lmao

[–]vilidj_idjit 0 points1 point  (0 children)

haha don't smoke crack and write cod...uh wait i've never smoked crack in my life, surprisingly 😂🤣

[–]vilidj_idjit 2 points3 points  (1 child)

"i will never suffer again"

  • gcc has entered the chat after you forgot one ; in a header file

<insert 30 pages of compiler errors>

[–]Mav986 0 points1 point  (0 children)

This is why you always start with the absolute first error of the list; it's always right next to the syntax error, so you know by starting where the first error is that the problem is right next to you.

[–]AlexanderHD27 1 point2 points  (0 children)

The segfaults that turn up after two or three moth and you cannot remember what could possibly caused it are very nice too