Interview with an Architect


I was asked to interview an Architect. Before I could say anything, he told me that he was an Enterprise Architect and he was absolutely disgusted that he was asked to document the Infrastructure. He further told me that he only wanted to be an Enterprise Architect. He explained to me that for understanding things better, he was studying the “C” code available in our Enterprise.

The last statement gave me enormous joy for 2 reasons.

  1. I said to myself that now I could at least ask some questions as “C” language was involved.
  2. I was glad that he was in touch with programming in spite of being an accomplished Architect.

I first set the premise clear to him that I was only the manager for System Architecture, that too acting. So, Enterprise Architecture was not in my scope of work. Next, I requested him to explain what he is unable to do by being a Technology Architect which he can do as an Enterprise Architect (You see I know a lot of jargon to sail through any situation. I have no idea what should be the answer to this question). He gave me some answer which I of course did not understand. Anyway, I asked him some more questions from the various problems on Architecture I need solving as a part of my job as the head of this department in our company. I also requested him to suggest some directions for solving the issues he had noticed in our Enterprise from his study for the past 6 months or so. It was a very interesting discussion with me learning about Rolls Royce and Scotland Yard and many other things. I told him that as I was not a professional Architect, I would give him the benefit of doubt.

I, then, requested him whether I could ask any question on “C” as he had studied “C” code till 3AM last night. He said that I could do so by all means. So, I requested him letting me know that in “C” if I want to print a variable named “a”, which is an integer, what should I write in the program. He started explaining something which I was not understanding. So, I gave him a board marker and requested if he could write it on the white board in my office. He wrote “printf” followed by a dash and then was waiting and thinking. In my enthusiasm to show my intelligence, I suggested that possibly he would like to write a “comma” followed by “a” and consider putting some brackets and look for a place to put a semicolon. He agreed and I was so glad. Then I requested him to let me know what I need doing if I want to read a value from the standard input into the same variable “a”, which was defined as an integer, in a “C” program. He blinked for some time. Seeing him blink, again in my enthusiasm, I suggested that whether he would consider something like “scanf“. He agreed with me and I was again elated. So, he wrote “scanf” on the board and was waiting. So, I suggested that he could consider writing the address of “a”. He thought for a while and told me that it was a good idea. So, I told him that possibly he would consider something like “&a”. He agreed.

I told him that I did not mean to demean his role as Architect and thus was not wanting to know all this from him. I actually wanted to know why Mr. Dennis Ritchie was so stupid that he takes a variable reference for printing its value and takes the address of the variable for reading a value into the variable. I told him that I was looking for this answer for very long. I was extremely sad when I was informed through Facebook that Mr. Ritchie had passed away as I wanted to tell him what a stupid language he has created which creates so much confusion. I wanted to tell Mr. Ritchie that he had no sense of symmetry whatsoever. I was still looking for the answer so that I could rectify the language before it is dead.

He wished me luck in my research. Using my enormous skills learnt and practiced through years of experience, I shook hands and headed straight for the Smoking Room. On returning from the Smoking Room, I made a report stating facts of the interview only and no decision. My report said that I found that the person’s handwriting was a bit difficult to read.

English: Unix creator Dennis Ritchie

English: Unix creator Dennis Ritchie (Photo credit: Wikipedia)

%d bloggers like this: