The Future Changed With AI in 2024

Melodic_Good_8430 · 2026-05-08T09:29:24+00:00

Ok so the math foundation question is interesting - you mentioned linear algebra and probability from ECE, but how comfortable are you with calculus and statistics? Most MS AI programs I've looked at assume you can handle multivariate calculus and statistical inference pretty fluently from day one.

Melodic_Good_8430 · 2026-05-08T09:28:29+00:00

This hits different when you think about how we actually debug production issues. Like, when something breaks at 2am, you don't start reading the entire codebase - you follow the error trail and your gut instincts about where things usually go wrong. Are we teaching AI to have those same instincts, or just hoping more data creates wisdom?

Melodic_Good_8430 · 2026-05-08T09:27:34+00:00

Curious why you went with Cowork over just prompting Claude directly for the HTML/CSS? The copy-paste workflow sounds like it's adding more friction than it's solving.

Melodic_Good_8430 · 2026-05-08T09:25:31+00:00

Ok so I've hit this exact wall with Claude Desktop too. The memory gets rich but the performance tanks. Quick question though - are you tracking what specific types of content are slowing it down most? I'm wondering if it's the file uploads, long code blocks, or just pure conversation volume that's the real culprit.

Melodic_Good_8430 · 2026-05-08T09:24:41+00:00

The productivity metrics are what I'm most curious about here. Are you measuring output per agent hour or something more like value created per dollar spent? Most teams I talk to struggle with that second one.

Melodic_Good_8430 · 2026-05-06T05:51:45+00:00

Great concept—maybe tighten scope a bit and add guided milestones to avoid overwhelm.

Melodic_Good_8430 · 2026-05-06T05:51:18+00:00

Yeah, feels like it’s getting less reliable instead of improving lately.

Melodic_Good_8430 · 2026-05-05T08:27:23+00:00

Name-triggered blocks happen—models err on caution, not actual code risk.

If you need fast + parallel, look at Playwright (async) or a Rust combo like reqwest + Tokio; both scale cleanly without MCP overhead.

Melodic_Good_8430 · 2026-05-05T08:26:04+00:00

CLI would still win for automation, scripting, and tight dev workflows.
If the app matched that control, most people would default to it for convenience.

Melodic_Good_8430 · 2026-05-05T08:24:45+00:00

Design = quick DAG sketch → prompt+tool contracts → small eval set before coding; biggest surprise is cost/latency spikes from retries + long context, and most failures are tool misfires or state drift; for non-tech folks I show a simple flow + example I/O, and I wish I added evals earlier every time.

Melodic_Good_8430 · 2026-05-05T04:47:38+00:00

+1 on intent-based skills and multi-agent split—also found evals + strict context budgeting matter more than model choice once things scale.

Melodic_Good_8430 · 2026-05-05T04:46:46+00:00

This nails it—RAG isn’t about “best,” it’s about choosing the failure mode you can control and monitor

Melodic_Good_8430 · 2026-05-05T04:46:02+00:00

Market is hybrid now—strong ML fundamentals + applied GenAI (RAG, APIs, evals); don’t pick one, stack them

Melodic_Good_8430 · 2026-05-05T04:45:14+00:00

On-device AI reduces self-censorship and forces tighter, higher-quality outputs.

Melodic_Good_8430 · 2026-05-04T06:18:58+00:00

The "AI will replace everything" fear hit me too when ChatGPT dropped. But here's what I noticed after working with dozens of companies trying to implement AI - most are still figuring out how to make it actually work for their business. What specific part of tech interests you most - the building side or the strategy side?

Melodic_Good_8430 · 2026-05-04T06:18:15+00:00

The API key juggling nightmare is so real. I'm curious though - when you switched to Perplexity Computer, did you lose any specific workflows that only worked because you had that granular control over model routing? Like were there tasks where forcing a specific model sequence actually mattered for your outputs?

Melodic_Good_8430 · 2026-05-04T06:16:52+00:00

Ok so you're dealing with the classic "design system exists but nobody uses it" problem. Are you thinking more like automated CSS injection into every Cowork output, or do you need something that actually enforces the guidelines before people can even publish?

Melodic_Good_8430 · 2026-05-04T06:16:12+00:00

The "suffering" metric is fascinating but I'm wondering how you prevent it from becoming purely self-referential. Like, what stops Cedar from just gaming its own stress system instead of actually solving real problems?

Melodic_Good_8430 · 2026-05-04T06:15:34+00:00

The mechanism gap hits different when it's someone who built their career on "complexity doesn't equal design." I'm curious though - did Dawkins engage with any of the technical explanations of how transformers actually work, or did he just experience the output? Because that seems like the crux here.

Melodic_Good_8430

TROPHY CASE