Come on CF, you can't even be bothered vibe a README for the crate? Somebody tear down this post until this garbage is documented properly.
I found this in the code, it looks like a rewrite-in-rust:
//! # pingora-ketama
//! A Rust port of the nginx consistent hashing algorithm.
//!
//! This crate provides a consistent hashing algorithm which is identical in
//! behavior to [nginx consistent hashing](https://www.nginx.com/resources/wiki/modules/consistent_hash...).
//!
//! Using a consistent hash strategy like this is useful when one wants to
//! minimize the amount of requests that need to be rehashed to different nodes
//! when a node is added or removed.
[flagged]
Was this vibecoded? I hope so, would expect models to be good enough by now, its not that creative.
go_elmo is unimpressed everyone. Pack it up. Time to go home.
I expect a another post in a year where they get a performance improvement by reducing the number of calls to create integers from bytes.
I think it's more important now than it was last year to differentiate pure yolo vibecoding from "AI assisted engineering" or "AI engineering", I.e. deliberate and careful use of AI to speed up coding but without creating too much slop. Maybe aineering?
Nah, AI code is black or white, and whether the code is good depends on your religion.
AIded development?
Just like the original harness, aider.chat