Build. Explore. Create.
A digital brand of Yuvaraj P. A developer identity, a creative technology brand, and a place to explore what happens when you build software from first principles.
It's the container for everything I build when I'm trying to understand something — not a product line, and not a company.
YuvaScript represents a mindset: build, explore, create. It's a place where ideas aren't only discussed or bookmarked. They get implemented, broken, and rebuilt until they make sense.
Some of what lives here will stay small. Some of it will grow. The first serious experiment is a programming language called Yuva.
A name for the work, and for the way it's approached.
A developer's technical point of view, made visible.
Where experiments run — including ones that fail.
Understand the layer beneath the layer you're using.
Yuva, and whatever curiosity leads to next.
The distinction matters, so it's worth stating plainly before anything else.
YuvaScript
The name, the philosophy, and the home for every experiment — of which a language is only the first.
Yuva
An experimental programming language — a way to find out how languages are actually designed, implemented and evolved.
Not because the world needs one. It doesn't. The languages we have are the work of enormous teams over decades, and Yuva is not competing with any of them.
But every language that exists was built by someone answering a question. Looking at those questions is the clearest way to understand why languages take the shapes they do.
Dates indicate first public appearance or initial design work. The questions are paraphrased, not quotations.
Six rules that decide what gets built, and what gets thrown away.
Before creating something, understand why it already exists.
Don't accept a convention just because it's everywhere. Ask why.
An idea only becomes real once it's implemented.
Start small. Make something work before making it good.
Every bug, limitation and design decision teaches something.
Yuva is allowed to change as understanding improves.
Where each part of Yuva actually stands today. Nothing here is marked finished, because nothing is.
Every language does some version of this. Select a stage to see what happens inside it.
Sketches of what writing Yuva might feel like.
CONCEPT SYNTAX — NOT YET EXECUTABLE.
These examples describe the direction Yuva is being designed in. The language
specification isn't finalised and none of this runs yet. Expect it to change.
// the smallest possible program let name = "Yuva" print(name)
Bind a value to a name, then do something with it.
let curiosity = true if curiosity { explore() build() create() }
Braces over indentation. No parentheses around the condition.
fn greet(name) { print("Hello, " + name) } greet("Yuva")
Short keyword, familiar call shape, no type annotations yet.
A direction of travel, not a commitment. Versions ship when they teach something, not on a date.
0.1
Foundation · current0.2
Expansion0.5
Experience1.0
MaturityThis roadmap is aspirational. Items will move, merge or disappear as the experiment teaches what actually matters.
Build what you want to understand.
Curiosity is not a distraction from engineering. It is often where engineering begins.
Every abstraction hides a story.
Learn the layer beneath the layer.
A small working system teaches more than a large unfinished idea.
Don't rush to 1.0.
Code is not only a tool for solving problems. Code can also be a way of asking questions.
The language is the first experiment. It won't be the last.
An experimental programming language.
In developmentSmall technical explorations that answer one question each.
OngoingTools built to understand something, then kept because they're useful.
OngoingIdeas, decisions, architecture and what each experiment taught.
PlannedWhatever curiosity leads to next.
OpenTurn ideas into working systems. Something that runs beats something that was only ever described.
Understand how things work beneath the surface — the layer you normally take for granted.
Make something that did not exist before, even if only you ever use it.
YuvaScript / 001
You don't need to know where the experiment ends. You just need to start building.
YUVA
BUILD.EXPLORE.CREATE.
An experiment is never finished.