Unpopular opinion: error handling in Rust is actually fantastic. Once you know the right patterns, which regrettably are NOT always obvious 😂

#rust #rustlang

I’m starting to really like Kotlin. It’s no silver bullet, but having types non-nullable by default unless deliberately marked as such has been the subtle game changer for my team.

Okay so honest question… I’ve heard several very terrible things about Matrix (mostly lack of moderation), and also a few happy users. What’s your opinion? Bit of framing:

- I would run my own server
- Use cases: DMs and bridging other platforms to simplify things
- Not super interested in the issues with public group chats unless you have something truly novel to add; decentralized problems have well known drawbacks

Boosts welcome.

#Matrix

Trying to build a touch typing habit that leads to coding faster - started trying the Vim keybindings for IntelliJ, and obtained a keyboard with clear caps because I’ve been looking down at my keys too much.

@raiderrobert finding dirt cheap ThinkPads, making cheap restorations/upgrades, and then installing Linux on them has been a really fun hobby lately.

It’s really a great example of an open source ecosystem that’s run in a professional and organized manner. Almost Arch levels of up-to-date-ness but with everything in the OS developed as a coherent whole. And the same philosophy applies to the ports free too. And even if the contribution process feels a bit dated with Bugzilla and patch uploads, it’s all well documented and approachable. Other FOSS projects can learn a lot :)

The never ending PR review dilemma....

In his mail "Data-Oriented Programming, Beyond Records", Project Amber lead Brian Goetz described a new #Java concept:

Carrier Classes

A generalization of records that allow us to succinctly define classes with a data-centric API that can participate in pattern matching and reconstruction.

Join me for the premiere on Thursday (22nd) 8am CET:
https://www.youtube.com/watch?v=cpGceyn7DBE

@ianthetechie I mean, that’s “enterprise” for ya! 😅

@raiderrobert noice!

I am continually impressed at the ability of giant orgs to succeed despite themselves.

I am reminded of saying that has been attributed to both Warren Buffett and Peter Lynch.

"Go for a business that any idiot can run, because sooner or later any idiot probably is going to be running it."

@geerlingguy my vote is bring the comments later.

@josh yup! CLI for the FTW!

Turns out text is still the universal interface

@raiderrobert this was *exactly* my experience with generating code for my current iOS project. It got enough done for me to say I saved myself weeks of effort, but I still had to reach in and change smaller bits of code that were clearly wrong to get it across the finish line.

I also learned that CLI tools tend to do better for me than embedded IDE tools.

@ianthetechie fascinating! Here in Chicago many of us have way too many physical keys since our apartments are a century or two old, picking up mail requires a separate key, some relatives share keys, our desks at the office have locks, etc.

@ianthetechie very nice! I’ve been wanting something better than the one built into my Mother-32…now you’ve inspired me to look into making an iPad app. 😂

Here's a mini guide on how to bring your website to up-to-date standards! You don't even need to have AI to be an AI company

Anti-patterns for distributed services:
- No timeout handling
- Missing retry logic
- Synchronous calls in critical paths
- Assuming 100% service availability
- No circuit breakers
- Complex distributed transactions
- Ignoring backpressure
- Treating remote calls like local ones
- Hardcoding IP addresses
- Assuming cloud regions never fail

What should I have added? 😱

Game

People keep making jokes about “vibe debugging” being hard.

I’m not experiencing this, personally. But then again perhaps my approach to LLM generated code is better described as “context driven coding” than “vibe coding”?

In both a legacy Java project and a generated Swift project, I was able to instruct a CLI running gpt-5.1-codex-max to successfully find root causes and write simple fixes.

In the legacy Java project, I also had it testing for and applying the fix by using TDD.