299 karma · joined April 1, 2018
More formally, the number of queries should be constant and not linearly scaling with the number of rows you're processing.
This is what happened with REST too, and it frustrates me more than it probably should.
The original pattern is such a good idea and not even remotely abstract. It's a well defined architectural pattern for a well defined problem yet people still managed to bastardize it to the point that the term REST barely means anything today
This sentence bothered me way more that it should've, for some reason.
Saving Voyager 1! - Bruce Waggoner at !!Con 2024 - https://www.youtube.com/watch?v=dF_9YcehCZo
Edit: Also, please do share when it's playable :)
What are some examples of a library that can limit or prevent side effects of a piece of python code? I could use one right now.
In my opinion, almost every developer I've worked with who advocated for generous amounts of comments has overestimated their (and or others') ability to write good quality comments.
Obvious ones like `a = b; // set a to b` while useless are also mostly harmless, but I've been lead astray by outright factually wrong comments, many more times than I can count. I certainly don't feel confident in my own ability to not write factually incorrect comments. So yeah, I'd rather the code do the talking.
That would be one hell of a museum
It's understandable for people to not be calm in this situation and struggle to explain things clearly, but it sounds like that wasn't the case here. So if you are calm, do the other person a favor and give a 10-15 second explanation of what happened instead of leaving them guessing.