If you've landed on this site, you've probably noticed the name. Creative Coding. Not "Gutui Engineering Consulting." Not "CG Tech Solutions." Not any of the safe, corporate-sounding names that a branding agency would suggest.
Creative Coding. Two words that have followed me for over fourteen years, from a small web development shop in Bucharest to an engineering leadership role at a European tech company. And even though what I do has changed dramatically, the name still fits, maybe more now than ever.
Let me explain why.
The origin story is simple
I registered creative-coding.ro in 2011 when I started my first company. I was twenty-something, building websites for small businesses, and I needed a name. I didn't overthink it. I just picked two words that described what I believed: that writing code is a creative act.
At the time, it was almost a contrarian position. Programming was widely seen as a purely logical discipline: a mechanical translation of requirements into instructions. You get a spec, you write the code, you deploy it. Creativity was for designers. Engineers just built what was asked.
I never believed that. Even in those early days, building WordPress sites and custom e-commerce platforms, the interesting problems were never about syntax. They were about finding elegant solutions under constraints. About designing systems that were simple enough to maintain but flexible enough to grow. About making choices when the spec was ambiguous, the budget was tight, and the "right" answer wasn't obvious.
That, to me, was creative work. It just happened to produce code.
What Creative Coding means now
Fourteen years later, I lead engineering teams. I don't write production code every day. My deliverables are team structures, delivery processes, architecture decisions, and hiring strategies, not pull requests.
And yet, the philosophy hasn't changed. If anything, it's become more central.
Creative Coding is a way of thinking about engineering problems. It's the belief that the best solutions don't come from following a playbook, they come from people who understand the problem deeply enough to see options that the playbook doesn't cover.
Here's what that looks like in practice:
When building teams, Creative Coding means hiring for curiosity and judgment, not just technical skill. The best engineers I've worked with aren't the ones with the most impressive resumes. They're the ones who ask "but why?" one more time than everyone else, who question the assumption behind the ticket before writing a line of code.
When making architecture decisions, Creative Coding means resisting the temptation to reach for the popular framework before understanding the actual constraint. Sometimes the most creative solution is the simplest one. Sometimes it's the one nobody suggested because it requires rethinking the problem entirely.
When shaping delivery processes, Creative Coding means recognizing that process is a tool, not a religion. The best process is the one the team actually follows because it makes their work better, not the one that looks impressive in a slide deck. This requires creativity: observing what's actually happening, diagnosing what's actually broken, and designing something that fits this team in this context.
When mentoring engineers, Creative Coding means teaching people to think, not just to execute. It means helping someone develop their own engineering judgment rather than making them dependent on yours. It means asking questions that open up their thinking instead of giving answers that close it down.
Why it's not just about code
The word "coding" in Creative Coding is increasingly metaphorical, and I'm fine with that.
The core idea was never really about the code itself. It was about the approach. It was about rejecting the assembly-line view of engineering where requirements flow in one end and software comes out the other, and nobody in the middle needs to think creatively.
Every meaningful engineering decision involves creativity:
- Deciding what to build and what not to build
- Designing a system that balances today's deadline with next year's scale
- Structuring a team so that people can do their best work
- Communicating a technical trade-off to a non-technical stakeholder in a way that leads to a good decision
- Finding a way to deliver value when the timeline is tight, the scope is unclear, and the team is stretched
None of these have a deterministic solution. All of them require judgment, lateral thinking, and the willingness to consider that the obvious approach might not be the best one.
That's Creative Coding.
The bridge between old and new
This website used to be a portfolio. It showed screenshots of websites I'd built for small businesses: dental clinics, real estate agencies, cleaning companies. It said "we" even though it was mostly me. It listed services like "Web Development" and "Cloud Integrations" and "Technical Consulting."
That version of creative-coding.ro served its purpose. It represented a legitimate chapter of my career, one where I learned the full weight of running a business, managing a team, and delivering for clients under real constraints.
But it doesn't represent who I am anymore.
Today, Creative Coding is less about the websites I build and more about the teams I build. Less about the architecture of a single application and more about the architecture of an engineering organization. Less about writing clever code and more about creating environments where clever people can do their best work.
The name stays because the philosophy stays. Engineering is a creative discipline. The best solutions come from people who think beyond the ticket. And the role of a leader is to protect and nurture that creative thinking, not to process-engineer it away.
In the end, it all becomes ones and zeros
There's a beautiful tension at the heart of Creative Coding. No matter how creative the thinking, how elegant the architecture, how inspired the solution, it all compiles down to ones and zeros. Binary. On and off. The most deterministic thing in the universe.
And yet, the path from problem to those ones and zeros is anything but deterministic. It's messy, human, full of judgment calls and trade-offs and moments where someone has to look at an ambiguous situation and decide: "this is the way."
That space between the human problem and the binary output, that's where Creative Coding lives. It's where the craft is. It's where I've spent my entire career, and it's where I plan to stay.
This is the manifesto, if you want to call it that. Not a mission statement drafted by committee, just an honest account of why I do what I do the way I do it. If it resonates, I'd love to hear from you.