Why Children Should Create Before They Learn to Code

Imagine giving a child a box of LEGO bricks and asking them to build something. Some children might immediately begin putting pieces together. Others may spend time imagining what they want to create. They might build a house, a vehicle, or something that doesn't have a name yet. Along the way, they discover that certain pieces fit together, some structures need support, and an idea that looked simple in their imagination may take several attempts to bring to life.

Now imagine asking the same child to learn all the rules of construction before touching a single brick.

Something important would be missing from that experience. The opportunity to discover, experiment, and experience the joy of making something.

We began noticing this connection more than a decade ago while coaching students for robotics competitions, including FIRST LEGO League. Students worked together to build LEGO robots, program sensors, and solve challenges. What fascinated us was how differently they approached the experience. Some students loved constructing the robots. Others enjoyed programming their movements, while some became deeply involved in the innovation projects, where they could imagine solutions to real-world problems.

Not every student was immediately interested in programming, but many were excited about creating something. That interest often became a natural reason to explore the technology behind their ideas.

A student building a robot might eventually ask how to make it stop before hitting an obstacle. Another might wonder whether a sensor could help the robot follow a line. Suddenly, programming wasn't an isolated subject to study. It became a tool for solving a problem the student cared about.

Over time, we helped students move from visual programming into Swift, where they began building applications that were eventually published on Apple's App Store. The transition was rewarding, but it also revealed some challenges.

Students who enjoyed building and experimenting sometimes found themselves spending more time dealing with programming syntax than exploring their ideas. A missing symbol or an unfamiliar instruction could interrupt the creative process. Some students were comfortable working through those details, while others needed a more approachable starting point.

We began asking ourselves a different question. What if students could begin creating digital products with the same freedom they experienced while building LEGO robots?

That question eventually led to Playground Engineer Studio.

PGE Studio is an iPad-first creative computing environment where students begin with visual objects rather than programming instructions. They can create shapes, adjust colors, experiment with movement, and build relationships between objects. As their creations become more complex, they encounter ideas such as repetition, cause and effect, and how different parts of a system work together.

Consider a student creating a snowman. At first, the activity may seem like a simple art project. The student creates circles for the body, adds eyes and buttons, and adjusts their positions. But as the project develops, interesting questions begin to emerge. Should the eyes belong to the head? Could the buttons be created using repetition instead of separate instructions? What would happen if the head moved?

These questions introduce computational thinking through something the student already understands.

Behind the scenes, PGE Studio generates corresponding programming code in Swift, Python, and JavaScript using predefined rules. The student doesn't need to write that code to begin creating, but the code is available to explore through I Can Read Code when curiosity or readiness develops.

We are not suggesting that learning programming syntax is unnecessary. Students who move into professional development will still benefit from understanding how code is written, tested, and maintained. Our belief is simply that syntax doesn't have to be the first barrier a child encounters when exploring technology.

This approach also creates opportunities for children with different interests. A student who enjoys art might begin by creating an animated character. Another who loves games might experiment with rules and interactions. A student interested in storytelling might create a scene where objects respond to events.

Each begins with something meaningful to them, and each has an opportunity to develop an understanding of how technology works.

As AI makes it easier to generate software, we believe this kind of experience becomes even more relevant. Children will grow up with tools that can produce code quickly. But they will still need to understand problems, make decisions, test ideas, and recognize when something doesn't work as intended.

Our goal is to give students opportunities to develop those foundations early, without taking away the satisfaction of figuring things out for themselves.

We don't expect every child who uses Playground Engineer Studio to become a software engineer. Some may become designers, scientists, entrepreneurs, or pursue careers we haven't imagined yet.

What we hope they carry forward is something more fundamental: the belief that technology is not simply something they use, but something they can understand and create.

Sometimes, that journey begins with a LEGO robot. Sometimes, it begins with a snowman on an iPad.

And sometimes, all a child needs is the freedom to begin.