---
title: "skzeeshan1992 (@izsk) | Hashnode"
description: "Bridging IT operations and frontend architecture through performance and system design. Read the latest articles by skzeeshan1992 on Hashnode."
url: "https://hashnode.com/@izsk"
---

@izsk

# skzeeshan1992

@izsk · Montreal, Canada · Joined April 2026

Bridging IT operations and frontend architecture through performance and system design.

### [FlashList vs FlatList: Stop Shipping FlatList for Real Feeds](https://izsk.hashnode.dev/flashlist-vs-flatlist-stop-shipping-flatlist-for-real-feeds?utm_source=hashnode&utm_medium=feed)

How recycling beats windowing in React Native, what breaks when you migrate, and the cases where FlatList is still the right call.

18 min read · [izsk.hashnode.dev](https://izsk.hashnode.dev/flashlist-vs-flatlist-stop-shipping-flatlist-for-real-feeds?utm_source=hashnode&utm_medium=feed)

[6d ago](https://hashnode.com/posts/flashlist-vs-flatlist-stop-shipping-flatlist-for-real-feeds/6af1f894518b076ab673fce7)

### [Start With a Monorepo: Small Teams Lose Weeks to Polyrepo Overhead](https://izsk.hashnode.dev/start-with-a-monorepo-small-teams-lose-weeks-to-polyrepo-overhead?utm_source=hashnode&utm_medium=feed)

A strong opinion on monorepo vs polyrepo for teams under 15 engineers, with a pnpm and Turborepo setup you can copy today.

17 min read · [izsk.hashnode.dev](https://izsk.hashnode.dev/start-with-a-monorepo-small-teams-lose-weeks-to-polyrepo-overhead?utm_source=hashnode&utm_medium=feed)

[Nov 2](https://hashnode.com/posts/start-with-a-monorepo-small-teams-lose-weeks-to-polyrepo-overhead/6ae8c3fd77447aebc0cc061c)

### [Server State vs Real-Time State: Stop Putting Both in One Store](https://izsk.hashnode.dev/server-state-vs-real-time-state-stop-putting-both-in-one-store?utm_source=hashnode&utm_medium=feed)

How I split TanStack Query and Zustand in a Socket.IO chat app, and why the cache bugs and ghost typing indicators stopped showing up.

18 min read · [izsk.hashnode.dev](https://izsk.hashnode.dev/server-state-vs-real-time-state-stop-putting-both-in-one-store?utm_source=hashnode&utm_medium=feed)

[Oct 19](https://hashnode.com/posts/server-state-vs-real-time-state-stop-putting-both-in-one-store/6ad64798548326417c19a7f6)

### [SSE vs WebSockets vs Webhooks: Stop Reaching for WebSockets First](https://izsk.hashnode.dev/sse-vs-websockets-vs-webhooks-stop-reaching-for-websockets-first?utm_source=hashnode&utm_medium=feed)

A practical guide to server-sent events, WebSockets and webhooks, when each one fits, and what the industry actually ships in production.

19 min read · [izsk.hashnode.dev](https://izsk.hashnode.dev/sse-vs-websockets-vs-webhooks-stop-reaching-for-websockets-first?utm_source=hashnode&utm_medium=feed)

[Oct 12](https://hashnode.com/posts/sse-vs-websockets-vs-webhooks-stop-reaching-for-websockets-first/6acd038f925af54ee7172f86)

### [Code Splitting in React: Route-Level vs Component-Level and What Actually Matters](https://izsk.hashnode.dev/code-splitting-in-react-route-level-vs-component-level-and-what-actually-matters?utm_source=hashnode&utm_medium=feed)

Most teams split everything or nothing. Both are wrong.

12 min read · [izsk.hashnode.dev](https://izsk.hashnode.dev/code-splitting-in-react-route-level-vs-component-level-and-what-actually-matters?utm_source=hashnode&utm_medium=feed)

[Aug 31](https://hashnode.com/posts/code-splitting-in-react-route-level-vs-component-level-and-what-actually-matters/6a9598c4a0c0d3fa8abac603)