Once I was fixing something in my code. I fixed the issue and ran it to see if it worked. Problem persists. I tinker with it for 15m, recompiling and running, problem persists! I break the code on purpose, code still runs...
Turns out I was executing a wrong file
Edit: This really blew up, thank you guys. At least I know I am not alone.
Adding echos to a php file, reloading like crazy without seeing the output anywhere until I've realized I was browsing production instead of dev server
Working on a bug in a web site. Changed the code, saved, run debugger, refresh browser, nothing. Don't even see my new trace statements in the console. It's like that part of the code isn't being run. Over and over, try this, try that. It's like nothing I do changes anything.
Ask colleague for a second pair of of eyes.
"Your browser is pointed to the server, not localhost." he said.
Luk164 on November 20th, 2019 at 22:46 UTC »
Once I was fixing something in my code. I fixed the issue and ran it to see if it worked. Problem persists. I tinker with it for 15m, recompiling and running, problem persists! I break the code on purpose, code still runs...
Turns out I was executing a wrong file
Edit: This really blew up, thank you guys. At least I know I am not alone.
cateyesarg on November 20th, 2019 at 23:54 UTC »
Adding echos to a php file, reloading like crazy without seeing the output anywhere until I've realized I was browsing production instead of dev server
urbanek2525 on November 21st, 2019 at 01:19 UTC »
Working on a bug in a web site. Changed the code, saved, run debugger, refresh browser, nothing. Don't even see my new trace statements in the console. It's like that part of the code isn't being run. Over and over, try this, try that. It's like nothing I do changes anything.
Ask colleague for a second pair of of eyes.
"Your browser is pointed to the server, not localhost." he said.
I'm never getting those hours back.