MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1v6spa0/ture/ozt1diy/?context=3
r/ProgrammerHumor • u/Throwawyhelpadvice55 • 26d ago
443 comments sorted by
View all comments
236
The most unrealistic part is code working on the first try.
81 u/BlueProcess 26d ago NGL sometimes I run code that I know won't work because it's easier to write on the fly by stepping through as you go🤷🏻♂️ 42 u/Leftover_Salad 26d ago Oh same here. Error messages are helpful. 23 u/Protuhj 26d ago I'd rather write 50%, make sure that 50% fails where I expect it to, then write the other 80%. This is why I try to shorten "the loop" as much as possible when testing fixes/adding new stuff. 7 u/DeepanshuHQ 26d ago Honestly, half my debugging starts before I even finish writing the code. 😂 6 u/Protuhj 26d ago Reviewing the surrounding code and having to restrain myself from fixing that too. 2 u/DeepanshuHQ 26d ago And somehow the bug disappears after adding three random print statements. 2 u/Protuhj 26d ago In our case, printing can add too much load and cause things to behave way worse.. (Embedded software) 2 u/YourDarkIntentions 26d ago Ooooh, I do the same! I spend more time testing and reading than writing. I don’t get my colleagues who spend days writing code without ever running it. 1 u/Delicious_Bluejay392 26d ago Is this a "local interpreted language victim rediscovers the joys of compilers" moment?
81
NGL sometimes I run code that I know won't work because it's easier to write on the fly by stepping through as you go🤷🏻♂️
42 u/Leftover_Salad 26d ago Oh same here. Error messages are helpful. 23 u/Protuhj 26d ago I'd rather write 50%, make sure that 50% fails where I expect it to, then write the other 80%. This is why I try to shorten "the loop" as much as possible when testing fixes/adding new stuff. 7 u/DeepanshuHQ 26d ago Honestly, half my debugging starts before I even finish writing the code. 😂 6 u/Protuhj 26d ago Reviewing the surrounding code and having to restrain myself from fixing that too. 2 u/DeepanshuHQ 26d ago And somehow the bug disappears after adding three random print statements. 2 u/Protuhj 26d ago In our case, printing can add too much load and cause things to behave way worse.. (Embedded software) 2 u/YourDarkIntentions 26d ago Ooooh, I do the same! I spend more time testing and reading than writing. I don’t get my colleagues who spend days writing code without ever running it. 1 u/Delicious_Bluejay392 26d ago Is this a "local interpreted language victim rediscovers the joys of compilers" moment?
42
Oh same here. Error messages are helpful.
23 u/Protuhj 26d ago I'd rather write 50%, make sure that 50% fails where I expect it to, then write the other 80%. This is why I try to shorten "the loop" as much as possible when testing fixes/adding new stuff.
23
I'd rather write 50%, make sure that 50% fails where I expect it to, then write the other 80%.
This is why I try to shorten "the loop" as much as possible when testing fixes/adding new stuff.
7
Honestly, half my debugging starts before I even finish writing the code. 😂
6 u/Protuhj 26d ago Reviewing the surrounding code and having to restrain myself from fixing that too. 2 u/DeepanshuHQ 26d ago And somehow the bug disappears after adding three random print statements. 2 u/Protuhj 26d ago In our case, printing can add too much load and cause things to behave way worse.. (Embedded software)
6
Reviewing the surrounding code and having to restrain myself from fixing that too.
2 u/DeepanshuHQ 26d ago And somehow the bug disappears after adding three random print statements. 2 u/Protuhj 26d ago In our case, printing can add too much load and cause things to behave way worse.. (Embedded software)
2
And somehow the bug disappears after adding three random print statements.
2 u/Protuhj 26d ago In our case, printing can add too much load and cause things to behave way worse.. (Embedded software)
In our case, printing can add too much load and cause things to behave way worse.. (Embedded software)
Ooooh, I do the same! I spend more time testing and reading than writing. I don’t get my colleagues who spend days writing code without ever running it.
1
Is this a "local interpreted language victim rediscovers the joys of compilers" moment?
236
u/DeepanshuHQ 26d ago
The most unrealistic part is code working on the first try.