Replies
@morozov_dev When I started learning programming with C, I mistyped "stdio.h" as "studio.h" 🤣 🤣
3
0
7
@morozov_dev 0nce remember doing a similar thing... stopped Coding altogether.. If you found it in the above sentence you are an ace coder
2
0
2
@morozov_dev Les gens qui refusent d'utiliser un IDE vous avez des problèmes tellement lunaires ça me fume
14
6
374
@morozov_dev 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.
0
0
27
@morozov_dev 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
0
20
@morozov_dev impossible. the compiler/IDE would told you right away you mistyped at line 2 🧐😏😉
0
1
3
@morozov_dev 😂😂😂 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
0
3
@morozov_dev The hardest code problems to find are not compilation errors (as the compiler tells you what and where you should change), but run time and logic errors.
0
0
2
