--- title: "#usecase articles | Hashnode" description: "Explore 22 articles tagged #usecase on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/usecase" --- Tag # #usecase 22 posts · 0 followers [Sachin Adi](https://hashnode.com/@sachinadi424) · [Oct 16](https://hashnode.com/posts/the-architecture-of-collaboration-why-the-future-of-ai-belongs-to-multi-agent-systems/6ad186243bff18c1f9a35811) ### [The Architecture of Collaboration: Why the Future of AI Belongs to Multi-Agent Systems](https://ghatodghach.hashnode.dev/the-architecture-of-collaboration-why-the-future-of-ai-belongs-to-multi-agent-systems?utm_source=hashnode&utm_medium=feed) Imagine hiring a single brilliantly smart intern and asking them to handle product management, write frontend code, review security vulnerabilities, run QA tests, and publish product documentation—all 6 min read · [ghatodghach.hashnode.dev](https://ghatodghach.hashnode.dev/the-architecture-of-collaboration-why-the-future-of-ai-belongs-to-multi-agent-systems?utm_source=hashnode&utm_medium=feed) [Nikhil Mali](https://hashnode.com/@nikhilsdf) · [Apr 22](https://hashnode.com/posts/spread-vs-rest-operators-in-javascript/69e8d37a5d1c10710555cd05) ### [Spread vs Rest Operators in JavaScript](https://nm-javascript.hashnode.dev/spread-vs-rest-operators-in-javascript?utm_source=hashnode&utm_medium=feed) With real life use cases, interview questions and also common mistakes to avoid. 4 min read · [nm-javascript.hashnode.dev](https://nm-javascript.hashnode.dev/spread-vs-rest-operators-in-javascript?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Feb 19](https://hashnode.com/posts/chapter-26-usecase23-sharedflow-hot-streams/699757f940a5f60bf0153abf) ### [Chapter 26 : UseCase23 - SharedFlow (Hot Streams)](https://kotlinflow.hashnode.dev/chapter-26-usecase23-sharedflow-hot-streams?utm_source=hashnode&utm_medium=feed) Everything that we have seen until now was cold flows. Now we enter the world of "hot” flows. Cold flow means: Nothing runs until collected Each collector gets its own independent execution Flow re 4 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-26-usecase23-sharedflow-hot-streams?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Feb 1](https://hashnode.com/posts/chapter-18-usecase15-flatmaplatest/6992110959d0758c8426aba7) ### [Chapter 18 : UseCase15 - flatMapLatest](https://kotlinflow.hashnode.dev/chapter-18-usecase15-flatmaplatest?utm_source=hashnode&utm_medium=feed) In this chapter we will focus on automatic cancellation of previous work when new data arrives. Concept flatMapLatest works like this: Upstream emits a value. A new inner flow starts. If upstream e 4 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-18-usecase15-flatmaplatest?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Jan 31](https://hashnode.com/posts/chapter-17-usecase14-flatmapmerge/6990c9910f9fa9734c0bfb95) ### [Chapter 17 : UseCase14 - flatMapMerge](https://kotlinflow.hashnode.dev/chapter-17-usecase14-flatmapmerge?utm_source=hashnode&utm_medium=feed) In UC13 you used flatMapConcat, which processed each stock one after another. In UC14 we use flatMapMerge(). This allows multiple inner flows to run at the same time.Now we upgrade from sequential exp 5 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-17-usecase14-flatmapmerge?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Jan 27](https://hashnode.com/posts/chapter-13-usecase10-distinctuntilchanged/6990c7a84641c9876a17eeb4) ### [Chapter 13 : UseCase10 -distinctUntilChanged](https://kotlinflow.hashnode.dev/chapter-13-usecase10-distinctuntilchanged?utm_source=hashnode&utm_medium=feed) In real streams, values often repeat. But sometimes, we only care when the value actually changes. distinctUntilChanged() ensures that the same consecutive value is not emitted twice. It filters out d 2 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-13-usecase10-distinctuntilchanged?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Jan 18](https://hashnode.com/posts/chapter-4-usecase01-cold-flow-basics/6990c25bb5924a246553d6fe) ### [Chapter 4 : UseCase01 - Cold Flow Basics](https://kotlinflow.hashnode.dev/chapter-4-usecase01-cold-flow-basics?utm_source=hashnode&utm_medium=feed) Cold Flow : Understanding Laziness and Execution We now have a fully validated in-memory dataset: List We will now understand Kotlin Flow from first principles. In this chapter our focus will b 5 min read · [kotlinflow.hashnode.dev](https://kotlinflow.hashnode.dev/chapter-4-usecase01-cold-flow-basics?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Nov 12, 2025](https://hashnode.com/posts/chapter-26-testing-the-insert-and-delete-use-cases/6914ad0fdba6e4e0b9869f5b) ### [Chapter 26 - Testing the Insert and Delete Use Cases](https://androidavatar.hashnode.dev/chapter-26-testing-the-insert-and-delete-use-cases?utm_source=hashnode&utm_medium=feed) Since InsertArtUseCase and DeleteArtUseCase are pure domain logic, they’re easy to test — no Android dependencies, just Kotlin coroutines and a fake repository. Let’s write clear, minimal, and clean unit tests using JUnit + Kotlin coroutines test. We... 2 min read · [androidavatar.hashnode.dev](https://androidavatar.hashnode.dev/chapter-26-testing-the-insert-and-delete-use-cases?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Nov 9, 2025](https://hashnode.com/posts/chapter-20-coding-the-domain-layer-for-insertartusecase-and-deleteartusecase/6910cce11d9821de32226bef) ### [Chapter 20 - Coding the Domain layer for InsertArtUseCase and DeleteArtUseCase](https://androidavatar.hashnode.dev/chapter-20-coding-the-domain-layer-for-insertartusecase-and-deleteartusecase?utm_source=hashnode&utm_medium=feed) Let us update the ArtUseCases class. data class ArtUseCases( val getArtUseCase: GetArtUseCase, val searchImageUseCase: SearchImageUseCase, val insertArtUseCase: InsertArtUseCase, val deleteArtUseCase:DeleteArtUseCase ) We will now cod... 1 min read · [androidavatar.hashnode.dev](https://androidavatar.hashnode.dev/chapter-20-coding-the-domain-layer-for-insertartusecase-and-deleteartusecase?utm_source=hashnode&utm_medium=feed) [Ganesh Rama Hegde](https://hashnode.com/@hegde10122) · [Nov 2, 2025](https://hashnode.com/posts/chapter-17-coding-the-viewmodel-for-the-searchimageusecase/690793da24a0fbc02b2bfc6d) ### [Chapter 17 - Coding the ViewModel for the SearchImageUseCase](https://androidavatar.hashnode.dev/chapter-17-coding-the-viewmodel-for-the-searchimageusecase?utm_source=hashnode&utm_medium=feed) data class SearchImageUiState( val isLoading: Boolean = false, val errorMessage: String? = null, val searchResults: List = emptyList() ) /\*\* \* ## ArtViewModel (Simplified Version) \* \* This ViewModel is responsible for fetching... 4 min read · [androidavatar.hashnode.dev](https://androidavatar.hashnode.dev/chapter-17-coding-the-viewmodel-for-the-searchimageusecase?utm_source=hashnode&utm_medium=feed)