All writings

The Art of Building and the Art of Undoing

An Architect's Reflection

A reflection by the original architect of devv.jobs & unicorncoders on how a product built on integrity and respect rose organically across Europe, and how it was undone when vision was replaced by management.

After many years of silence, there is value in reflection. Not to assign blame, but to understand. To understand the difference between building and managing, between seeing and merely steering. This is a reflection on a structure that, between 2018 and 2022, underwent a dramatic ascent and an equally instructive collapse. It is a case study in the most critical of all leadership skills: the art of noticing.

All meaningful creation begins by noticing something that others have missed. Our platform was born from a genuine observation of a market that was technically functional but spiritually bankrupt. For software developers in Europe, the landscape was a source of constant frustration. We didn't just see a business opportunity; we saw the silent friction, the unspoken desire for a platform built on respect.

My architectural answer was not an incremental improvement but a radical inversion of the existing model.

First, I dismantled the power imbalance by making salary transparency non-negotiable. No more guessing games, no more wasted time.

Second, I eliminated fear by building a system of true anonymity, allowing professionals to explore the market without risking their current employment.

Third, I declared war on noise by designing an elegant shield against recruiter spam, ensuring that every interaction was meaningful.

These were not mere features; they were declarations of respect encoded in the system.

The entire concept and its execution were designed for the talent, not for the sellers of talent. This philosophy was the foundation. The success that followed was not the result of an aggressive marketing budget, but of organic expansion. In just two years, without external growth capital, we took leading positions in several European tech hubs — from Berlin through Amsterdam to Warsaw and Vilnius. It was proof that an architecture of authenticity, transparency, and technical rigor could still cut through the noise of a saturated market.

For every growing organization, there comes a moment when structure must meet scale. New investors arrived, carrying with them a different logic — one born not of systems thinking but of management orthodoxy. They saw not an ecosystem to be nurtured, but a machine to be controlled; a belief in mechanical efficiency drawn from the industrial age of Taylorism, utterly alien to an organization that thrived on trust, culture, and tempo.

The contrast was total. We had built through a trust economy, with openness as our driver; they tried to steer through control and calendars. It was leadership trained to see numbers, processes, and hierarchies — but blind to the subtle, human systems that were the company's true engine.

The deeper failure, however, lay in the quiet usurpation of vision. The very pillars that had built the company, authenticity, transparency, rigor, were soon presented as the inventions of those who had merely inherited them. It was a silent annexation of another's work, an act that opened an irreparable trust gap with the original team.

The collision between a fast, learning product culture and an administrative model from the 20th century created a fracture that could never be sealed. Where one side built with algorithmic precision informed by user feedback, the other responded with elaborate strategies and the logic of authority. When data and insight challenged directives, they were not treated as opportunities for discovery but as acts of insubordination.

It was a peculiar strain of leadership, confidence operating in inverse proportion to insight. The result was paralysis: meetings multiplied, clarity evaporated, and the product lost its pulse.

During a brief restructuring, the team was given a chance to reclaim the product's direction. In three months, we corrected the course and launched a version true to its origins. It stood as proof that the original vision had never failed — only been obscured.

Capital is, at its core, a vote of confidence. When investors witness and boards co-create a dissonance between a leadership that cannot see and a team that still does, the rational choice is to withdraw that confidence. The financial unraveling that followed was not the cause of the fall but its confirmation: the internal trust capital was already spent.

The end was not an orderly wind-down to preserve value, but a stalemate of egos. The focus shifted from serving users to settling accounts. It was an unworthy conclusion for something once so vital.

Looking back, there is no bitterness, only clarity. The story of this company is a lesson in leadership and in perception. A company's soul is not a line item on a balance sheet, yet it remains its most valuable asset. Scaling is never about replacing founders; it is about scaling the principles that made the founding possible.

The greatest tragedy is never a company's failure. It is when a company had every potential to succeed but was led by those who looked without seeing.

I write this not to mourn but to document, so that the next generation of architects can see where the blueprint went wrong, and why.

When the structure finally collapsed, responsibility did not fall upon those who had steered it off course. It landed, as it so often does, on the original architect. Narratives were rewritten; the failure of management recast as a flaw in vision, a convenient fiction meant to manufacture shame.

But a blueprint is not invalidated by a poor builder, and shame requires one's consent. I chose not to give it. True vindication is never a public argument won but the quiet act of building again, applying the same principles of clarity and authenticity to new structures.

Time, in the end, is the final auditor. It reveals who built from genuine insight and who merely managed from borrowed authority. The former, even after a fall, always find new ground to build upon.

That same blueprint, re-applied in tech recruitment, went on to generate millions, a quiet proof that the design itself was sound.

And those who only know how to manage from borrowed authority? They eventually discover they have nowhere left to go.

Read original on Medium ↗
Carry forward

An Architect's Reflection