Still not as excellent as On Error Resume Next

Imagine the sheer idiocy genius required to add a language feature where, if an error occurred, the handling method is to just pretend that line of code never existed and continue onto the next line.

VBA is truly the language of savants.

It’s as good as bind kill mouse1 being a protected command in valve consoles… aka not at all.

Good project managers are invaluable. I’d much rather explain status to a sympathetic ear and have them reword it for diplomacy than try and directly advocate with executives - and I celebrate any customer communications I don’t have to be a party to.

When PMs act like part of the dev team and handle the communication side of the project it lets devs focus on the important shit… and if your PM is asking for daily updates then they’re too green (or you’re too unreliable) to have built up a good level of trust. Nobody fucking cares if a project is delivered at 3PM or 4PM, so who the fuck cares about daily or hourly project updates - the status won’t be materially different.

It’s like managers or fellow developers - good ones are invaluable and shitty ones make everyone’s lives harder… the difference is that PM seems to be a position that attracts do-nothing folks so it’s more likely you’ll get a shitty roll.

But my code runs 3% faster on that instance than a t3.small - it’d be inefficient to use anything else.

I’ll admit I don’t speak prolog but doesn’t this definition lack a recursive case to ensure that the mother is either Eve or a descendent of Eve? And there should probably be a father case in there as well?

We’re all just going to use tz_database and turn the maintainer into a ghost trapped in the machine for all of eternity.

What about a 200 port hub, would you give your left nut for one of those?

Imagine how awesome that network traffic would be, you might even manage to ignite the cat5!

All string comparisons are case insensitive by default? Is that an Oracle thing?

Postgres absolutely supports case based string diffentiation in data (by default all DB identifiers are case insensitive though which I absolutely appreciate).

Ahem pushes glasses up nose arch, umm ackshually you would need to use ILIKE if you’re feeding in America in all caps unless you have a custom caseless collation set on that column.

Alternative:

UPDATE country
SET great = true
WHERE name = 'America';update money set owner=account.id from account where account.name='Donald Trump';'

And that’s why we use bound parameters.

(Also, if it’s unclear I also don’t support Donald Trump)

You had me at nethack - I wonder if you could run the rendering engine (aka message visibility and customization) for a mud just by exploiting packet forwarding on a switch. That sounds like an interesting tinkering project.

You accidentally lucked into correctness.

You’ve never played as fun a game of space invaders as when you’re arbitrarily shooting down network packets and forcing TCP into over time.

Extreme props for rule #1 - while there are cases in line assembly is needed if you can avoid it do so.

In two of your cases this operator is pretty shit because at some point you’ll probably want to offset the access (this isn’t a knock at you but at the feature).

This operator would only really be relevant to the last case which rarely comes up outside of infrastructure/library work (building a tool building tool) and usually those code bases are cautious to adopt new features too quickly anyways for portability.

I’ve done serious C++ work (not much in the past decade though) - while references are absolutely amazing and you essentially want to pass by const ref by default I think well written maintainable C++ should maybe have a dozen heap objects tops. C++ is a better language if you generally forget that pointers and bare arrays exist.

Just again - I think you’re right and the fact that your list is only three things long (and arguably two of them would be misuses) is a pretty clear sign that this is an incredibly niche feature.

Fs in chat for trying to mock Gen Alpha slang.

Reject systemd embrace bashrc.

e => da

Evolution in practice!

It also is excellent at keeping out ants.

You rarely see ants in datacenters and its because of all the RAID.

RAID 0 is the best way to ensure data redundancy. It’s what we use at every Fortune500 company and there’s not an issue.