3 ms·
That’s why it’s important to find a team and coworkers that aren’t so uptight.
by pizlonator 3y ago
That’s why it’s important to find a team and coworkers that aren’t so uptight.
- slaymaker1907 3y agoWith a project that could live on for many years, I’d object to this code, but only because it doesn’t really explain _why_ it’s necessary despite wasting time/memory. The humorous name is great, though. It might be explained in the VCS history, but people aren’t likely to look it up there and I’ve noticed the history tends to get lost for a lot of old projects.
- eru 3y agoFortunately, git helps you stitch together histories (without changing hashes), if you later recover it: https://git-scm.com/book/en/v2/Git-Tools-Replace https://git-scm.com/book/en/v2/Git-Tools-Replace
- pizlonator 3y agoThe name isn’t just funny. It’s also accurate. And it’s quite evidently stood the test of time. In a VM, often the most important kind of documentation is about labeling what is the fast path and what is the slow path. This method name alerts the code reader that they’re looking at one of the slow paths.
- spopejoy 3y agoIsn't part of the goal with deliberately weird names like this is to alert callers that HERE BE DRAGONS so, like, don't call this unless you've read _and understood_ the source code?