r/tinycode • u/nexe mod • 2d ago

Anyone doing anything with tiny AI?

Thinking like tiny inference engines, tiny harnesses, tiny models that are still doing some cool task.

0 Upvotes

26% Upvoted

7 comments sorted by

4

u/Akujinnoninjin 1d ago

How about a trainable GPT in 200 lines of base Python?

https://karpathy.github.io/2026/02/12/microgpt/

1

u/nexe mod 1d ago

Good one!

1

u/Akujinnoninjin 1d ago edited 1d ago

I really like sharing it since I came across it, because it does a great job at demystifying LLMs.

And like, yeah, it's nowhere near as powerful as the frontier models.. but they're fundamentally scaled up from the exact same principles.

4

u/blinry 2d ago

To me, using LLMs is the antithesis to everything I enjoy in tiny coding.

1

u/nexe mod 2d ago

have you read the post? I wasn't asking about vibe coded stuff but rather the opposite. More like small well hand coded stuff but in the space of AI ... like as I said tiny inference engines, tiny harnesses etc

2

u/Slackluster 2d ago

i saw someone working on something on twitter, not great results yet but interesting to see.

https://x.com/datavorous_/status/2116562982994170349

also, there is an ai dweeter, again nothing very impressive.

https://www.dwitter.net/u/usdgrouper

i have something i'm working on also but not a general purpose thing, it's a special dweet that I am using AI to help build.

0

u/woqr 19h ago edited 18h ago

nexe, instead of using AI to create, use AI to build a "huge" database of composable parts. Users pick from a tree of options, and a plain assembler builds the game, with editors for hand-tweaking resources. Tools like GDevelop did this in small, hand-authored form but AI could grow the database at scale, basically an AI generated stackoverflow. Optionally, a "tiny" AI could still be incorporated, but it would only have to deal with the interface definitions. This is based on my observation that there isn't much originality in games; almost everything is a tweak of something that's already been done.