Dungeons of Daggorath. I had a Color Computer 2 growing up, while we lived in a trailer park. I was still a little afraid of the dark, and the hallways and first person view with jump-scare monsters were a bit intense for me. I’d have to run from one end of the hallway to the other, to get to the bathroom and back.

The impressive event queue system in that game felt like magic to me, like I wondered what happened to the monsters when you turn the computer off.

I was a “smart kid” but I don’t think I was a smart kid.

(Something something original author, something something signed copy of the original source code on my github)

I feel like there should be a third box with Wall Street raider types, for scrapers that use Selenium browser automation.

I don’t think it’s entirely unblockable - adsense seems to know to only serve unmonetized PSA ads - but I think it’s very difficult to discriminate between “this is a real browser controlled by an end user” and “this is a real browser being controlled by automated test software”.

The available food is mostly things they can pop into the fryer: Think fish and chips, except you can also choose “planks” of chicken breast, or breaded shrimp, or little balls of seasoned dough called “hush puppies”.

My wife hates them, and they’re an occasional guilty pleasure for me.

This.

My units and integration tests are for the things I thought of, and more importantly, don’t want to accidentally break in the future. I will be monumentally stupid a year from now and try to destroy something because I forgot it existed.

Testers get in there and play, be creative, be evil, and they discuss what they find. Is this a problem? Do we want to get out in front of it before the customer finds it? They aren’t the red team, they aren’t the enemy. We sharpen each other. And we need each other.

Love this, 100% accurate. QA people are amazing, protect us from ourselves in so many ways we didn’t even think of.

Are you sure? TOTP secrets can be exported. I think passkey implementations explicitly prevent that. Unless I’m missing an option to export passkey creds, e.g. print them out.

That same disaster recovery feature (which I need) also helps avoid a future where every forum and avenue of dissent requires dis-repudiation via passkeys. It’s a weird nuance, ascribing a social effect to a simple ability to back up your keys without backing up your whole phone.

How does that protect against “only you could have logged in because this passkey is only on your phone”?

Passkeys make plausible deniability more difficult. “This user name isn’t necessarily associated with my real world identity” permits some important good things.

They would enforce the rules of their payment card network. Once they’re aware of a violation they take action. If they become aware of a series of violations they take further action to ensure the merchant complies in the future.

I’m surprised I’m the first comment saying this, but all I see is a user who needs help expressing their needs but who is not getting that help. Sure they don’t have our experience with decomposing problems and anticipating technical issues, but that’s normal and expected.

Dear God do I hate how true that is. Not sure if intentional or not, but either way I’m with you. And I think they’re working to a plan.

I had a call center job while finishing college, but I’m currently a professional software developer. The difference in coverage is crazy. Dental crowns went from 25% to 75% coverage. My annual maximum out of pocket for healthcare is so low I keep hitting it by accident and wondering why things are suddenly free.

Why? I think it’s a deliberate plan to make life pretty good for like 51% of us, so we won’t vote against the way they absolutely wreck the other 49% of us.

I hope it stops working soon.

Needs a method to ensure all incoming transactions can be reversed if the expected payment to charity is never made or is refused. Or am I missing a component of the design that guarantees this?

Remove these blank lines.

I’m not seeing unit tests for this.

Unnecessary comment.

BLAM

Ow! Also, this could’ve been a smaller calibur.

Looking closer at the image, I’m going with “in this house we use single sideband.” (But, as a Plex user, I love yours too.)

Hey no botting!

NEW

Giving up land to an invader was ever acceptable? LOL

Agreed. Use your experience to shape the direction your teammates are moving in. Be an architect, and let them handle your light work.

Ugh, this makes me want to “slash slash slash.”

And those jobs are critical to the process of making new developers.

An important part of my education - the part that grad school can’t teach you, you have to learn it on the job - was being new and terrible, grinding on a simple problem and feeling like a waste of money. Any of the experienced guys sitting behind me could have done this thing in a few hours but I’ve been working on it for a week. “What’s the point? Any minute now they’re going to tap me on the shoulder and tell me I’m done, it’s time to go find another job.”

But that never happened.

Those early problems weren’t fun. At home I would have never chosen to work on them. I’d leave them for someone else. “But now that I’m collecting a paycheck for it, this isn’t up to me. I have to work on it. I can’t give up. I can ask for help, but I need to show my peers that I belong. I can solve difficult problems. I can persevere.”

As a mediocre professional developer, I had to struggle to learn that. I wasn’t getting far on my own, without mentorship and motivation. Homework, pursuing degrees, wasn’t getting me there. (And even now, I seem to have about two weeks of attention span, for projects at home.)

As a professional C# developer since 2012, I’d say a programmer needs four kinds of knowledge. As an organizational user of Github Copilot for a couple months, I’d say AI tools can help with one, maybe two of those.

Understanding language and syntax, so you can communicate the ideas in your head to the machine accurately: AI is fairly good at this, will certainly get a lot better.

Understanding algorithms and data structures, well enough to compare and contrast, and choose the most appropriate ones for each circumstance: AI can randomly select something, unless it’s a frequently solved problem. I don’t expect this to get better except for the most repetitive of coding tasks.

Understanding your execution environment and adapting your solutions to use it well: I don’t see the current generation of AI tools ever approaching this. I don’t think they have context for how a piece of code is used, when trying to learn from it. One size fits all is not a great approach.

Understanding your customer’s needs and specific problems, and creating products, not code. Problem domains and solutions are a business’s entire reason for existence. This is all kept confidential (and outside the reach of an AI training data set) for competitive reasons. As a human employee, you get to peek behind the curtain and learn these things yourself.