Ever needed a simple test to get that interviewee talking? The point of this Knol is to provide you with a small code sample to discuss with an applicant.
Given the size of the world and the number of companies in it it's pretty unlikely that either a) whoever you give this test to (as a company) will have read this, or b) if you memorise this (as an interviewee) that this will be the test the company uses.
It's just a bit of fun that comes after I realised that I'd written some technically correct but logically incorrect code. Hope it will be useful to someone someday!
Here is the code snippet;
static void Main(string args)
string filePaths = Directory.GetFiles(Directory.GetCurrentDirectory());
if (filePaths.Count() > 0)
StreamReader file = null;
file = new StreamReader(Directory.GetCurrentDirectory() + @"\Settings.txt");
while ((line = file.ReadLine()) != null)
foreach (string OldName in filePaths)
string sRename = line.Split('|');
string NewName = Path.GetFileName(OldName).Replace(sRename, sRename);
if (Path.GetFileName(OldName) != NewName)
Path.GetDirectoryName(OldName) + @"\" + NewName);
if (file != null)
The first thing to say is that this code compiles and runs. This test isn't about asking people how much they know of the C# syntax and how easily they could write applications using Notepad to compile later. If you like people like that then you're probably after a much longer series of tests!
Question One: What does it do?
A fairly good answer would be: Renaming files based on a series of rules read in from a file.
That's an excellent high-level description that you could give to anyone who would instantly know what was going on. Of course Software Engineers tend to answer in a more complicated way so you can expect some mention of "in the same directory", "using old/new values in the file separate by | (pipe)", "renaming only files where the rules in the settings file require it", etc.
As a quick example of how it works if our Settings.txt file contained two rows:
And you had the files; Execution_Test.txt and OldData.txt in your directory then after running the application these would be changed to ExecutionText.txt and Data.txt.
Now here are a (non-exhaustive) list of things that could be raised during a discussion;
- Lack of comments. Always a good one for the interviewee to raise!
- There is no error-checking so errors drop right out with the ugly "... has stopped working" windows error message. This can happen in multiple places; Reading from Settings.txt (does it even exist for a start!), renaming a locked file, invalid text in Settings.txt, etc.
- Variable naming. Very inconsistent; file, NewName, sRename, etc.
- BUG: The application will try and rename itself and the settings.txt file - ideally both of these should be ignored.
- BUG: If you have two entries in Settings.txt (say Old|New, and Yes|No) then if you have a file which combines the two entries (OldYes.txt, NewYes.txt, etc) then the application will crash as when it tries to do the second rename the file will no longer exists - the application should read settings and loop files rather than reading files and looping settings.
- BUG (Obscure): If you are simply changing case (Old > old) then Directory. Move will raise an error, you need to use a temporary file in this special case.
I'm sure there are more (I should really have written these down as I thought of them rather than trying to remember a few days later), let me know all the ones I've missed by commenting below.