When you found the problem in the code

Oct 22, 2022 · 3:33 AM UTC

181
981
378
7,094
RelevantRecentLikes
When I started learning programming with C, I mistyped "stdio.h" as "studio.h" 🤣 🤣
2
7
😄
0nce remember doing a similar thing... stopped Coding altogether.. If you found it in the above sentence you are an ace coder
2
1
0k, aIright 👌
1
😂😂😂😂 – at Bengaluru South, India
1
2
🤭
😂😂
1
1
😄
i got a terrible flashback
1
1
🤭
Les gens qui refusent d'utiliser un IDE vous avez des problèmes tellement lunaires ça me fume
13
6
1
360
If it took you 4h to find that, programming is not for you. At least you found out in 4h. Ton of people go all the way through Law School and the bar only to find they don't want to practice Law.
4
20
@Bely_araujo1
1
2
we have been all through this. 😂
2
@radgratitude
1
Whew. I thought I was the only one. lol
1
lol - why didn't they look at the compiler output, it would have said there was an error on that line. 😉
Realize it's just a joke, but it would have failed the first attempt compiling. Likely four hours of typing in somebody else's code, and failing the first attempt to build.
26
Compiler didn’t catch that?! 🤔
1
19
Good lord all mighty how much code do you throw into one function
4
10
impossible. the compiler/IDE would told you right away you mistyped at line 2 🧐😏😉
1
3
😂😂😂 As long as you found the problem, time was not actually wasted. I can bet that, that's the first thing you'll look at the next time your code has a bug.
2
3
It be like this. Worse when it's a closing curly brace.
4
The rite of passage that even the oldest coder has never seen the end of ☠️
3
@michyikegbunam 😂😂
2
@lesliegonzs espero haberte etiquetado bien jeje Te amo
2
Been there! 😅😭
2
Why didn’t the ide flag it smh.
1
@MaxouBras
2
@realJohnAdex
1
2
@zkamaroski
1
The glass is half full. Congrats
1
Lol. Hang in there.
1
Made us smile 😄
1
Get a better IDE! 😆
1
@allanzokah azim amigo?
1
1
Load more replies