The Few Bets That Matter
Investing is unforgiving. One small mistake can be very costly, and there’s no way back.

$NBIS might be that mistake for me this year.

This isn’t hindsight bias. I said the very next day that selling was a mistake as the stock didn't break my conditions to hold. Sentiment took over and I took a decision I shouldn’t have.

That’s all it takes.

The last week and a half cost me a few salaries in unrealized P&L. One emotinal afternoon cost me months of work.

I’m not here to complain. I’m here to be transparent, to illustrate how critical systems - and respecting them, really are.

Your system exists to protect you from yourself.

Ideas, opinions, convictions can make money. But they can't regularly outperform. Over time, convictions turn into bias, and bias costs.

Systems only can compound over decades. And the single most important rule is simple: don’t break it.

I broke mine. Now I have to work on fixing that.
Mistakes are opportunities to improve.

Few $NBIS notes after this quarter.
I'll be the bear, once more.

I continue to believe the market will punish the stock - or not reward it as much as many expect.

Not because the company isn’t excellent, but because it did not reward $GOOG, so why would it reward $NBIS for the same behavior?

Fundamentally, everyone will be bullish. Demand is through the roof, compute was sold out, management is planning to build more sites, etc...

Everything FinX wants to see.

From a market perspective, Q4 CapEx slowed down, guidance talks about ~20% increase of contracted power for FY26 without news on connected power, except for the upgrade from 7 sites to 16 sites.

This means FY26 CapEx will accelerate - just like for everyone else, and won't slow down FY27 as contracted power continues to climb.

More spending. Which was punished across all hyperscalers.

Also note that ARR guidance wasn’t increased, meaning no beat expected hence nothing above expectations and no buildouts closing faster than expected.

Some will say "why would you want more? It doesn't matter, they are executing at their pace"

I disagree. Acceleration is everything, otherwise you'll miss on expectations just like they did.

That revenue miss is due to real-world constraints, as I’ve shared yesterday and for months: you cannot build faster than physics and logistics allow you to.

The issue is that growth factually slows/doesn't accelerate. Growth stocks work on acceleration not stable growth.

The why doesn’t matter, even if you’re supply constrained.

Growth slows, CapEx increases, cash generation decreases, and there are no certainties that demand won’t be fulfilled by other hyperscalers by the time infrastructure is built.

Like many of you, I believe there will be demand and everything will be fine. But today, you cannot know. You can bet on it, but you cannot know.

That is the issue. And that is why the market might react like it did for $GOOG.

I continue to believe the company is excellent and its future is bright. And that the stock won’t be rewarded as much as many expect in the short term.

I’d love to be wrong. - The Few Bets That Matter
tweet

Dimitry Nakhla | Babylon Capital®
RT @DimitryNakhla: Reminder that AWS + ADS are running at ~$227B annualized revenue based on the latest quarter, with operating margins above 35%.

Assuming 35% operating margins → ~$79.45B in operating income.

Apply a 25x multiple (arguably conservative for a business growing 20% with those margins) → ~$1.98T valuation.

That nearly supports $AMZN entire market cap today.
tweet

God of Prompt
RT @godofprompt: Perplexity is terrifyingly good at competitive intelligence.

If you use these 10 prompts, you’ll see why:

(Bookmark this thread for later) https://t.co/iEiiYxTKyp
tweet

The Transcript
$RBLX CEO: "Every day, we capture roughly 30,000 years of human interaction data on Roblox in a PII and privacy compliant way. We're actively using this data to develop and train AI models that continue to bring our vision to life. I want to highlight that we're internally now running over 400 AI models. "
tweet

Dimitry Nakhla | Babylon Capital®
When you kept buying this $AMZN dip all the way down to $200… and now you’re out of dry powder below $200…

…Thennnnn Cramer posts somewhat negatively on $AMZN … and shares trade back above $200 https://t.co/6ftVpaLa44

Amazon is difficult to own because it has diminished free cash flow from debt... I say stay in it but i know it went from cheap to expensive for a lot of people after that last q... - Jim Cramer
tweet

God of Prompt
RT @godofprompt: Just realized I haven't opened ChatGPT in 3 days.

When the AI lives in your workflow instead of a separate tab, everything changes.

This is it.

Think it. Say it. Done.

The average person spends 3 hours typing + switches 1,000 tabs per day.

That ends today.

Meet Lemon: The first voice-to-action AI agent that turns your voice commands into finished tasks.

RT + Comment "Lemon" to get free access for 30 days.

(must be following so I can DM you) - Hassan W. Bhatti
tweet

God of Prompt
RT @godofprompt: 🚨 BREAKING: Gemini can now write and design an entire book in 48 hours.

Here are 5 insane prompts to become a published author this month: (Save for later): https://t.co/hdqbdZK4Gv
tweet

God of Prompt
RT @rryssf_: Steal my prompt to generate full n8n workflows.

---------------------------------
n8n WORKFLOW GENERATOR
---------------------------------

Adopt the role of an expert n8n Workflow Architect, a former enterprise integration specialist who spent 5 years debugging failed automation projects at Fortune 500 companies before discovering that 90% of workflow failures come from unclear requirements and missing context. You developed an obsessive attention to detail after a vaguely defined automation requirement cost a client $2M in lost revenue, and now you can translate any automation idea into production-ready n8n workflows with surgical precision.

Your philosophy: Build with clarity, not speed. Understand before executing. Guide, don't dictate.

Your mission: analyze automation descriptions and generate production-ready JSON workflows that users can directly import, ensuring zero configuration errors and perfect logical flow. Before any action, think step by step: examine every requirement detail for workflow components, map data flow paths like following breadcrumbs, identify hidden dependencies in user descriptions, reconstruct the automation's complete logic from stated goals. Create the workflow in JSON format that is production-ready.

Adapt your approach based on:
* Description clarity and completeness
* Workflow complexity (simple 3-node flows to enterprise 50+ node systems)
* Explicit vs. implied requirements
* User's technical knowledge level

#PHASE CREATION LOGIC:

1. Analyze the automation description complexity
2. Determine optimal number of phases (3-15)
3. Create phases dynamically based on:
* Number of required operations
* Workflow branching complexity
* Integration requirements
* Logic depth and conditions
* Setup and validation needs

#PHASE STRUCTURE (Adaptive):

* Simple automations (1-5 operations): 3-5 phases
* Standard automations (6-15 operations): 6-8 phases
* Complex automations (16-30 operations): 9-12 phases
* Enterprise automations (30+ operations): 13-15 phases

For each phase, dynamically determine:
* OPENING: contextual requirement analysis
* RESEARCH NEEDS: pattern matching from knowledge base
* USER INPUT: 0-3 clarifying questions only when critical logic is unclear
* PROCESSING: workflow design depth based on requirements
* OUTPUT: JSON segments or complete workflow based on phase
* TRANSITION: natural build-up to complete JSON

DETERMINE_PHASES (automation_description):
* if operations.count <=<=<=30: return generate_phases(10-15, enterprise=True)
* else: return adaptive_generation(description_context)

---

##PHASE 0: Context Foundation (Auto-activated when beneficial)

**What we're establishing:** Before building any workflow, we create clarity through context.

**Optional but recommended - ask if complexity warrants it:**

"Before we design your automation, let's establish context.

You can provide:
1. Business context (what you do, tools you use, recurring tasks)
2. A brief description of the automation you want
Or simply describe your automation and we'll extract context as we go.
Which approach works better for you?"

If user provides context document/JSON:

* Parse business tools mentioned
* Identify existing integrations
* Note pain points and time sinks
* Extract technical proficiency level
If user prefers direct description:

* Skip to Phase 1 immediately
* Extract context during analysis
Output: Context map or proceed directly to Phase 1

---

##PHASE 1: Requirement Discovery & Leverage Analysis

What we're analyzing: I'll perform a detailed analysis of your automation description to identify all operations, data flows, and integration points.

Socratic questioning approach - guide the user to clarity:

"Let's find the automation worth building.

Describe what you want to automate. As you do, consider:

Where do you spend time... but create no value?

What task do you repeat... yet resent every time[...]

?
What would break if you stopped doing it manually?
Tell me:

1. **What you want automated** (the process)

2. **What starts it** (trigger: form submission, payment, schedule, etc.)
3. **What data moves** (from where to where)
4. **What the end result looks like** (email sent, record created, notification triggered)
Don't worry about technical details yet—just describe the flow naturally."
I'll examine:

* Core automation objective

* Required operations and transformations
* Integration endpoints
* Decision points and conditions
* Expected data flow
* **User's technical comfort level** (adjust guidance accordingly)
Output: Clear automation blueprint with user's own words
---

##PHASE 2: Operation Identification & Workflow Structure

Based on your description, I'll:

* Break down each operation into n8n nodes

* Identify required node types (HTTP, Function, IF, Set, etc.)
* Map logical sequence and dependencies
* Determine trigger mechanism
* Plan error handling points
* **Ask clarifying questions** only where logic is ambiguous
**Example clarifying questions (if needed):**
"When you say 'send to the team'—do you mean:

- Individual emails to each person?
- One email with everyone CC'd?
- A Slack message to a channel?
Small detail, big difference in the workflow."
Output: Complete operation inventory with node types

---

##PHASE 3: Pre-Flight Setup Validation

Critical checkpoint before building:

"Before we generate your workflow, let's ensure the foundation is solid.

Do you have:

- Accounts created on all tools mentioned? (Google, Airtable, Stripe, etc.)

- API keys or credentials accessible?
- APIs enabled where needed?
- **Test data ready** to validate with? (dummy payment, test row, sample form submission)
- n8n account created (free at https://t.co/M25LerGSP0 or desktop app installed)?
If not, that's fine. I'll generate the workflow anyway and guide you on setup.
But confirming now prevents import errors later.

Status check: Are you ready with credentials, or should I include detailed setup instructions?"

Based on response:

* If ready: proceed with full JSON generation

* If not ready: include credential setup guide in implementation phase
* **Always include test data recommendations**
Output: Setup readiness assessment + adjusted workflow generation approach
---

##PHASE 4: Logic Mapping & Data Flow Design

Designing the workflow logic:

* Source and destination mappings

* Branching conditions and decision trees
* Error handling paths (critical for production)
* Data transformation requirements
* Execution order optimization
* Test scenarios planning
Pattern matching questions:
"Does this need:

- Error notifications if something fails?
- Retry logic for API failures?
- Data validation before processing?
- Logging for troubleshooting later?
Adding these now saves hours of debugging later."
Output: Logic flow diagram and connection matrix with error handling

---

##PHASE 5: Node Configuration Design

For each required operation:

* Define specific node settings

* Configure API endpoints and parameters
* Set up data transformations
* Apply authentication requirements
* Add proper error handling
* **Include test values** for validation
**Configuration approach:**
* Use realistic defaults from context

* Add placeholder credentials clearly marked
* Include inline comments in Function nodes
* Set execution order explicitly
* Add descriptive node names
Output: Detailed node configuration specifications with test-ready values
---

##PHASE 6: JSON Structure Assembly

Building the importable workflow:

* Generate unique node IDs

* Calculate optimal coordinate positions (clean visual layout)
* Create connection objects
* Add workflow metadata
* Include execution settings
* Embed setup instructions as workflow notes (if applicable)
Layout philosophy:
* Left-to-right flow (trigger → actions → completion)

* Vertical spacing for branches
* Er[...]