First thought, assuming that birth year starts at 1900 is bad for a number of reasons; one of which, "process this list of authors and ..."

What about everyone born before 1900?

It’s a contrived example. And I have to assume the author intended it to be contrived given that he also put an upper bound at 1999 in an article written in 2026 in an industry that skews young.

But the pattern applies regardless of the validation logic.

Or what if they were born after 1999?

It's just a toy example not a production ready birthday validation library.

Assuming it is necessarily known which is the birth year of anyone assumed to have been in existence is already a big hypothesis if we go in that direction.

I use them all the time on Perl code.

https://metacpan.org/pod/Devel::NYTProf

Going to have to xerox this for my wall.

Someone ought to give them a kleenex for all of their boo-hooing.

Some young folks probably need to google what xeroxing means

But after the changing pampers, please.

It is the Cadillac of search engines, after all-- a real doozy.

I laughed so hard that I needed a bandaid.

Whoa buddy, let's do a quick zoom first.

Apple II, DOS and PRODOS calls do that too.

https://prodos8.com/docs/techref/calls-to-the-mli/

Nope, just explosive rapid deconstruction.

>stuck on an old OS release (i.e. RHEL?) and/or they don't build their own version and use the "system" Perl.

I build my containers and put Perl right in them. Makes the container a little chubbier but no outside dependencies.

And would be awesome if it gave out the current time.

I have a SuperNote that is a decent PDF viewer and notetaker.

https://goodereader.com/blog/reviews/supernote-a5x-digital-n...

> window snapping/tiling

Put me in the camp that hates window snap/tiling.

I have a certain workflow that needs this window there, and this one here ... don't snap to a location or go full screen.

Check out FancyZones in Microsoft PowerToys.

> We use IBM MQ at work and I wouldn't exactly call it simple.

2nd'd & 3rd'd ...

You hired a 50 man lumberjack crew to cut down a sapling.

I've been spending a some time to remove IBM MQ out and going to "simpler" queuing solutions. First of all, cost. Guess what, we're not getting anything out of licensing per year to justify the cost.

With improving the end points, we don't need all that complexity. With 5 9's uptime on the network and smarter end points, retrying messages isn't expensive.

As always, YMMV.