---
title: "BOBBY KUMAR (@bobby-kumar) | Hashnode"
description: "Software engineer building scalable systems, exploring AI, and learning in public. Read the latest articles by BOBBY KUMAR on Hashnode."
url: "https://hashnode.com/@bobby-kumar"
---

@bobby-kumar

# BOBBY KUMAR

@bobby-kumar · Delhi, India · Joined August 2026

Software engineer building scalable systems, exploring AI, and learning in public.

### [When Personalization Meets the Edge](https://the-engineers-notebook.hashnode.dev/when-personalization-meets-the-edge?utm_source=hashnode&utm_medium=feed)

Personalization changes how a request is handled. Context must be identified, the right experience must be selected, and caching must ensure that responses are reused safely. The challenge isn't just delivering personalized content - it's deciding where those decisions happen and how the right experience can be delivered efficiently at the edge.

9 min read · [the-engineers-notebook.hashnode.dev](https://the-engineers-notebook.hashnode.dev/when-personalization-meets-the-edge?utm_source=hashnode&utm_medium=feed)

[Sep 12](https://hashnode.com/posts/when-personalization-meets-the-edge/6aa59494dbbc0aed06943329)

### [Caching: It Isn't Just a Performance Problem](https://the-engineers-notebook.hashnode.dev/caching-it-isn-t-just-a-performance-problem?utm_source=hashnode&utm_medium=feed)

Caching can make applications faster, but it also changes how systems handle freshness, correctness, personalization, invalidation, and failure. The real challenge isn't caching - it's deciding what can be safely reused, by whom, and for how long.

10 min read · [the-engineers-notebook.hashnode.dev](https://the-engineers-notebook.hashnode.dev/caching-it-isn-t-just-a-performance-problem?utm_source=hashnode&utm_medium=feed)

[Sep 5](https://hashnode.com/posts/caching-it-isn-t-just-a-performance-problem/6a9c4d05eea212cb86b6976d)

### [The Journey of a Request in a Next.js Application](https://the-engineers-notebook.hashnode.dev/the-journey-of-a-request-in-a-next-js-application?utm_source=hashnode&utm_medium=feed)

Every page is the result of a request moving through multiple systems. From the browser and edge to middleware, data sources, rendering, and back again. The request has already travelled through an entire system before a page reaches the browser.

7 min read · [the-engineers-notebook.hashnode.dev](https://the-engineers-notebook.hashnode.dev/the-journey-of-a-request-in-a-next-js-application?utm_source=hashnode&utm_medium=feed)

[Aug 29](https://hashnode.com/posts/the-journey-of-a-request-in-a-next-js-application/6a93098979676b78fc4d5d3b)

### [From Components to Systems: Why Frontend Engineers Need System Design](https://the-engineers-notebook.hashnode.dev/from-components-to-systems-why-frontend-engineers-need-system-design?utm_source=hashnode&utm_medium=feed)

As frontend applications become more distributed, data-driven, personalized, and performance-sensitive, frontend engineers are no longer just designing components - they're designing systems.

7 min read · [the-engineers-notebook.hashnode.dev](https://the-engineers-notebook.hashnode.dev/from-components-to-systems-why-frontend-engineers-need-system-design?utm_source=hashnode&utm_medium=feed)

[Aug 22](https://hashnode.com/posts/from-components-to-systems-why-frontend-engineers-need-system-design/6a89d89ee4925841657b4dbb)