I'd butter not tell you my secret, cuz if my boss finds out I've been loafing around, I'd be toast!

Although as they say, no pain, no grain, so maybe he would at yeast excuse the bread puns.

How do you make a cuttlefish laugh?  Give it ten tickles.

Which dinosaur has the richest vocabulary?  The the-saurus, of course.

My best friend was charged with stealing my dictionary.  I have no words.

If it were up to me, I'd just migrate from bookworm to Devuan chimaera instead of trying to reinstall the vps. And possibly upgrade to daedalus afterwards.

Doctor: Before we begin this procedure, I have to warn you that the survival rate is only 50%.
Patient: Well, then let's do it twice!

Airport security found a suspicious-looking unattended suitcase.

After efforts to find the owner failed, they decided to force it open.  And lo and behold, it contained nothing but a single German sausage.

"Oh no," said the chief inspector. "This is the wurst case scenario!"

The student was dozing off in English class. The teacher noticed, and snapped:

"Name two pronouns!"

The student replied groggily, "Who, me?"

My daughter decided to name her iPad after the Titanic.  I have a syncing feeling about this...

"My sister plays the piano by ear!"

"That's nothing; my brother fiddles with his whiskers!"

Dependencies are inherently evil.  Did you know that versioned dependencies are an NP-complete problem?  As in, if you have a graph of projects that have versioned dependencies on each other, resolving these dependencies potentially require an exponential-time (or exponential-space) algorithm.  Dependency hell indeed!

In my own code projects, I prefer having no dependencies at all.  Of course, this isn't always possible; so the next best thing is shallow dependencies: those that only require 1 level of dependencies. Actually, before I even get to dependencies, my preference is single-file modules that I can just copy into my source directory and use as-is, without declaring any dependencies.  Not many things can be used this way, but when such exist, I prefer it.  Only if I have no choice, I'll go with a shallow dependency.  And of course, the fewer dependencies the better.  Recursive dependencies I try to avoid like the plague unless there's absolutely no way around it.  And I absolutely would not touch an automatic dependency system that will automatically download 500 packages in response to a single dependency on some package that's promiscuous in its recursive dependencies.  Those things are pure evil.

See also this link that describes a lot of the issues that come with dependencies, that people have been ignoring for far too long: https://research.swtch.com/deps

The couch potato finally found a job at the stadium that suited him. He became a common-tator.

Sorry was too lazy to do it. Will do that next time.  My bad!