<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on Bruno Pedro</title><link>https://brunopedro.com/categories/development/</link><description>Recent content in Development on Bruno Pedro</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 19 Oct 2022 14:55:13 +0200</lastBuildDate><atom:link href="https://brunopedro.com/categories/development/index.xml" rel="self" type="application/rss+xml"/><item><title>Event-driven Feature Development</title><link>https://brunopedro.com/2022/10/19/event-driven-feature-development/</link><pubDate>Wed, 19 Oct 2022 11:20:00 +0200</pubDate><guid>https://brunopedro.com/2022/10/19/event-driven-feature-development/</guid><description>&lt;p>Sharing information between different features can be done in a synchronous or asynchronous fashion. Following an asynchronous communication style doesn’t mean that you’re sharing events. You can, for instance, pass commands between features. By doing so, you’re creating a strong functional dependency between features. To avoid that, you should instead share information about things that happened, or events. By sharing events, you create opportunities for other features to become more relevant to users while acting independently.&lt;/p></description></item></channel></rss>