Analyst Uttam

225 posts

Analyst Uttam

Analyst Uttam

@analystuttam

I make analytics simple. SQL • Python • Power BI • AI| ✉️: [email protected]

India Katılım Ocak 2025
24 Takip Edilen27 Takipçiler
Analyst Uttam
Analyst Uttam@analystuttam·
Sam Altman: 'No jobs apocalypse' Reality: Amazon cut 16k corporate roles in 2026 citing AI efficiency. HSBC planning up to 20k AI-driven cuts. 55k+ AI-linked layoffs in 2025 alone.He was right on tech speed, wrong on timing. Entry-level white-collar is getting squeezed first.Adapters win. Others adapt or lag.
English
0
0
2
331
unusual_whales
unusual_whales@unusual_whales·
OpenAI's Altman says AI unlikely to lead to 'jobs apocalypse'
English
199
36
675
91.9K
World of Statistics
World of Statistics@stats_feed·
If all humans suddenly lost the ability to lie, what industry would collapse first?
English
6K
445
6.8K
1.8M
Analyst Uttam
Analyst Uttam@analystuttam·
Classic adoption vs. impact gap. 95% engineer usage + 70% AI code is impressive, but consumer features are the real scorecard. Token spend exploded faster than value — enterprises are now shifting from 'how much AI' to 'what ROI?' Next phase: targeted agents over blanket coding.
English
0
0
0
8
Polymarket
Polymarket@Polymarket·
JUST IN: Uber’s COO says heavy AI spending is getting harder to justify, as higher token usage fails to show a clear payoff in consumer features.
English
228
471
4.9K
477.6K
Analyst Uttam
Analyst Uttam@analystuttam·
@AlexHormozi True. Regret from inaction hits harder than any failure. The only real loss is never starting.
English
0
0
0
129
Alex Hormozi
Alex Hormozi@AlexHormozi·
I'd rather be a failure than a coward.
English
321
971
6.4K
107K
Analyst Uttam
Analyst Uttam@analystuttam·
What's one AI tool you actually use daily that isn't ChatGPT or Copilot? Genuinely curious what's getting real adoption.
English
0
0
0
12
Analyst Uttam
Analyst Uttam@analystuttam·
Most data scientists are solving the wrong problem. They optimize models. The company needed a decision. There's a graveyard of 94% accuracy models that never shipped, never influenced strategy, never touched revenue. Technical correctness is not business value. The best DS hire I ever saw had mediocre notebooks and terrifying business instincts. She retired three dashboards, killed two roadmap items, and saved $2M in misdirected engineering spend. In 90 days. The skill gap in data science isn't technical. It's judgment.
English
0
0
0
9
Analyst Uttam
Analyst Uttam@analystuttam·
6/ The line that reframes the whole category: "Memory is a side effect. Context is infrastructure." I tested Unabyss before its Product Hunt launch. Wrote up the full architecture breakdown, what actually works, and where it's still early. Full piece:@analystuttam/your-ai-tools-have-no-memory-of-you-this-tool-finally-fixes-that-300270879b32" target="_blank" rel="nofollow noopener">medium.com/@analystuttam/…
English
0
1
3
93
Analyst Uttam
Analyst Uttam@analystuttam·
5/ There's also a security argument most people ignore. Standard integrations give AI agents live access to your inbox, drive, and repos. That's 50 live credential exposures if you run 5 agents across 10 apps. A context vault changes the architecture: agents read from a curated file. Not your live accounts.
English
1
0
2
21
Analyst Uttam
Analyst Uttam@analystuttam·
Most people have the AI context problem completely backwards. They say "AI has bad memory." That's technically true. But strategically wrong. Here's the real diagnosis — and why it matters for how you build your stack. 🧵
English
1
0
3
21
Analyst Uttam
Analyst Uttam@analystuttam·
Most AI startups aren't building products. They're building demos that require a human to fix the output before anyone sees it. That's not a product. That's a workflow with a liability at the center.
English
0
0
0
11
Analyst Uttam
Analyst Uttam@analystuttam·
🚀Build all-in-one AI workspace like @genspark_ai (the Claude-powered one Kay Zhu talked about) — high-level steps: 1️⃣Foundation: Integrate Claude API (Anthropic) as the reasoning core. Add a model router (LiteLLM) for Claude + GPT/Gemini/etc. 2️⃣Super Agent Orchestrator: Build a planner + executor with LangGraph or CrewAI. Use Mixture-of-Agents pattern: break tasks → route to specialist agents. 3️⃣Tools Layer (the magic): 50+ tools — web search, code sandbox, browser automation, slide/doc gen (pptx libs), image/video APIs, file handling. 4️⃣Modern UI: Next.js + Tailwind. Clean sidebar (projects/drive), big prompt bar ("Ask anything, create anything"), live previews for slides/docs/code. 5️⃣Memory & State: Vector DB (Pinecone) for RAG + Postgres for projects/history. Give agents long-term memory. 6️⃣Content Engine: Agents that don’t just chat — they execute and output editable artifacts (slides, sheets, sites, apps). 7️⃣Ship it: Add auth, deploy (Vercel + FastAPI backend). Start tiny → iterate fast. The real edge? Team execution, not just tech. Anyone can prompt. Great teams ship autonomous workflows that finish the work. Start with #1-3 this weekend. What part are you building first? 👇
English
0
0
1
94
Claude
Claude@claudeai·
Kay Zhu is the co-founder and CTO of @genspark_ai, the all-in-one AI workspace built on Claude. In a market moving this fast, where anyone can build, he thinks the team is what makes the difference:
English
194
146
2.1K
299.4K
Analyst Uttam
Analyst Uttam@analystuttam·
Most data scientists are still cleaning CSVs. The engineers who will replace them are writing natural language queries against live data pipelines. The job didn't disappear. It just moved one abstraction layer up.
English
0
0
0
6
Analyst Uttam
Analyst Uttam@analystuttam·
x.com/runwayml/statu… Runway just quietly redefined the reshoots economy. Aleph 2.0 doesn't generate video. It edits it — frame-consistent, multi-shot, up to 30 seconds at 1080p. Swap the outfit. Change the location. Recast the character. No crew. No location fee. No continuity supervisor. The first wave of AI video was about creation. The second wave is about revision. That's where production budgets actually live.
English
0
0
0
82
Analyst Uttam
Analyst Uttam@analystuttam·
The best data scientists today aren't writing more code. They're writing better instructions. Instruction tuning didn't just change how models behave. It quietly reassigned the highest-leverage skill in data science from syntax to specification. The bottleneck was never compute. It was always clarity of thought.
English
0
0
0
9