Failure – Weekly Article Dump

Failure: Should You Fear It? Thanks for checking out this weekly article dump, and sorry it didn't make it out on Friday. I was out visiting family in Alberta and I didn't have enough time to get this post all set up. Better late than never! The theme for this past week seemed to be articles about failure. Not all of them, of course, but a lot of authors are writing about what it means to fail and why that's not always such a bad thing. Do we need to avoid all failures in order to be successful? Articles Stepping Away, So Others Can Step Up: In this article, Jonathan Bush discusses something that's often hard for leaders to do... Step away. It's difficult for many people to disconnect and have trust in their team to get things done. Trust should…

1 Comment

Example: Getting Data Back From An EventHandler

Background I previously wrote about why I like to use events here and here. I figured it would be appropriate to illustrate a simple case where you can delegate decisions between functionally separate parts of code (say, between an application layer and a presentation layer). If you're well versed in C# and .NET, this might put you to sleep. If you have no idea what I'm talking about, hopefully this will help. By the end of this, hopefully you'll have a better idea for how you can use an EventHandler to pass data/state back through an invoked event... And don't forget to check out the code! The Scenario Let's assume we have a layered application, which is usually my go to. I might have three layers: one for data persistence, one for my business logic and one for interacting with…


Why Events? Decoupling.

Background Previously, I wrote about how events provide you with flexibility in your code. If you take on an event-based paradigm, you can view your system as a group of components that have events execute when certain conditions are met, and less of a procedural view where X always must occur after Y. But what else do events let us do? Decouple your architecture! We all know decoupling is a beautiful thing, so let's see how it's done.   How Events Decouple Your Code So the big question then is, how? I'd like to start by providing framing an example architecture. If we assume that we have code that is decoupled by major functionality, we might have some sort of layered architecture. This could mean that we have three layers: presentation, application, and data. These layers would be responsible for…


End of content

No more pages to load