Sometimes we are so busy cranking codes and debugging apps that we fail to stop even just for a bit to look around us and find relationship to our works. Eversince I entered the IT industry , an 8 hour work schedule is never enough to keep track with IT changes. You study a new technology , once you're done and ready to make use of it a new comes along. Isn't it a tiring process? In between these infinite loops of a developers daily life, i usually stare at some of photos of my son and came up with a picture of how I look at my life now as a developer in the persona of my child . Read on and take a peek at marvins software development life cycle.
Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the inte
Comments