Stretching perhaps from the introduction of the first iPod in 2001, through the release of the groundbreaking iPhone 4 (and subsequent refinement with the iPhone 5), Apple was regularly lauded as best-in-class when it came to hardware and software design and the synchronicity of those elements. But things changed.

It’s been said that software is “eating the world.” More and more, critical systems that were once controlled mechanically, or by people, are coming to depend on code.

There’s a potential security exploit that ASP.NET MVC leaves you open to. However, in Peter’s opinion, all the proposed solutions miss the point.

Policies are often the result of something that once went wrong. It’s organizational scar tissue developed from a This Can Never Happen Again mandate. And its almost always ill-considered.

Everybody gives lip service to the idea that people are the most important part of a software project, but nobody is quite sure what you can do about it. The very first thing you have to do right if you want to have good programmers is to hire the right programmers, and that means you have to be able to figure out who the right programmers are, and this is usually done in the interview process.

This fairly trivial project aims at introducing a newcomer to GraphQL and the way it works. The code aims to explain the client and the server side of things. The source code has been heavily commented and documented in order to explain what's going on. It is highly recommended to read through it. Do not be afraid!

After years of being left for dead, SQL today is making a comeback. How come? And what effect will this have on the data community?