374 karma · joined September 24, 2019
This was the first shape that seemed to have a kernel where if you related to as a reader, I thought it was a good indication that you'd enjoy the whole piece.
So I want to be less afraid to do that. Because at the end of the day, if I decide it's too stolen, I can always just not release it.
I think there's something here that's a little different from just "refrain from criticism" that I needed to hear which is something like "you can spend a lot of time trying to find the perfect way to do something, or you just do it many different ways and see which you like better" and frankly, I spent so much time noodling, it might have been _less_ overall time if I'd just forced myself to record some very formulaic versions I was averse to, and seen if any of those inspired me to actually get the thing done.
I liked "Instead, it’s about creating one version of a project that will likely either be improved upon in the future or serve as inspiration for something else. The key is to cultivate the commitment and conviction to declare that something is done, for now." from your piece. I think that's what I'm trying to get at.
That said, I don’t think that just because this is the way things are, this is this is the way things have to be. Even with our interactions with AI. And I have hope.
Ted Chiang had a great piece in the New Yorker years ago called “Why AI isn’t going to make Art”[1] where he describes something similar. There are 10,000 choices to make in every good pieces of art. AI makes the average choice for every decision and the average choice is derivative and uninteresting. There in I think lies both the problem and the solution. Rather than autocompleting our work, we’d all be so lucky to have a captivated and motivated reader who asks all of the questions this author suggests, so we can get better and better at asking them ourselves and making great art.
[1] https://dmd-program.github.io/dmd-300-master/assets/Chiang-A...
In fact I think the opposite is true. The Zcash bug was found with opus 4.6 or something like that. Many worse models currently in the wild might be very capable but not yet industrialized for bug finding.
Another example from today. Cryptography system that’s been around for decades: https://eprint.iacr.org/2026/1630
It’s going to be a bumpy few months
Though, like, I guess I expect that when this comes out, all the opus traffics will move over. It does appear to be much more capable, just jury is out about how much more capable
If smaller models can find these things, that doesn’t mean mythos is worse than we thought. It means all models are more capable.
Also if pointing models at files and giving them hints is all it takes to make them find all kinds of stuff, well, we can also spray and pray that pretty well with llms can’t we.
It just points to us finding a lot more stuff with only a little bit more sophistication.
Hopefully the growing pains are short and defense wins
I appreciate the sentiment and I agree. While I think there are countless humans who could do way better, I was never going to hire someone to illustrate this. Furthermore, I don't think it reads very interestingly without the images. I doubt it would have even gotten published.
But now thousands of people have seen it, it's shown that it can strike a chord. Maybe it is worth polishing a little more. It would be adorable as a small book
Still, right now I think we can tell, so I focused on making sure they were my words, but I let an llm help edit and I think it honestly made it much more readable
I tried to focus on 3 main bits:
Early exploration, problems between people, and then how much is ultimately in or out of your control
What ruined it for you?
To answer a few of your comments:
Writing is all mine but I had Claude proofread it, in addition to some close friends. Honestly it pointed out some great weaknesses in the original draft.
The art is all nano-banana through a tool called flora ai. I’d love to work with a human illustrator for something like this. I can draw, but I can’t paint and there’s an aesthetic here I think it handles better than I would have.
Man, it’s amazing that I can get something out there that expresses a vision all by myself. If this were a revenue generating project like an actual children’s book or something I’d love to work with someone that could bring it to life a bit more.
The other interesting bit is that you can have an arbitrary map size and just repeat it. The game is 32x32 but it could be whatever.
https://blue-sphere.fly.dev/play?map=s3-01
Anyway, great stuff you have here!
If you need a video to try it out, maybe grab a clip from one of these: https://www.youtube.com/results?search_query=halo+windmill+s...
When I write a sql query that includes a vector search and some piece of logic, like: ``` select name from users where age > 21 order by <vector_similarity(users.bio, "I like long walks on the beach")> limit 10; ``` Does it filter by age first or second? I've liked the DX of pg_vector, but they do vector search, followed by filtering. It seems like that slows down what should be the superpower of a setup like this.
Here's a bit more of a complicated example of what I'm talking about: https://blog.bawolf.com/p/embeddings-are-a-good-starting-poi...
https://hexdocs.pm/elixir/1.12/typespecs.html
They’ve recently started gradual typing which will feel a lot like typescript in the early days where you can type some things but you’ll frequently need the escape hatch ‘dynamic’ which is their ‘any’ to make it compatible with existing code
https://elixir-lang.org/blog/2023/09/20/strong-arrows-gradua...
I bet if we put a better description into the embedding for 'ruler,' we'd avoid this. Something like "a straight strip or cylinder of plastic, wood, metal, or other rigid material, typically marked at regular intervals, to draw straight lines or measure distances." (stolen from a Google search). We might be able to ask a language model to look at the icon and give a good description we can put into the embedding.
I don't expect to have to change the embeddings for each icon all that often, so storing them seemed like a good choice. However, you probably don't need to cache the embedding for each search query since there will be long-tail ones that don't change that much.
The reason to use pgvector over blobs is if you want to use the distance functions in your queries.