aleksiy123
Joined 5 years ago
Joined 5 years ago
Mythos > Fable ? Opus > Sonnet > Haiku
Tho I think it’s definitely not obvious at first glance. And requires some thinking to order if you are even familiar with the terms in the first place (I had to look up opus)
The ordering seems to be based on size?
I actually like the google one. Alphabetical categories. Essentially alpha beta without the existing connation.
I think the bigger problem it’s getting harder to order models linearly. As later versions of the model make different tradeoffs across dimensions.
There’s a lot of people different people from a lot of different ages and backgrounds.
Just because they haven’t seen all of the same sci-fi movies they aren’t qualified to work on ai?
Also, I love sci-fi but it’s also not always representative of reality.
Maybe even the best I’ve ever seen.
I see box is now a thing but no span?
So render text to image then use box right?
Does anyone know what the SOTA is for cad models from image or multiple images?
I was hoping to try doing some reproductions of stuff i saw in museums/palaces in Europe.
I feel like unique address per sender, receiver pair could cut down on so much spam.
And you can see exactly who is leaking your info.
But getting the last 10-20% actually requires your attention and many often many iterations.
Then you have 5+ things that are 80% done but kinda janky and broken in weird ways. Finishing them still takes work and discipline and can end up feeling overwhelming. Or you can swap to this new idea you just had in the shower, and get the dopamine rush all over again.
It sneaks up on you. Ironically discipline seems to be more important than ever. Easy to spend a bunch of tokens/quota and get nowhere but feel productive.
With multi repo it’s just a smaller constant friction on everything you do.
With mono repo everything is working amazing. Then you hit something big you need to solve to move on. So the friction is more spiky.
Edit: to add another thought. I feel like multi repo is more process oriented, while in mono repo you try to resolve that through tooling. Devs are just generally going to write about that more.
All of that plus runtime performance and features.
All of these things still matter for agents. I think it’s just less visible to a dev now.
But velocity, bugs, token costs are still being impacted. You only see that if you are tracking it.
Scaling maintainable code base is probably more important than ever with the fire hose of code incoming.
Runtime config is a pure function of environment.
A versioned binary/artifact should be the same across environments.
Release stage is a property of environment. (local/dev -> preview/staging -> prod)
If behaviour or value of something changes across environments it belongs as config and not code.
Easier to shit on people and things with hot take then actually have a grounded and coherent argument or realise that different companies/teams have different constraints, problems and environments they operate as well as different solutions.