One of our teammates will get back to you soon.
This article presents the fun and useful game of "Code Battleship" to evaluate the quality of your codebase.
If you’ve been involved in software engineering recently, you’ve probably heard of the "Joel Test" of software. I recently ran into a situation where a prospective client wanted to talk about estimates for building certain features, but without a signed contract wouldn’t give out access to the code base.
Obviously any estimates given would be very approximate, and probably dangerous shots in the dark. However for the sake of entertainment, I decided to play along and try to come up with approximate timelines. I thus came up with a list of questions that I could ask so that I could get a rough idea of the code quality that inhabited the invisible code base. I thought of it as a game of sorts - a Code Battleship, if you will. If enough of the answers came back negative, I envisioned the other party yelling in despair, “you sunk my code base!” Without further ado, here are the questions in Code Battleship:
Have you ever played Code Battleship? Let us know in the comments if you have other questions that could contribute to sinking enemy vessels.
Published on May. 25, 2014
Join our community of avid readers and stay informed with the latest articles, tips, and insights delivered straight to your inbox. Don't miss out on valuable content – subscribe now and be part of the conversation!
We care about your data. Check out our Privacy Policy.