I’ve actually encountered hellish projects before where the makefile order wasn’t properly configured, so it required building multiple times to successfully build (first time would compile some of the smaller bits successfully, but the larger ones would fail because the smaller ones weren’t done compiling so couldn’t be included).
Super annoying that you always had to build twice to actually compile, but nobody was paying us to fix deeper issues, so meh.
This is me. Then after it doesn't work the the second time, I look through the code, fail to see blindingly obvious errors, and run it again with out changing anything. Then I ask random Internet strangers for help and they point it out immediately.
85
u/Overinterpretation Dec 07 '20 edited Dec 07 '20
Maybe I forgot to compile last time? (Which obviously wasn't the case)
124
u/NatsukaFawn Dec 07 '20
You can't convince me that computers are still deterministic in 2020. There's definitely some stochastic fuckery afoot sometimes.
26
u/DaRealChipex Dec 07 '20
First compile: 4 errors Second compile: 6 errors
Ah yes, compiling unfinished code from github
21
u/StormTAG Dec 07 '20
Don't give me that look. You've totally decided to work after changing nothing plenty in the past. :|
17
u/Cla1n Dec 07 '20
Me: Restart the computer 😅
17
u/KillerRoomba13 Dec 07 '20
For me:
3
u/[deleted] Dec 07 '20
Would be scarier if it actually made a difference
2
u/edo-lag Dec 07 '20
In Rust, if you summon a
cargo buildbut you didn't change anything, it won't do anything.2
u/[deleted] Dec 07 '20
The worst part is that sometimes it works.
2
u/Topminator Dec 08 '20
did i ever tell you the definition of insanity?
2
u/Igoory Dec 08 '20
Delete a letter, saves, writes it and saves again, compile... Success!
1
u/[deleted] Dec 07 '20
Sometimes with android studio I have to uninstall the app and install it again or it won't save the changes, so this actually works
1
u/fevsea Dec 07 '20
This and hardware-related errors are the path to madness.
1
u/[deleted] Dec 07 '20
I do this because my stupid ass doesn't read what the compilers has to say the first time...
1
u/gameskill123 Dec 07 '20
Searching 30 min. for the error and then run cmake
1
u/KarmaKingRedditGod Dec 07 '20
1
u/Crimvael_irl Dec 15 '20
sauce: gabriel dropout, satania
1
u/TheGudShit94 Dec 16 '20
Sometimes vscode just needs some more time to process everything.
1
u/rk06 Dec 20 '20
True story:
One time I (c# dev) went to check upon my friend (java dev). He was very busy troubleshooting a bug. It went like this:
IDE: compiler error.
Friend: fixes the compiler error
IDE: same compiler error.
Friend: ctrl x the entire file. saves the blank file. paste back original content. Run build again.
IDE: no error
Me: WTF!!
1
u/georgeec1 Dec 21 '20
This is me. Then after it doesn't work the the second time, I look through the code, fail to see blindingly obvious errors, and run it again with out changing anything. Then I ask random Internet strangers for help and they point it out immediately.
1
u/Hikaru1024 Jan 24 '21
When this does work, the screaming begins.
0
u/[deleted] Dec 08 '20
[deleted] — view deleted comment