We just crossed 300 followers. Let me reintroduce myself. I’m Fiyin, a Frontend Engineer obsessed with frontend design, performance, and systems. If you are a frontend engineer and you're serious about growing in your career, thinking like an engineer and not just writing code,

Planning to use @xyflowdev for mindmap generation on Summara to allow users to generate mindmaps from videos. Let's see how it goes :)

Good luck @jogicodes ! Not like your gonna need it :)

Quick tips to keep tests healthy: Delete outdated ones (UI changes a lot, tests have shelf life) Fix or kill flaky tests (bad tests hurt more than none) Use user-like queries (getByRole, getByText) → they survive refactors Start small, focus on confidence, not coverage %.

Tests feel slow and awkward at first (first 10–20 feel painful Most devs who start say, "I wish I'd begun earlier."

Smart way to start (don't rewrite everything): Write tests for new code you're adding Prioritize what breaks trust: login, payments, forms, core flows When you fix a bug, first write a failing test that would've caught it, then fix, never regress Ask: "If users can't do X, is

Why test at all if your app "works" without it? Early on: manual clicks are fast enough. But later on bigger team, refactors, and production bugs make you fear. Good tests bring confidence to change code quickly and catch regressions before users do. Long-term velocity >

The golden rule in modern React testing (especially RTL): Test what the user sees and does, not how your code works inside. Click like a user → modal opens? See the right text/image? Form submits correctly? Avoid: "state equals X" or "this function was called with Y". Focus

Just finished a @FrontendMasters section on React by @holtbt, testing with Vitest + React Testing Library (RTL). If you've been shipping React apps without tests for years (like most of us have), here's why it's worth adding now and how to think about it the right way. 🧵

If you want to understand React forms completely This thread shares the 2 types every dev must know in 2026:

A quick read.

Follow @OsokoyaF for more practical React threads.

Rule of thumb in 2026: → Quick form? → Uncontrolled → Anything with validation, formatting, or logic? → Controlled (or React Hook Form) Most production apps now default to controlled.

Example (uncontrolled)

Example (Controlled)

Controlled forms (React state is the source of truth). You give the input value={state} + onChange. Every keystroke updates React → you get instant validation, formatting, and one field affecting another.

Uncontrolled forms (The browser DOM is the source of truth) No state. No onChange. Just a ref. You read the value only when you need it (usually on submit). Fewer re-renders. Less code. Perfect for file uploads or super simple forms.

If you want to understand React forms completely This thread shares the 2 types every dev must know in 2026:

If you want to Understand Error Boundaries in React This thread shares 6 notes on it: 🧵

If you want to Understand Error Boundaries in React This thread shares 6 notes on it: 🧵

Great read for anyone interested in TanStack libraries. Thanks for the shoutout 🙏