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.

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.

And here I was saying using git in the command line instead of a visual form might make me an elitist.

I’ve been living life on easy mode and not putting real care into my work.

The i686-pc-windows-gnu target has been demoted to Tier 2, as mentioned in an earlier post.

Fedora is discussing dropping support entirely, right? Interesting times we live in…

[clicks light switch off and on repeatedly]

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

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!

I also can’t get the printer to work.

I’m working through rust-exercises.com and taking notes on my thoughts. I may or may not want to use it for a short workshop at work - mostly for fun, since I work with a very different stack.

So far, I don’t know if I like the exercises, because the target audience doesn’t feel like it’s clearly defined: you both solve is_even with an if/else and overflow an i8 to -1. I don’t think I’ve met the person who is that inexperienced and that knowledgeable…

How are folks liking these exercises?

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?