We’re nerds.
That’s the point.
A skeptical friend. A butter-passing robot.
And a small moment that explains a lot about why we’re here.
We’re the kind of people who get excited about a really good piece of code. Who try a new tool because we can’t help wondering what it might make possible. Who hear a ridiculous idea and immediately start figuring out how to build it.
We know. Nerds.
But the part we love most is what happens when something that only existed in someone’s head becomes something they can actually use. A page you can open. A button that does something. A little world you can step into.
One of our favorite examples involves butter.
“What would you like me to build?”
In the early days of working with agentic AI code generation, I was talking with a friend who wasn’t convinced. His view was straightforward: AI couldn’t produce anything of value.
I was spending a lot of time with these tools, and what I was seeing made me want to challenge that. So I asked him what kind of app he’d like.
Somehow, we settled on a butter-passing robot game. A little robot you could control in a 3D world, built with Three.js. Its very important job: pass the butter.
About five minutes later, I sent him a link.
From “what if”
to “here, try it.”
He played it. He agreed it was amazing. And then he said the thing that stuck with me:
“But not just anyone
could do this.”
Maybe he was right.
I knew how to talk to the agent, what to ask for, and how to get the result into a browser. I had a feel for what would work and what would need fixing. Those things came from being deeply, happily nerdy about software for a long time.
The five minutes were real. So was the experience behind them.
Please pass the butter.
A fresh little recreation of the idea that started the conversation. One robot, one breakfast table, one very important delivery. Your turn.
One robot. One very important job.
Built with Three.js. Best enjoyed with a little curiosity.
What if more people could?
A tiny robot game doesn’t prove that every software problem can be solved in five minutes. A useful, dependable app takes care: understanding the problem, making good decisions, testing what happens, and sticking around to improve it.
But that afternoon did show us something worth paying attention to. The distance between having an idea and trying it out was getting shorter. And knowing how to work with the tools made a remarkable difference.
My friend had shifted the conversation. We’d started with whether AI could make anything worthwhile. Now we were talking about who could actually make use of it.
That second question is the one we keep coming back to at DRD.
There are people with a business to run, a community to bring together, or an idea they’ve been carrying around for years. They can describe what they need. They shouldn’t have to become fascinated by deployment pipelines before they can start making it.
Our kind of nerdy.
For your kind of idea.
We want to put our capabilities in other people’s hands. The technical knowledge, the tools we’ve learned to work with, the small decisions that make an app feel right. All the things that helped turn a strange request into a link my friend could open.
That’s the intention behind DRD: a place to start with an idea, build with a coding partner, and keep shaping what you make. We put our experience into the foundations, templates, and components so you have something solid to work with. And when you need a team to take on a custom build, we can work with you directly.
We still get excited about the code. We still disappear into the details. We still think a tiny butter-passing robot is an excellent use of an afternoon.
We just want more people to experience the part where an idea becomes real.
We’ll bring the nerdy.
You bring the idea.
Keep the conversation going.
What would you ask a coding agent to build? Share a thought or a question. Comments are public.
Loading comments…