Programmer’s Paradox

Being agile does not mean rigidly adhering to a system called Agile.  Being agile means adapting to the situation at hand, no matter how you choose to adapt.
That’s my take from Steve McConnell’s latest post and I completely agree with him.

Designing for the Social Web is a recently published book written by Joshua Porter, the man behind the the design blog and website Bokardo.  I’ve been reading Bokardo for a while now, and so when Designing for the Social Web became available, I picked up a copy for myself.
The book has to be one of [...]

Divide and Conquer.
It was while reading the Thrift white paper, and seeing this line in the conclusion that the connection hit me:
Thrift has enabled Facebook to build scalable backend services efficiently by enabling engineers to divide and conquer.
That’s exactly the point of all the various agile methodologies: enable a team to divide up the project [...]

Construx has released the results from their 2008 software mistakes survey.  It’s worth reading the article to see their methodology and how they slice and dice the numbers.
Here’s the final list they’ve come up with for the 10 classic software mistakes with the highest mistake exposure (meaning they have the highest average occurrence plus the [...]

Jay Fields has an excellent article up at InfoQ talking about software development.  He compares software development to playing poker.  It’s an analogy that works incredibly well.
In the article is this quote:
“Many programmers sit in cubes, tackling problems all on their own.”
While most of us don’t think about that statement often, if at all, it [...]