Group items tagged

"Even with the rise of cloud computing, the world still revolves around servers. That won't last, though. Cloud apps are moving into a serverless world, and that will big implications for the creation and distribution of software and applications."

"I want to look at some of the costs of unit testing and ask the question "why is unit testing hard?" After all, if unit testing weren't hard, we wouldn't have to question whether or not it was worth it.  It makes sense then to look at first why it is hard and what makes it hard."

Apple's new MacBook Pro follows the fine tradition of the iPhone 4 and third-gen iPad in that it has a super high-resolution Retina display: a 2880 x 1800 panel with an amazing 220 pixels packed in per inch. It's an incredible display. In fact, it's such an incredible display that it actually has about one million, seven hundred thousand pixels more than it needs to satisfy Apple's definition of Retina, leading some to claim that those pixels are all going to waste. Nothing could be further from the truth.

The goal of this blog entry is to explain the basic concepts of Scrum in less than five minutes. You learn how Scrum can help a team of developers to successfully complete a complex software project.

I have a very simple rule, I like to follow that helps to simplify my code. "Don't validate developer input" This rule simply means that we should not try and validate input that came from a source that is not a user or external system.

I've found that there are three basic types of duplication that we can eliminate from our code that successfully build on each other.

But there is another technological shift conspiring against many web frameworks that isn't focused on performance, but instead focused on "ease of use" - which in many cases may hit far closer to home.  That shift is the reorganization of MVC. 

CQRS, while a relatively simple concept, still brings a lot of assumptions about what CQRS is and should be. So what is CQRS? Simply put, CQRS is two objects where there was once one. We're splitting code infrastructure down to the data layers between commands and queries. But the assumptions around what a CQRS should be lead folks I've seen down paths of unnecessary complexity. Complexity around the architecture, and especially around the UI.

I don't want to write this article. I believe there is no way to provide advice about listening without sounding like a touchy-feely douchebag. But I'm going to write this article because there is a good chance that your definition of listening is incomplete, and what I consider to be obvious and simple ways to listen are not obvious at all.

Many things in programming become easier as your level of experience increases. However, some things remain stubbornly difficult. This document tries to characterize five of these difficult things; optimization, networking, security, reliability and scalability, what makes them hard and what you can do about it.