Yeah, or their parents argued a lot and they don’t want to end up in a relationship where this is the case. This can also mean they’re quick to exit a relationship as soon as the first conflicts need to be resolved, because it feels like a sour relationship to them.

That “l” is an L. 🙃

https://en.wikipedia.org/wiki/"Weird_Al"_Yankovic

𝆐𝆑

Oh yeah, I do think setTimeout executes in parallel, so only the largest element determines the execution time. It was difficult enough to make that sentence make sense, so I didn’t want to cram that detail in as well. 🙃

I mean, it does scale with the size of the input. Just not with the count of inputs, but rather the size of each input element.

I agree in general, that a crash is much better than silently failing, but well, to give you some of the nuance I’ve already mostly figured out:

• In a script or CLI, you may never need to move beyond just crashing.
• In a GUI application or app, a crash may be good (so long as unsaved data can be recovered), but you likely need to collect additional information for what the program was doing when the crash happened.
• In a backend service, a crash can be problematic when it isn’t actually necessary, since it can be abused for Denial-of-Service attacks. Still infinitely better than failing silently, but yeah, you gotta invest into logging, monitoring and alerting, so you don’t need to crash to make it visible.
• In a library, you generally don’t want to trigger a crash, unless an irrecoverable error happens, because you don’t know where it’ll be used.

Currently implementing error handling for a library I’m building and the process is basically to just throw all of the information I can find into there. It makes the error handling code quite verbose, but there’s no easy way for me to know whether the underlying errors expose that information already, so this is actually easier to deal with. 🫠

However there are things when the Ai is helpful, especially for writing tests in a restrictive language such as Rust.

For generating the boilerplate surrounding it, sure.
But the contents of the tests are your specification. They’re the one part of the code, where you should be thinking what needs to happen and they should be readable.

A colleague at work generated unit tests and it’s the stupidest code I’ve seen in a long while, with all imports repeated in each test case, as well as tons of random assertions also repeated in each test case, like some shotgun-approach to regression testing.
It makes it impossible to know which parts of the asserted behaviour are actually intended and which parts just got caught in the crossfire.

Yes, catastrophic software bugs…

Somehow I like the look of both this:

And this:

The bottom one certainly has its own vibe. That with dark theme and monochrome icon set would look cool.

Is it maybe a burying instinct, like they have with their poop? The carpet might seem more like grass or lose ground, where it is possible to bury it. You don’t really want the puke rotting away on the stone ground of your lion’s den, do ya?

Damn, even when I don’t mention it, it’s apparently obvious that I’m gushing about Rust. 😅

I had the Rust CLI Book in mind: https://rust-cli.github.io/book/index.html
Especially, if you have experience in another language already, the first chapter shows you how to develop and ship a useful Rust application in a short amount of time. And then the second chapter contains all the detail information, which you might need, after you’ve run off and started building your own thing.

But yes, Rust By Example is also really great. It happens a lot that you search “xyz in Rust” and it’s one of the first results, and always worth clicking on.

I see the value in reading documentation front-to-back for picking up all the little tidbits of information (or at least knowing where they’re documented), but yeah, ultimately I need to be building something to really process the information.

Kind of my sweetspot is documentation that makes you build along, but doesn’t overstay its welcome. As in, don’t cram all the details along the way, but rather just dish out important information on rapidfire.
I will run off building my own thing in the middle of the tutorial, if that isn’t the case, whether I want to or not. As soon as it’s quicker to learn by dicking around with the code, I will do that and then I’ve spoiled future chapters, so likely won’t return.

Dried lentils don’t need to be pre-soaked, but I prefer to cook them separately and drain the water they boil in.

Pre-soaking lentils (and pouring the water away) makes them easier to digest, in particular it makes them bloat you less.

https://farmhouseguide.com/benefits-of-soaking-lentils/

An exception are dehulled lentils, like red lentils. They don’t need pre-soaking and are quicker to cook, too. I often throw red lentils into the cooking water with my noodles or rice, just to add some protein into the meal.

You generally have to fork to create a PR…

Last year, money was running out in our project and the guy who had trained me decided he’d take the L and move to another project, so we could continue in the project. And yeah, suddenly I was in the role of the lead developer.

Like, don’t get me wrong, I would’ve been the one to be moved to another project, if I wasn’t up for the task. It’s not like I was a complete dumbass.
But it did still feel more like “I guess, we doin’ lead development now” rather than something I had intentionally worked towards.

I mean, depends on the country. Labor laws here in Germany mean that it’s worth investing into workers and when you have invested, it costs you significantly more when they quit than if you just paid them reasonably.

If we leave realism aside for a moment, though, the difference is that:

• a carry slot limit restricts how many distinct kinds of items you can have, whereas
• a carry weight limit moreso forces you to leave behind duplicates of items or to e.g. make a choice between heavy armor vs. having auxiliary items.

It depends on the game what’s more fitting for the overall design, but yeah, ultimately you want to prevent the player from optimizing the fun out of the game.
Having very heavy armor or dozens of healing potions can be boring, since there’s no risk anymore. But having one of each different kind of item can also kill the fun, because having the perfect solution for every situation is just as boring.

Yeah, and you’d often get a separate junk inventory, along with a one-click button to sell everything from there. I guess, at least it was an attempt to solve the problem…