Fair enough, they could have meant something other than what they wrote. I still disagree though - it seems more likely they exaggerated intentionally for dramatic/comedic effect. The joke works better with the straightforward, grammatical interpretation.
- 0 Posts
- 4 Comments
Read the post again, it’s unambiguously the same single shirt for all the days of a week
Tap for spoiler
we’re apparently all just painting hypotheticals/anecdotes so here’s mine
You probably didn’t need an immediate answer, but you wanted one. You also pressured me into making a quick decision based on 2 paragraphs of new information you just dumped on me, expecting me to not only remember all of it, but immediately understand and integrate it into my decision making process.
I’ll probably remember half of your info dump at best and the likelihood of you getting the answer you were hoping for just went down hard because I feel slighted by your ambush and because I don’t feel informed enough to give you a “yes”.
If I did say “yes” we might be in bigger trouble though, since I likely misunderstood or forgot something.Put it in writing and make both our lives easier.
You can still call if I didn’t reply after 10 minutes.
You can even include your deadline in the message if you have one.
In a decent IDE you can CTRL+click (or similar) on a function name to go to its definition. This is absolutely faster than scrolling, especially if you’ve got more than a couple dozen lines in the current file.
When splitting functionality into smaller functions you would ideally not have to keep implementation details of other functions in short term memory.
You only need to understand/remember the contents of the current function. Does it do what the name suggests? Cool, you’re done checking it.
Of course, the “2 hard problems in computer science” meme exists for a reason - it’s not always straight forward to come up with good names. But in my experience, even when coming up with a fitting name is difficult, reducing nesting usually helps a lot with comprehension, mainly because it reduces scope and thereby the amount of information you need to hold in your head.
The larger a function gets, the harder it is to check that it does what it’s supposed to.
There is of course a balance to strike - trying to force every single function to be at most 3 lines is likely to make the code more difficult to understand and is, in my eyes, almost pathological. But a function that covers more than a screen is the other extreme that should be avoided when practical.