Migration – Weekly Article Dump

Migration: Bye to the Pi Well... it happened. If you checked in earlier this week, you might have noticed Dev Leader was completely down on Thursday. Quite a bummer... but the show must go on. Migration to a new host was necessary, but that wasn't without some hiccups. For me, having a site hosted was still a pretty new process. I had tried it a couple of times before, but running a web server that I controlled always felt better. Just more control I suppose. Migration started off sort of sour where I was required to re-install Wordpress on my host a few times due to some technical difficulties... And of course, it was hard to sit still while I knew my site was down. Once I finally had Wordpress launched, the only part of the migration that went smooth…

0 Comments

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…

0 Comments

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…

0 Comments

Why Events? Flexibility.

Background There are many different approaches to developing software, but in my opinion, the opposite ends of the spectrum end up being: Knowing how the whole system looks, feels, and operates before coding a single line. Having an idea of what the user wants and coding to make it happen. Although I'm generalizing a lot here, it's sort of like the battle between Waterfall and Agile. Okay, great. So what am I rambling on about here? Well, in the first case, you know all the ins and outs of the system. You can structure your system so that almost no matter how complex it is, you can ensure that method A is always run immediately after method B which is etc... The design is completely controlled. You have a spec for how all the components work together. The problem? Well,…

1 Comment

End of content

No more pages to load