I’ve taken to writing .http files which are runnable on a number of IDEs and plugins. I don’t need to know what anybody else is using to run them, they live with the code and I’m happy.

That said, I’ve seen people on QA do really cool end-to-end tests at load via very approachable scripting on Postman.

There’s lots of room for “to each their own” here.

I learned to let you all squabble amongst yourselves and get the answer. Since every question is a duplicate, it stands to reason the question I have has already been answered.

Let’s all just wait for the new versions of languages, frameworks and operating systems. LLMs won’t have been trained on those and won’t have answers, people not asking each other online will generate no answers to train on.

Let’s read and train on docs, right? Yeah, right.

I love how the documentation is in the actual .h file and the read me is a mere formality.

I’m disappointed I didn’t get this as a floppy in the mail.

My thought as well, but those stones were shaped to match each other, reducing the amount of grout needed. It just goes to show the old ways still work, but you have to commit.

I’ve said this before only to hear “we don’t have time to set that up and agree on a common style” and “that’s team B’s responsibility since we’re contributing to their code base.” Guess what kind of issue we kept wasting time on?

There are a couple of takeaways here. I think the main one is acknowledging that many technical problems are deeply human problems and the existence of a technical solution doesn’t mean we shouldn’t apply the human solution as well.

[clicks light switch off and on repeatedly]

Welp, I guess we’re closed for the week.

let a = String::from(“Hello, world!”).into()

I’ll see myself out.

Common criticisms here would be that these endeavors stifle creativity and show the adoption of modern solutions. That said, I find conducting “code archeology” to figure out the idiomatic way of doing something in an old project very rewarding. Because computer programs exist in people’s mind’s, doing that with the support of original developers or subject matter experts is some of the most effective knowledge transfer I’ve ever witnessed.

Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.

Shared with my favorite blind iOS dev. Should be a good laugh!

Just learning. I threw together a little CRUD API in Rocket the other day.

Now I’m playing around with Diesel. I don’t love the intermediate New types, coming from EF Core. Is that because Rust ~~~~doesn’t really have constructors?