# signaling (blogs) — RSS Amplifier Recent posts from the 1 feeds in the RSS Amplifier directory that cover signaling. Page: Feed: --- ## [The Code is the Context](https://nizar.se/the-code-is-the-context/) _2025-12-01 · Nizar's Blog_ Most advice on working with agents focuses on orchestration and interaction strategies. But I keep finding renewed significance in the software development fundamentals we've always known. After all, agents don't just respond to how we prompt them, they also respond to what they find in the codebase. Discovery Agents start each session fresh, with no memory of previous work, just the prompt and… ## [Lean Claude Code for Production](https://nizar.se/lean-claude-code-for-production/) _2025-08-15 · Nizar's Blog_ Many agentic coding demos showcase landing pages, one-off scripts, or greenfield projects. While technically impressive, they often produce single files with little thought for maintainability. Even OpenAI's ChatGPT 5 launch demo followed this pattern. At the other extreme, some content focuses almost entirely on elaborate integrations and orchestrations. Both have their place, but neither reflect… ## [TDD Guard for Claude Code](https://nizar.se/tdd-guard-for-claude-code/) _2025-07-21 · Nizar's Blog_ Claude Code fit well into my workflow, but sticking to Test-Driven Development (TDD) principles still needed occasional reminders: one test at a time, fail first, no over-implementation. It worked, but it wasn’t effortless. So I built TDD Guard , a utility that handles that for me and keeps my attention focused on designing solutions rather than policing TDD. Leveraging Hooks The breakthrough… ## [Agentic TDD](https://nizar.se/agentic-tdd/) _2025-06-17 · Nizar's Blog_ Since I started programming, I've insisted on always writing my own code. It wasn't out of necessity; it was a personal choice. Even as LLMs (Large Language Models) became part of my workflow, I stayed firm about handling production code myself. Last week, that changed. Exploring Coding Agents After seeing countless demos online and reading about new workflows, I decided it was time to experience… ## [How I Use LLMs as a Developer](https://nizar.se/how-i-use-llms-as-a-developer/) _2025-04-25 · Nizar's Blog_ I have been using Large Language Models (LLMs) for the last two years. During this time, I’ve noticed that people’s opinions about LLMs vary dramatically. The community seems split—some developers swear by them, while others remain skeptical or outright dismissive. Personally, I find these differences fascinating because they highlight that there’s no single “right” way to think about LLMs, and… ## [Implementing Durable Entities in Kotlin - Final Enhancements](https://nizar.se/implementing-durable-entities-in-kotlin-final-enhancements/) _2025-01-07 · Nizar's Blog_ Introduction Throughout this series, we've explored Durable Entities from the ground up: managing state, creating entities, signaling, cross-communication, and two-way interactions. There steps have culminated in a flexible and functional system for handling stateful workflows in Kotlin. In this final post, we'll refine and enhance our implementation. By introducing abstractions and a DSL-like… ## [Implementing Durable Entities in Kotlin - Calling Entities](https://nizar.se/implementing-durable-entities-in-kotlin-calling-entities/) _2025-01-06 · Nizar's Blog_ Introduction So far, we have built a solid foundation for Durable Entities in Kotlin. We have established stateful entities that persist data and allowed them to interact dynamically through signaling. We have also introduced cross-entity communication, where entities can notify each other of significant events. However, all interactions so far have been fire-and-forget. Entities can send signals,… ## [Implementing Durable Entities in Kotlin - Cross Communication](https://nizar.se/implementing-durable-entities-in-kotlin-cross-communication/) _2025-01-05 · Nizar's Blog_ Introduction So far, we have built stateful entities that persist data and respond dynamically to external input through signaling. However, all interactions have been one-directional: clients send commands, but entities remain isolated from each other. Real-world applications often require entities to collaborate, exchanging updates and triggering actions across a distributed system. This post… ## [Implementing Durable Entities in Kotlin - Signaling Entities with Input](https://nizar.se/implementing-durable-entities-in-kotlin-signaling-entities-with-input/) _2025-01-04 · Nizar's Blog_ Introduction So far, we have implemented signaling to interact with entities dynamically, allowing our counter to respond to operations like increment and reset. However, these signals have been limited to simple operation names, restricting flexibility. In this post, we extend our signaling mechanism to support input data, enabling more complex interactions. By passing structured data with each… ## [Implementing Durable Entities in Kotlin - Signaling Entities](https://nizar.se/implementing-durable-entities-in-kotlin-signaling-entities/) _2025-01-03 · Nizar's Blog_ Introduction So far, we have created an entity that stores state using custom status, but it remains static. Once created, there is no way to interact with it or modify its state dynamically. In real-world applications, stateful objects must react to external inputs. This is where event-driven updates come in. In this post, we introduce signaling, a mechanism of sending one-way (fire-and-forget)… ## [Find what they just said (Sponsored)](https://crawlproof.com/a/gI2i4rWG8KRN) _2025-01-02 · **Sponsored**_ Surface recent public signals so you can send policy-aware, relevant outreach ## [Implementing Durable Entities in Kotlin - Creating Entities](https://nizar.se/implementing-durable-entities-in-kotlin-creating-entities/) _2025-01-02 · Nizar's Blog_ Introduction So far, we have seen how Durable Entities persist state across executions and conserve resources. We have used custom status and metadata to store and retrieve state for a basic Counter entity. However, to interact with entities efficiently, we need a structured way to identify and reference them. This post introduce Entity IDs, which uniquely identify specific instances of an entity.… ## [Implementing Durable Entities in Kotlin - Persisting State](https://nizar.se/implementing-durable-entities-in-kotlin-persisting-state/) _2025-01-01 · Nizar's Blog_ Introduction Durable Entities provide a way to model long-lived, stateful objects in serverless workflows, but they aren't natively supported in Kotlin. In the previous post , we introduced Durable Entities and explored their key principles, such as event sourcing and deterministic execution. A fundamental requirement of Durable Entities is persisting state across executions to ensure entities… ## [Implementing Durable Entities in Kotlin](https://nizar.se/implementing-durable-entities-in-kotlin/) _2024-11-19 · Nizar's Blog_ I've been fortunate to work with some of the greatest minds early in my career, an opportunity I'm endlessly grateful for. Over the past year, I've worked with Erik Meijer on Automind , tackling some truly exciting challenges. This experience introduced me to Durable Functions, an abstraction that simplifies building stateful workflows in serverless environments. Among its many features, Durable… ## [Supply Chain Security Risks in Static Sites](https://nizar.se/supply-chain-security-risks-in-static-sites/) _2024-09-11 · Nizar's Blog_ Static sites are perceived as more secure than their dynamic counterparts due to their simplicity and lack of server-side components. However, this perception can lead to overlooked threats, particularly those introduced by third-party libraries and services. In this article, we'll explore how these vulnerabilities arise and how you can defend your site against them. What Are Static Sites? Static…