Browse Comments — Clean (de-noised)

The connection between EQ and performance makes a lot of sense when you consider how much of work revolves around people, not just tasks. Technical skills open doors, but how you show up determines what happens next. Justin Wright

Most people spend 20 hours watching tutorials to avoid spending 20 minutes building something real 😂

Cuts into his business model too apparently

Luís Rodrigues This is a useful simplification because many organisations still discuss these components independently rather than as an integrated operating system. From what I’ve seen, the real enterprise challenge rarely sits in the individual layers themselves. It emerges at the orchestration layer: - how context flows across systems - how permissions are governed - how decisions are validated - and how actions remain observable, controllable, and accountable at scale That’s where many AI deployments become significantly harder than the architecture diagrams suggest.

Strong performers usually show it through steady presence and how comfortable others feel speaking up around them, Justin Wright. That kind of energy quietly lifts the whole team and improves how work gets done.

Chris Olah saying publicly that competitive pressure, capital pressure, and geopolitical pressure push AI labs in directions that can conflict with doing the right thing — that's not a philosophical observation. That's a structural admission that external governance is load bearing, not optional. For healthcare organizations making AI procurement decisions right now, that statement should change how they evaluate vendor accountability. A vendor whose own co-founder acknowledges these incentive conflicts exists is a vendor whose contractual governance requirements, audit trail provisions, and human override protocols need to be airtight before a single patient record touches their system. The trust problem isn't theoretical. One of the architects of the technology just confirmed it from the Vatican. That's about as public as a warning gets.

To the surprise of no one since its being forced on us in every facet of living.

Framing MCP as the nervous system is spot on. Most enterprise agent architectures stall out because teams treat tool integrations as a series of fragile, manual API hooks. Standardizing that connection layer is the only real way to build workflows that scale without constantly breaking down.

EQ separates good managers from great leaders. The ability to regulate reactions and stay empathetic under pressure is what builds lasting trust.

This is so much easier to digest. Thank you for not making me watch a talking head

When you own your mistakes, you send a message and set a standard that shows strength.

Luís Rodrigues Each layer has a distinct role, and the real power comes when they are designed to work as one system instead of separate parts. Thanks for sharing.

A lot of AI systems fail because teams focus heavily on the “brain” and underestimate the importance of grounding, orchestration, and reliable connections between tools.

I think Internet Computer Protocol will play a role. This is the whois info on the domain subnet.ae. Notice that the registrant is the Swiss Subnet. What is the Swiss Subnet? And is Swiss Subnet going to be assisting the UAE with this? "Cloud infrastructure for the AI era. Swiss Subnet provides sovereign execution environments built in Switzerland for AI-native, regulated, and mission-critical workloads, where legal jurisdiction, technical control, and physical operation are aligned." Look at the bottom of the page of the Swiss Subnet. It's powered by the Internet Computer Protocol (ICP). Swiss Subnet:

It looks great but RAGAS still imperfect...

EQ is rarely proven by being nice. The real test is what happens when your ego feels threatened. Many leaders think they need more empathy, but first they need the ability to stay calm long enough to hear the uncomfortable truth.

If task is vague, they complete the wrong thing fast. The hands need guardrails... runtime bounds max spend, max actions, and approval for high risk actions, and audit trails, and kill switch. The nervous system MCP is the wiring. The brain LLM is the intelligence. The hands Agent are the execution. All three need to be designed together. The weakest layer diagnostic is the starting point.

The one thing I’d add: make people delete or rewrite their first Project prompt after a few days. The first version is usually aspirational. After 10 real tasks, you learn the weird stuff Claude keeps getting wrong: tone, assumptions, formatting, when to push back, when to ask. That second prompt is where it starts getting useful.

Well said. Technical skills might get people through the door, but emotional intelligence is often what determines how far they grow. Self-awareness, communication, and understanding people become even more important as responsibilities increase. People rarely remember only what you achieved, they remember how you made them feel while working with you.

Feels like a solid ramp-up, the real test is whether it actually becomes part of your daily workflow or just another setup you forget after day 3.