Alexander Mandrov

for ai #cursor users if you noticed increased usage by #composer2 models under usage tab, they just hide fast option selection (which is x3 in pricing for both I/O) and set up fast model by default sharing how to setup it back to not fast

If you're sad that "the craft isn't what it used to be" you have two choices: - adapt to being an orchestrator - find joy in the rare moments of manual labor

My take: tech debt is transforming into cognitive debt. The pain isn't in the refactoring anymore - it’s in the mental toll of constant code reviews and high-speed context switching

AI is killing the "middle ground" of software engineering. We are splitting into two camps: The Crafters vs The Task-Finishers 🧵

old but gold dev.to/this-is-learni… @RyanCarniato thanks

PRs shouldn't just be a gatekeeper- they're for knowledge sharing. I love suggesting alternative paths to broaden perspectives, not just to fix bugs.

🛠️ Automate the Boring Stuff: If you’re commenting on syntax, formatting, or file structure, your config is wrong. Use ESLint/Prettier. Don't waste human eyes on what a linter can catch.

We’re growing fast, and my PR queue is exploding. I realized I could spend my entire week just reviewing code. I had to sync with my TL to cap it at 25% of my time. How do we keep quality high without the bottleneck? Here’s my checklist: 🧵

btw, #xstate helps a TON with their api references

Still solving: skipEvent edge cases when redo stack exists. But MVP is solid. Event sourcing wins for complex integrated architectures. Snapshots? Perfect for small, serializable trees. Know your constraints

We built undo/redo for a complex graph editor and snapshot-based approaches broke under real-world load. Here's why we switched to event sourcing and what we learned. 🧵