I’ve been helping with an initiative to establish a Data Analysis Special Interest Group where our focus will be on providing our consultants engaged in Data Analyst roles with the necessary, tools, tips, and techniques to help them succeed. As I was doing some research, I came across this blog published back in 2004, and I was surprised to find the content and questions as still being relevant.
After attending the 2014 version of AWS re:Invent and hearing the announcement of Lambda, I was intrigued about the possibilities of what could be accomplished with it and if it could simplify my software and infrastructure.
The purpose of this post is to illustrate the application architecture for a database-driven, e-commerce web application with traditional on-site hosting and hosting with Amazon Web Services (AWS). We’ll take it one step further and explore associated costs using AWS’s Simple Monthly Calculator, an online tool used to help customers estimate their monthly bill.
I recently saw a comment on LinkedIn that critiqued the Agile Transformation team of being the barrier to the Agile Transformation itself. Of course, my thoughts about my own Agile Transformation team started reeling. What does a good Agile Transformation Team look like? Several answers came to mind.
An Agile Transformation team should have these following characteristics:
Bad Incentives: How the ServiceNow Knowledge Base Resembles the Prisoners’ Dilemma, Part 1
ServiceNow Knowledge Base Background
ServiceNow is a Platform as a Service (PaaS) that offers an array of Service Management applications, with roots in IT Service Management (ITSM). Among them is a knowledge base, where users can gather, analyze, store, and share knowledge with the purpose of improving efficiency by reducing the need to rediscover knowledge. 
There are many design patterns available when implementing a universal application in Windows. The more common design patterns include Model-View-Controller (MVC), Model-View-Presenter (MVP) and, of course, Model-View-ViewModel (MVVM). MVVM is the more commonly used design pattern in Windows 8+ universal applications. This is due to its ability to decouple the business logic and view logic of applications in a way that provides the most reusable code across the two primary platforms - phones and tablets/pcs.
We live in a connected world – a world in which personalization and apps are at our fingertips and where your job doesn’t end the second you walk out of the door at 5:00PM. However, we often find that our companies are slower to innovate, adopt, or offer the services we are accustomed to outside of our work. We find that IT is still busy staying on top of service desk tickets, than reaching out to the business to improve productivity.