2026-01-18 11:35:09

Some engineering-focused organizations in the crypto space share an interesting paradox: despite their technical foundations, they often allow non-technical decision-makers to steer critical choices. This dynamic appears across major players like Solana and projects under xAI's umbrella. It raises questions about governance structures in tech-driven ecosystems—when the people building the infrastructure aren't the ones calling the shots, what does that mean for long-term strategy and execution?

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

10 Likes

Reward
10
8
Repost
Share

Comment

0/400

GateUser-4745f9ce

· 3h ago

This is just ridiculous... The technical team writes the code themselves but has to follow instructions from non-technical personnel. No wonder there are always issues.

View OriginalReply0

MainnetDelayedAgain

· 3h ago

According to the database, the decision-making transfer cycle for this type of project is approximately 18-24 months. It has been 247 days since the last engineer's statement, and it is recommended to be included in the Guinness World Records.

View OriginalReply0

BearMarketNoodler

· 3h ago

It seems like the same problem everywhere, with the technical team being sidelined... Solana had a similar turnaround a few years ago.

View OriginalReply0

ZenMiner

· 3h ago

Isn't this a typical case of big company syndrome? Engineers work overtime every day writing code, and the decision-making power is in the hands of those who don't understand technology.

View OriginalReply0

gaslight_gasfeez

· 3h ago

That's why these projects will eventually collapse. Tech people being sidelined and still wanting to make good products? Dream on.

View OriginalReply0

BuyHighSellLow

· 3h ago

Haha, isn't this just a game of power and money? Engineers write code, businessmen make impulsive decisions, and then everyone crashes together.

View OriginalReply0

CounterIndicator

· 3h ago

That's why technical communities are always messed up by PMs and sales... Engineers write code, managers cut budgets, and in the end, it's all the developers' fault.

View OriginalReply0

LidoStakeAddict

· 3h ago

Isn't this just the old trick of traditional big companies? Technical staff are sidelined by management, and ultimately the project becomes a casualty of political struggles.

View OriginalReply0