The Bugged Dev

A Human Bugged by Bugs | Software Developer | Design Engineer | Building with AI | Learning Three.js 🥳

[The Bugged Dev @thebuggeddev]

Only if education could be this interactive ❤️‍🔥

I've had a looong wish to build something genuinely useful through vibe coding, and I finally did it.

A 3D human anatomy application built with @threejs using GPT 5.6 Sol.

It all started with a single design image that I created using GPT Image 2.0. I then used it to generate every 3D organ image, one by one.

Next, I converted each of those images into 3D models using @tripoai (and no, they didn't sponsor this 😄).

After that, I opened Codex, wrote a master prompt based on the design, and gave it the prompt, the design image, and all the 3D models.

Codex built the first version beautifully, but there was one big problem.

Every single 3D model was nearly 120-150 MB. That obviously wasn't practical for the web and was giving a performance of 16fps.

After a few iterations, Codex optimized each model down to roughly 2–5.5 MB while preserving the visual quality, reducing the total asset size from ~900 MB to just 28.6 MB. And each model loads on demand.

Along the way, Codex also generated those anatomical illustrations showing where each organ sits in the human body, and even created the interactive hotspot markers that explain different parts of every organ. It handled all of that.

The process wasn't exactly one shot, but it also wasn't difficult. You just have to do it step by step.

It genuinely felt like building something that could make learning anatomy much more engaging.

The inspiration came from @DilumSanjaya's 3D animal plant cell project. I remember seeing it and thinking, "I want to build something like this one day."

And I did it :D

Live: https://t.co/gIFgkj8UVB
Code: https://t.co/nijvyWcyxO

[The Bugged Dev @thebuggeddev]

@nathangu76 Opus 5.5 is still ahead as it follows details more closely but Kimi K3.1 Pro is also super close to those results.

[The Bugged Dev @thebuggeddev]

Clearly misleading information.

I’ve been using Kimi K3.1 Pro since yesterday to procedurally generate 3D models with bpy, and the results have been phenomenal.

This is just one example. I’ve generated plenty more, and it does all of this on its own. Not using any 3D Gen model at all.

Not sure why everyone is going against Kimi when it's really actually good.

It really shouldn’t be that hard to acknowledge that it’s a great model. Besides, it's an open weight model.

Doing good for humanity and advancing AI in general

[Elshayib @elshayib_]

Coming out of reddit Kimi K3.1 pro 3D work is mostly coming out of a 3D Gen model apparently.

[The Bugged Dev @thebuggeddev]

@ieditormurata Not even a buck, my friend. Not even a buck.

[The Bugged Dev @thebuggeddev]

@CryoberryWeb Yay, let's goo 🥳

[The Bugged Dev @thebuggeddev]

Can't believe what I'm seeing 🥹❤️

My recent project built with Gemini 4 Argon just made it to the official Google News page

https://t.co/yYe7OjhgyG

[The Bugged Dev @thebuggeddev]

@SammmAing Of course, i feel proud and so you should be. It's indeed great thing to be noticed by Goooogle itself!! 🫶

[The Bugged Dev @thebuggeddev]

@gracepursuits Omg, this means so much to me. Thank you so so much 🥹💜

[The Bugged Dev @thebuggeddev]

@miketaylorcai Thank you 🫶

[The Bugged Dev @thebuggeddev]

@ameliajtech It is indeed wild. Kimi K3.1 is really phenomenal!

[The Bugged Dev @thebuggeddev]

@LmbtnE i will for sure use kimi in production but why do i have to cut other subscriptions to do that 😂

[The Bugged Dev @thebuggeddev]

@clara_jane47268 Probably mostly because it's a chinese model lol

[The Bugged Dev @thebuggeddev]

@loktar00 Soon 🔜

[The Bugged Dev @thebuggeddev]

@ORameshO It's properly optimized, running well in browser. You can check it here: https://t.co/UqlZkDytEv

[The Bugged Dev @thebuggeddev]

@iSp4rklux_ It isn't like only Kimi did it. Many AI companies do same.

And with every new update, it's going to get better so it has to be like that, maybe

[The Bugged Dev @thebuggeddev]

@sachasayan It's simple Kimi chat through https://t.co/Xticp4TLg6

[The Bugged Dev @thebuggeddev]

@almosttomorrowe Sure, you can check whole thing Kimi did here: https://t.co/fHdKi2Bpgt

[The Bugged Dev @thebuggeddev]

@AI_Andrew Thank you for sharing this with me, otherwise, I would have never known 🥹💜

[The Bugged Dev @thebuggeddev]

@SahilPanhotra it really feels so.

maybe it's best to believe in own benchmarks and try test things 😅

[The Bugged Dev @thebuggeddev]

@vamsibatchuk Thank you so much 🥹🫶

[The Bugged Dev @thebuggeddev]

@clara_jane47268 Oh, how I wish that but no no and no.

[The Bugged Dev @thebuggeddev]

Claude Opus 5.5’s result on the same task as Kimi K3.1 Pro

[The Bugged Dev @thebuggeddev]

My honest take on Kimi K3.1 Pro 🥶

I asked Kimi to turn an art concept into a complete 3D environment at around 10:25. At the same time, I gave Claude Opus 5.5 the exact same task.

About an hour later, Kimi produced what you see below. A complete 3D scene running right in the browser, with reflective icy seas, drifting floes, rugged snow-covered fjords, and warm windows glowing against the cold.

Claude finished around the same time, but a little earlier than Kimi. So, clearly, Kimi has improved in terms of execution speed. It feels faster than its previous models.

Now, let's talk about cost. The task consumed 62% of my 5-hour session on the $100 Claude plan, whereas it used just 0.53% of my Kimi Vivace plan's session.

I followed up with another task to make some refinements, and that barely cost anything either with Kimi. Just 0.35% of my session credits.

You can do the math and see how much cheaper it is.

Finally, talking about the results, I think Kimi K3.1 Pro is really solid. When it comes to UI, it reminds me of GPT-6 Astra, while its overall capabilities feel closer to Claude Opus 5.5.

Although I preferred Claude's result overall in terms of 3D modeling, as it followed the original requirements in greater detail, Kimi K3.1 Pro came pretty close. In fact, Kimi presented the overall scene better than Claude.

Overall, I'd highly recommend giving Kimi a try. It really feels like it sits somewhere between the frontier models.

True to its benchmarks, i would say.

P.S. This is not a paid post. Kimi hasn't paid me anything, nor have they ever paid me in the past 😅

Live: https://t.co/RaVY55MeGY

[The Bugged Dev @thebuggeddev]

@AnonymerNutze12 You're welcome to see my bank statements 😂

[The Bugged Dev @thebuggeddev]

My honest take on Kimi K3.1 Pro 🥶

I asked Kimi to turn an art concept into a complete 3D environment at around 10:25. At the same time, I gave Claude Opus 5.5 the exact same task.

About an hour later, Kimi produced what you see below. A complete 3D scene running right in the browser, with reflective icy seas, drifting floes, rugged snow-covered fjords, and warm windows glowing against the cold.

Claude finished around the same time, but a little earlier than Kimi. So, clearly, Kimi has improved in terms of execution speed. It feels faster than its previous models.

Now, let's talk about cost. The task consumed 62% of my 5-hour session on the $100 Claude plan, whereas it used just 0.53% of my Kimi Vivace plan's session.

I followed up with another task to make some refinements, and that barely cost anything either with Kimi. Just 0.35% of my session credits.

You can do the math and see how much cheaper it is.

Finally, talking about the results, I think Kimi K3.1 Pro is really solid. When it comes to UI, it reminds me of GPT-6 Astra, while its overall capabilities feel closer to Claude Opus 5.5.

Although I preferred Claude's result overall in terms of 3D modeling, as it followed the original requirements in greater detail, Kimi K3.1 Pro came pretty close. In fact, Kimi presented the overall scene better than Claude.

Overall, I'd highly recommend giving Kimi a try. It really feels like it sits somewhere between the frontier models.

True to its benchmarks, i would say.

P.S. This is not a paid post. Kimi hasn't paid me anything, nor have they ever paid me in the past 😅

Live: https://t.co/RaVY55MeGY