HN user

jinay

439 karma

https://jinay.dev/

contact: hi at jinay dot dev

Posts18
Comments62
View on HN

I recently did a deep dive on open-endedness, and my favorite example of its power is Picbreeder from 2008 [1]. It was a simple website where users could somewhat arbitrarily combine pictures created by super simple NNs. Most images were garbage, but a few resembled real objects. The best part is that attempts to replicate these by a traditional hill-climbing method would result in drastically more complicated solutions or even no solution at all.

It's a helpful analogy to understand the contrast between today's gradient descent vs open-ended exploration.

[1] First half of https://www.youtube.com/watch?v=T08wc4xD3KA

More notes from my deep dive: https://x.com/jinaycodes/status/1932078206166749392

https://github.com/JinayJain/dictator

Built one for myself. It's context-aware and promptable.

Tested well on Linux, not so much on other platforms but in theory should support them.

It's a bit meta but I wrote it mostly using Claude Code. Once I had an MVP, I was able to prompt much faster by just speaking out what I wanted it to change.

I used to think that typing speed was not really that important, especially when now we have so many LLMs doing the typing for us. But honestly, now I think it's even more important because the specificity and detail in your prompts are paramount to getting a good response, and something like a dictation tool (which is what I'm using right now) is really good for generating very specific prompts.

In fact, I wrote all this out using a dictation tool in ~20 seconds (258 WPM).

That's not the only concern though. The web is by far the most accessible way to distribute something, which is paramount in getting people to use it.

Cursor is likely very tuned for Claude (prompts-wise and all) due to its dominance with 3.5 and now 3.7. Still, Gemini 2.5's tool calling has been pretty poor in my experience which Cursor heavily relies on.

When I was first learning computer vision, I wrote a program that could tell the time from an image of a clock [1]. I had no purpose for it besides the fact that it seemed like a cool problem to try and solve.

Years later, I get an email from a stranger in Korea, asking me how to run my program. Why would he want to use my silly program? Turns out you can adapt the code to read analog pressure gauges which is really useful for chemical plants. Goes to show that there's often a use for most things.

[1] https://github.com/jinayjain/timekeeper

Meta Llama 3 2 years ago

It's almost guaranteed that there will be quantizations and adaptations to consumer hardware that should make it both versions of the model accessible to mortals on consumer GPUs (and even CPUs).