Kitze Ristovski
where else to find them
website:https://kitze.io
github:kitze
bluesky:thekitze.bsky.social
x:thekitze
youtube:@kitze
youtube:@kitzeproductivity
youtube:@kitzemusic
youtube:@kitzecast
devto:kitze
what they talk about
all 6 in the filters
where they keep going back
- React Day Berlin2 editions2017–2018
- reactjsday2 editions2017–2018
all 11 in the filters
on a stage with
- Adrian Hajdinonce
- Alem Tuzlakonce
- Johannes Goslaronce
all 5 in the filters
who talks about the same things
- Cory House16 talks
- Adam Klein14 talks
- Michel Weststrate30 talks
- Glenn Reyes17 talks
- Sara Vieira38 talks
- Gerard Sans30 talks
| title | conference | date |
|---|---|---|
| AI Unconference | React Summit 2026 | 2026-06-12 |
-- no description -- | ||
| From Vibe Coding to Vibe Engineering | React Summit 2026 | 2026-06-12 |
Web development has always moved in cycles of hype, from frameworks to tooling. With the rise of large language models, we're entering a new era of 'vibe… | ||
| Navigating the Hype Driven Frontend Development World | React Live 2019 | 2019-09-13 |
Claims that hooks boost team productivity but hooks are not a global state solution and require memoization to avoid excess renders; compares Redux (verbose)… | ||
| Navigating the Hype-Driven Frontend Development World Without Going Insane | React Day Berlin 2018 | 2018-11-30 |
Concrete rules and real tradeoffs: when to adopt hooks or GraphQL, why Gatsby blocked an update and React Static solved it, styled‑components versus emotion… | ||
| Navigating the hype-driven world of frontend development without going crazy - 'Kitze' Ristovski | ReactJS Day 2018 | 2018-10-05 |
Argues that FOMO comes from wrong priorities and gives concrete rules: recognize breaking points before migrating, sleep on new libraries, and prefer pragmatic… | ||
| Navigating the hype-driven frontend development world without going insane | React Alicante 2018 | 2018-09-13 |
Argues that FOMO comes from impulse-driven upgrades and social media noise and shows concrete decisions: a 14‑page remove node modules RFC as comic evidence… | ||
| React State Management In a GraphQL Era | React Amsterdam 2018 | 2018-04-12 |
Argues that GraphQL plus a client like Apollo removes most data-state pain — fetching, caching and invalidation — and that teams often drop 5,000 lines removed… | ||
| The exciting future of React | JSHeroes 2018 | 2018-04-10 |
React 16 actually rewrites the core as React Fiber core rewrite and enables concrete features: fragments replace aux so components return multiple siblings… | ||
| State Management in a GraphQL Era | ReactFest 2018 | 2018-03-08 |
We're going to start with exploring the evolution of making a SPA.! Then we're going to dive into the problem of how fetching, caching, and reading data really… | ||
| The exciting future of React | Frontend Developer Love 2018 | 2018-02-15 |
Covers concrete React 16 changes with live demos: how fragments without extra wrapper lets components return multiple elements, how portals into another window… | ||
| React state management in a GraphQL era | AgentConf 2018 | 2018-01-25 |
Claims that GraphQL pushes most server data problems to the client and makes global state libraries unnecessary in many cases, with concrete stacks: Apollo +… | ||
| React State Management in a GraphQL Era | React Day Berlin 2017 | 2017-12-02 |
Compares concrete stacks: GraphQL with Apollo replacing most data plumbing, Redux or MobX only for specific needs, and Next.js for easy SSR; claims a team cuts… | ||
| State management in a GraphQL era | dotJS 2017 | 2017-12-01 |
Claim: with GraphQL (Apollo) the data problem largely disappears and in about 90% of cases Redux is unnecessary. Demonstrations compare a verbose Redux fetch… | ||
| React state management in a GraphQL era | ReactJS Day 2017 | 2017-10-06 |
Argues that GraphQL with Apollo often replaces external stores for server data while UI still uses local setState for ephemeral state; shows concrete patterns… | ||
| nothing matches | ||