“Oh, they print in that order? That’s weird.”
“Oh, they print in that order? That’s weird.”
I did both of these at once last week.
Added a breakpoint. Debugger didn’t break.
Added an echo "here";
. Debugger didn’t print.
Added a throw new Exception('fuck');
. Debugger didn’t throw.
Stepped through. Debugger wouldn’t let me step in.
It took me almost an hour to realize it wasn’t the debugger’s fault and that a variable I thought was guaranteed to be truthy at that point was actually falsey due to upstream changes in a spreadsheet parser. I felt kind of stupid for not trusting the debugger at that point.
For context: these are the original lines
Science inherently involves the reproduction of work that’s already been done. That’s how the process ensures reproducibility. Talking about the efficiency of science makes very little sense because the savings bought by science are privatized, viewed like externalities.
Rhizomes stay winning
Put Netanyahu, Assad, Erdogan, Khamenei and their cabinets and top people from Hezbollah in Hague then we can talk.
So what you’re saying is Assad must go?
Now if he could start making cuts to the military…
Yeah. I can understand the use case when it’s something relating to keeping simple state in sync by replacing it with derived state. But this particular case was flushing a cache after each get, which made each get of the property non-deterministic based on the class’s state.
I helped a friend debug a script last week that was working inconsistently in really weird ways. I looked at the script and it was all event hooks littered with sleep calls. I told him he was basically fuzz testing his own script and then getting surprised when he found race conditions. Shit was wild. Also, sometimes getters in Python are a mistake.
Okay but I wanna know the findings of the study