---
title: "Ganesh Rama Hegde (@hegde10122) | Hashnode"
description: "Ganesh Rama Hegde (@hegde10122) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@hegde10122"
---

@hegde10122

# Ganesh Rama Hegde

@hegde10122 · Mumbai,India · Joined July 2024

[Website](https://designpatterns.hashnode.dev/)

### [The Inbox Operations Agent](https://ganeshhegde.hashnode.dev/the-inbox-operations-agent?utm_source=hashnode&utm_medium=feed)

Chapter 1

55 min read · [ganeshhegde.hashnode.dev](https://ganeshhegde.hashnode.dev/the-inbox-operations-agent?utm_source=hashnode&utm_medium=feed)

[Aug 15](https://hashnode.com/posts/the-inbox-operations-agent/6a805487472146c4e97cdd77)

### [Chapter 1 : UseCase01 - Coroutine Builders and Execution Semantics](https://kotlindeepdive.hashnode.dev/chapter-1-usecase01-coroutine-builders-and-execution-semantics?utm_source=hashnode&utm_medium=feed)

Mental Model: What Is a Coroutine? A coroutine is a suspendable computation, represented as a state machine, executed under a Job, scheduled by a dispatcher and resumed via a continuation. It is not a

13 min read · [kotlindeepdive.hashnode.dev](https://kotlindeepdive.hashnode.dev/chapter-1-usecase01-coroutine-builders-and-execution-semantics?utm_source=hashnode&utm_medium=feed)

[Feb 23](https://hashnode.com/posts/chapter-1-usecase01-coroutine-builders-and-execution-semantics/699bdee5a32af19cb6fcc92b)

### [Chapter 30 : UseCase27 - Flow Cancellation & Cooperative Cancellation](https://kotlinflow.hashnode.dev/chapter-30-usecase27-flow-cancellation-cooperative-cancellation?utm_source=hashnode&utm_medium=feed)

Flow cancellation is not an optional feature. It is a core part of how coroutines are designed to behave. When a collector stops collecting, the entire upstream flow is cancelled automatically. This i

6 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-30-usecase27-flow-cancellation-cooperative-cancellation?utm_source=hashnode&utm_medium=feed)

[Feb 21](https://hashnode.com/posts/chapter-30-usecase27-flow-cancellation-cooperative-cancellation/6999ddbd1ea55229dbb50438)

### [Chapter 29 : UseCase26 - Channels and Flow Bridge](https://kotlinflow.hashnode.dev/chapter-29-usecase26-channels-and-flow-bridge?utm_source=hashnode&utm_medium=feed)

Now we do one level below Flow. Flow is built on coroutines.Coroutines are built on channels. Here we convert channel to Flow and build Flow using channelFlow. We also understand producer-consumer in

4 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-29-usecase26-channels-and-flow-bridge?utm_source=hashnode&utm_medium=feed)

[Feb 21](https://hashnode.com/posts/chapter-29-usecase26-channels-and-flow-bridge/6999a568649f185d24e98f46)

### [Chapter 28 : UseCase25 - Hot vs Cold Flow comparison](https://kotlinflow.hashnode.dev/chapter-28-usecase25-hot-vs-cold-flow-comparison?utm_source=hashnode&utm_medium=feed)

In this use case we will do an architectural level comparison of hot versus cold flow. CODE IMPLEMENTATION package org.kotlinflowlearner.stockflow.usecases.uc25 import kotlinx.coroutines.flow.\* impor

4 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-28-usecase25-hot-vs-cold-flow-comparison?utm_source=hashnode&utm_medium=feed)

[Feb 20](https://hashnode.com/posts/chapter-28-usecase25-hot-vs-cold-flow-comparison/699894629333793b50d6ea84)