The hard part for me is choosing the model and effort, that's why I always resort to Astra xhigh, but then it ends up consuming tokens so fast.

How do you decide what to pick? I mean, I do Platform work on a large monorepo with many different interconnected services, and so I always want the implementation to be "correct".

Simple as it sounds but I ask Sol or Astra to propose optimal model and effort level for a given workload. Works pretty neat for me.

A very relevant book that goes beyond the workplace (but also includes it): Alienation and Acceleration: Towards a Critical Theory of Late-Modern Temporality by Hartmut Rosa

Thank you for the recommendation!

I never had this dread after switching to Debian.

"him"? Have we reached that dystopia level?

I've been seeing a lot more anthropomorphization of these models on HN lately and it's alarming.

Not all HN visitors are native English speakers and in some languages "it" doesn't construct well with verbs, thus thought frameworks forms through usage of him/her. Nothing more to see I suppose.

It's a male name, and gendered pronouns can be hard for foreign speakers at times, irrespective of proficiency level. I wonder if you're overthinking this?

Every french person I've talked to IRL, for example, calls Claude "him." It's partly a language thing.

i prefer to call her Claudia

A database with built-in HA is a significantly more complex system than one without it.

And one built without it and not coordinating with it is often much harder to reason about when you bolt it on later.

Anyone remembers Teleport Pro?

Really.. I was scrolling to find a comment complaining for this slop GH issue, which should be 10% of the size of what it is.

Surprised me it took so much scrolling to get to this.

Like, who reads all that crap?

I just stumbled onto this, which probably explains it: https://openrouter.ai/announcements/gpt55-cost-analysis

I guess parent argues that:

  - humans have a track-record of writing memory bugs

  - memory-safe languages prevent such by construction

Therefore, what's the justification of not using a memory-safe language (as opposed to an unsafe one)?

> what's the justification of not using a memory-safe language

Use Go, Java or Fil-C, and memory safety is achieved at the expense of runtime performance. Tracing garbage collectors make your programs run slower and use more RAM.

With Rust you pay with complexity. Rust has new, weird syntax (lifetimes, HRTB, etc) and invisible borrow checker state that you've gotta understand and keep track of while programming. Rust is a painful language to learn, because lots of seemingly valid programs won't pass the borrow checker. And it takes awhile to internalise those rules.

I personally think the headache of rust is worth it. But I can totally understand why people come to the opposite conclusion.

> because lots of seemingly valid programs won't pass the borrow checker

Some straight-up valid programs as well

Rusts memory safety constructs do also impose a (much smaller) runtime performance penalty. Every Arc / Rc is a memory safe abstraction with runtime cost since rust has no way to prove cyclic reference graphs are safe at compile time.

Interop.

How about they are pointing out a worrisome direction society might be taking, whereas work will infiltrate even more what used to be family or personal time, thus accelerating burnout?