Imagine being the ruler of that city and letting him get "cured" instead of having him infodump / give daily reports about this.

"Captain's Log, supplemental."

I've been a dev for 20+ years and yeah, learning a new repo is hard. Here's some stuff I've learned:

Before digging into the code:

• get the thing running and get familiar with exercising it: test happy path, edge cases, and corner cases. We're not even looking at code yet; we're just getting a feel for how it behaves.
• next up, see if there's existing documentation. That's not an end-all solution, but it's good to see what the people that wrote the thing say about it.

Digging into the code:

• grep is your very best friend. Pick a behavior or feature you want to try and search for it in the codebase. User-facing strings and log statements are a good place to start. If you're very lucky, you can trace it down to a line of code and search up and down from there. If you're unlucky, they'll take you to a localization package and you'll have to search based on that ID.
• git blame is also your very best friend. Once you've got an idea where you're working, use the blame feature on github to tie commits to PRs. This will give you a good idea of what contributing to the PR looks like, and what changes you'll have to make for an acceptable PR.
• unit tests are also a good method of stealth documentation. You can see what different areas of the code look like in isolation, what they require, and how they behave.
• keep your own documentation file with your findings. The act of writing things down reinforces those things in your mind. They'll be easier to recall and work with.
• if there's an official channel for questions / support, make use of it. Try to strike a balance here: you don't want to blow them up every five minutes, but you also don't want to churn on a thing for days if there's an easy answer. This is a good skill to develop in general: knowing when to ask for help, knowing when an answer will actually be helpful, and knowing when to dig for a few minutes first.

There's no silver bullet. Just keep acquiring information until you're comfortable.

That would be pretty easy.

return "Why are you even trying to do it this way?\n$link_to_language_spec\nThis should be closed.;

A long time ago, my old therapist asked me what I thought would happen after I died. I told him I didn't know and was ok waiting to find out when it happened. He pressed me on it and I said "ok, either the big switch flips and that's it, or something soul-like survives, or the human mind dilates my final moments into an eternity because it cannot comprehend non-existence." And then he changed the subject.

This reminds me of that.

Sometimes my mom calls a fanny pack a strap-on. This is like that.

This reminds me of the time my group played a kobold campaign. We found a halfling scout and dealt with him. Then we made an improvised catapult and launched his corpse into the middle of his camp. And then we snuck in and wiped the rest of the halfling party while they were trying to figure out what was happening.

One of the guys in our party put skills in cooking and rolled a nat 20 making halfling jerky. A few sessions later a wizard or whatever granted us a wish, and we wished for our supply of nat 20 halfling jerky to never run out.

So now we're rolling around the countryside raising hell and handing out halfling jerky to everyone because it is now the most powerful diplomatic tool in our arsenal. We never told anyone what it was made out of and pretty much any NPC who didn't want to kill us on sight got a piece.

I don't remember what happened to the party. I think our GM gave up in disgust after a while. Good times.

The final project in my instrumentation class was to tune a PID controller for a hot/cold mixing valve. I (CS/ENG) was paired up with an engineering student and a lot of it was throwing parameters in, seeing if weird shit happened, and then turning down or up based on the result. I had a programming final and something else I was supposed to be studying for, so I just started doing a binary search with the knobs. We got the thing tuned relatively fast and my partner acted like I was a wizard.

Authority is a privilege and a responsibility, not a virtue or a right. If you are in a place of authority your life should be harder, not full of fawning sycophants that give you an ego boost.

Loud guy.

Pretty sure One-Who-Goes-Bankrupt-Running-A-Casino is a Ferengi insult.

The people that want to restrict reproduction are acting like eugenicists? I'm shocked. This is my shocked face.

Kernighan's Law states "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

Since no thought went into writing the code, I can only believe that no thought is required to fix. Therefore my involvement is unnecessary. Have fun!

All these years I've been reading a book without an orange.

Molyneux's great sin is the inability to shut the fuck up while he's ahead. lt's hard to explain how much weight this guy carried in the 90s/very early 00s but he was the guy that did Populus, Dungeon Keeper, and Syndicate. And then he just kept over-promising and fucking up for a whole decade.

If he'd kept it reasonable he might still carry some of that weight but he cannot stop promising the moon and then delivering mediocre shit. It would be like Miyamoto releasing flappy bird with NFTs instead of the next Zelda game. God he's so frustrating.

Yep, and the newer ones are getting worse.

maybe this will work

...

...

...

linting and unit tests

This is real. In order to formally evict, it needs to go to court. Because eviction is a civil matter, most places don't give access to a public defender. This means that the tenant must retain legal counsel or fill the paperwork out themselves. I've heard of at least one local case where the defendant was publicly berated by the judge for not applying the correct spacing to the document. Most people don't have the time to be lawyers as well as working jobs and raising kids. It's ludicrous but it's the default status.

It sounds like she theoretically got fourteen days to respond, but wasn't notified. In my state, it's five. It should be a minimum of thirty, but half our state legislature is realtors and landowners. Evictions follow a person around, too, and make it harder for them to find new housing.

If you hate this news story, check out tenant right to counsel, which is a new movement to guarantee legal defense for evictees. Cities are slowly adopting it, and it needs to happen everywhere.

Huh. These things are a central plot point in Hercule Poirot's Christmas. I always thought Agatha Christie just made them up.

As someone whose employer is strongly pushing them to use AI assistants in coding: no. At best, it's like being tied to a shitty intern that copies code off stack overflow and then blows me up on slack when it magically doesn't work. I still don't understand why everyone is so excited about them. The only tasks they can handle competently are tasks I can easily do on my own (and with a lot less re-typing.)

Sure, they'll grow over the years, but Altman et al are complaining that they're running out of training data. And even with an unlimited body of training data for future models, we'll still end up with something about as intelligent as a kid that's been locked in a windowless room with books their whole life and can either parrot opinions they've read or make shit up and hope you believe it. I'll think we'll get a series of incompetent products with increasing ability to make wrong shit up on the fly until C-suite moves on to the next shiny bullshit.

That's not to say we're not capable of creating a generally-intelligent system on par with or exceeding human intelligence, but I really don't think LLMs will allow for that.

tl;dr: a lot of woo in the tech community that the linux community isn't as on board with