It is a Chief Architect in Maryland who led me onto a programmer's track. Last night, I met him and asked him to have a look at the manuscript of my discussion between me and Guest. My instructor condemned me and he told me to shut up.
My instructor thought I should have not involved in any communication with the guest. He thought such a discussion is pointless. He stressed before me that a good architect is good at explaining customer's requirement, writing definite documentation, doing various trade-off things, ...Finally, he told me that a project is not implemented by packing some patterns.
I was blamed on. My chief architect's words are: " Why did you present your ideas in the case that some guy just gave you a two-sentense description of his so-called project? Are you so cheap?" Though I felt extremely embarrassed, I had to admit I was wrong.
I think I had a good lesson. Actually, I did not understand what the Guest wanted to do even after I finished the discussion.
This post has been archived. It cannot be replied.