Michael Solati @MichaelSolati

michaelsolati.com Oakland, CA Joined April 2008

Tweets

1K
Followers

667
Following

147
Likes

6K

Michael Solati @MichaelSolati

6 months ago

UX Tip: Kill the loading spinner. 💀 Research takes time. Waiting sux. I used Server-Sent Events (SSE) to stream the agent's actions. The user sees: "Scanning wiki..." -> "Reading blog..." -> "Generating villain..." It makes the wait feel like part of the experience.

0 0 0 32 0

View Details

Michael Solati @MichaelSolati

6 months ago

To stop the AI from generating a "wall of text," I enforce a strict JSON schema. This acts as a contract. The AI must return structured objects for NPCs, Locations, and Plot Hooks. No more rambling. Just usable data.

1 0 0 38 0

View Details

Michael Solati @MichaelSolati

6 months ago

I got tired of AI generating the same "twisted trees" and "whispering winds" for D&D campaigns. Generic hallucinations are boring. So I built an agent that turns the entire internet into a procedurally generated library. Here is the "Research-then-Generate" workflow 🧵👇

1 0 0 48 0

View Details

Michael Solati @MichaelSolati

6 months ago

Stop guessing the output of async code. If you found this breakdown helpful: 1. Follow me Michael Solati for more deep dives into JS internals. 2. Check out the full visual guide here: dev.to/michaelsolati/…...

0 0 0 26 0

View Details

Michael Solati @MichaelSolati

6 months ago

⚡ TL;DR Cheat Sheet * Synchronous: Runs first. * Microtasks (Promises): Run immediately after the stack clears. Exhaustive processing. * Rendering: Happens after Microtasks, before Macrotasks. * Macrotasks (Timers): Run only when everything else is quiet.

1 0 0 24 0

View Details

Michael Solati @MichaelSolati

6 months ago

I love digging into the "weird" parts of JavaScript. Here is the classic "Predict the Output" game that trips up even Senior Developers during interviews. What prints first? The Timeout (0ms) or the Promise? 🧵 Let's visualize the Event Loop. 👇

1 0 0 30 0

View Details

Michael Solati @MichaelSolati

7 months ago

Read the full, in-depth blog post here: dev.to/michaelsolati/…

0 0 0 25 0

View Details

Michael Solati @MichaelSolati

7 months ago

tl;dr: The 2025 Reality * Enterprise: LeetCode is alive (Anti-Cheat Mode). * Startups: Vibe Coding is here (Speed Mode). * The Risk: "Bring Your Own AI" creates economic inequality. * The Fix: Be bilingual. Audit AI output with strong fundamentals.

1 0 1 33 0

View Details

Michael Solati @MichaelSolati

7 months ago

I interviewed with Big Tech and Startups in 2025. The result? A widening gap that is breaking the hiring process. We are moving from "Meritocracy" to "Pay-to-Win." Here is the reality of LeetCode vs. Vibe Coding (and why it matters). 🧵

1 0 0 41 0

View Details

Michael Solati @MichaelSolati

7 months ago

Follow me for more honest takes on the engineering industry. And read my full breakdown here: dev.to/michaelsolati/…

0 0 0 22 0

View Details

Michael Solati @MichaelSolati

7 months ago

TL;DR - The market isn't just saturated; it's compressed. - Layoffs are funding GPU purchases ($170B+ shift). - The "How" (coding) is commoditized. - The "Why" (Engineering & Verification) is the gold standard.

1 0 0 21 0

View Details

Michael Solati @MichaelSolati

7 months ago

The 2025 tech market feels just like the 2015 bootcamp boom. But if you look at the data, it's actually much worse. We aren't just facing saturation. We are facing "Vertical Compression." Here is the reality of the market that no one is talking about. (Thread below 🧵👇)