Welcome to DocForge, an open wiki for programmers. Anyone can contribute documentation, articles, and tips for software developers. Our mission is to be a central repository for information helpful to those who create software.

We all talk about using the right tool for the job in the context of programming items. But which job? And what's the right tool for it?

I want your help in determining the answer for this.

This compressed file contains 9 text files that make up the entire source code for the original Metroid game for the NES. These files are an expansion of SnoBro’s Source code he posted a few years ago. The code has been changed to be assemblable with Ophis instead of x816 because of memory issues. Labels corresponding to address values have been added to every line to make the code easier to follow for beginners interested in understanding the inner workings of a Nintendo game. The labels also make the code easier to debug if it is modified. At this time, the source code is still a work in progress but it is much farther along than the original document. The title page is completely documented. The intro routine, end routine, password scheme and sound engine are described in detail. About a third of the game engine is detailed and about half of each game area page.

A complete list of all major algorithms (300), in any domain. The goal is to provide a ready to run program for each one, or a description of the algorithm. Programming languages include Java, JavaScript and PHP, C, C++ either in direct form or generated from a Scriptol source.

Rich Hickey's second, "philosophical" talk at the first Clojure Conj, in Durham, North Carolina on October 23rd, 2010. Many thanks to Matt Courtney, who graciously provided the equipment and expertise that made this recording possible.

This is the second of several posts in which I’d like to share some of the things we learned throughout more than 14 sprints of Agile development using Scrum. Some of them might appear as open doors, but I wish I knew or thought about those before I started that project. Just by looking back at the mistakes a team of 10 made in a period of 12 months, they apparently aren’t that obvious. So after having discussed requirements management, let’s talk about the sprint planning.

In this post I proudly present the Top 100 of Best Software Engineering Books, Ever. I have created this list using four different criteria: 1) number of Amazon reviews, 2) average Amazon rating, 3) number of Google hits and 4) Jolt awards. Please refer to the bottom of this post to find out how I performed the calculations, how to receive the full top 100 list in PDF MS Word, and why that obscure and silly little publication of yours has not made it on my list.

It's been nine months since I created the Top 100 Best Software Engineering Books, Ever, with the best books ever released. I still refer to it when I want to pick up a timeless classic.

But last week I suddenly had the desire to know what the new best software development books are. And I couldn't find any such list. So, of course, I made it myself.

One year ago, at the Agile 2010 conference, I came up with the idea to publish a Top 100 Agile Books. Like many of my other top 100 lists it was a great success (in terms of blog traffic).

This year I am not at the Agile 2011 conference (for various reasons, both good and bad). But nevertheless, I decided to publish a new edition of the Top 100 Agile Books, especially for my friends at Agile 2011 who are enjoying a great conference without me.

The Play framework makes it easier to build Web applications with Java
Finally a Java framework made by Web developers. Discover a clean alternative to bloated enterprise Java stacks. Play focuses on developer productivity and targets RESTful architectures.

What things should a programmer implementing the technical details of a web site address before making the site public? If Jeff Atwood can forget about HttpOnly cookies, sitemaps, and cross-site request forgeries all in the same site, what important thing could I be forgetting as well?

Factor the UI into a view and controller where the view handles simple mapping to the underlying model and the the controller handles input response and complex view logic.

After listening how the community has interpreted Command-Query Responsibility Segregation I think that the time has come for some clarification. Some have been tying it together to Event Sourcing. Most have been overlaying their previous layered architecture assumptions on it. Here I hope to identify CQRS itself, and describe in which places it can connect to other patterns.

Many people have been getting confused over what CQRS is. They look at CQRS as being an architecture; it is not. CQRS is a very simple pattern that enables many opportunities for architecture that may otherwise not exist. CQRS is not eventual consistency, it is not eventing, it is not messaging, it is not having separated models for reading and writing, nor is it using event sourcing. I want to take a few paragraphs to describe first exactly what CQRS is and then how it relates to other patterns.

How many of your projects start off like this: You and your team get together at the start of your project thinking you are all on the same page?

And when you start building something, you realize you were thinking something completely different.

This happens all the time on projects: assuming there is consensus when none exists.

While good teams can roll with these punches and adapt as they go, it’s a form of waste that can hurt or kill the unwary before they even get out of the gate.

To nip this problem in the bud, at ThoughtWorks we created a lightweight project chartering tool called “The Agile Inception Deck: 10 questions and exercises you’d be crazy not to ask before starting your project.”