241 karma · joined August 13, 2024
Junior dev: Make me a sandwich.
Senior dev: We’re building a sandwich. It needs a roasted tomato, thin sliced, X mm in thickness. Add some bacon. I want mayonnaise but it needs to be feature gated.
One sandwich later. . .
Senior dev: where’s my bread man?
What blog post are you talking about? This is still up: https://blog.google/technology/developers/introducing-gemini...
Edits: ugh typos
My strategy involves building stateless apps with distributed services that have good support in Kubernetes like Yugabyte and Minio.
What I do is host the thing on a cheap cloud server until it grows enough to need HA or scaling. At that point I move my workloads into a cluster.
I already have everything patterned out though so, I’m living in some sunk costs if anything newer or truly better comes along.
I just don't see what doesn't "scale" exactly here. Been using k8s for 7 years, never had a problem that wasn't my own fault. Even for parallel processing, I feel like there's so many options and patterns to use because it depends on the task the job does.
Competing looks like starting with what other people are already doing and making it better.
In the comments of the post, homie points at this for the text: https://www.hawley.senate.gov/wp-content/uploads/2025/01/Haw...
---
Haven't read it yet, will come back with an opinion after I see what all the fuss is about.
---
Edit: Read the bill. Pretty short.
Reminds me of the fight against cryptographic systems. Kinda hilarious imo.
IANAL
The most useful and valuable feature of LLMs imo is using the embeddings to enhance document search. There are smaller models that are just as good for this though.
I doubt anyone will really do anything worth-while in maintaining CockroachDB when it's latest version eventually does falls into Apache licensing.