A difficult day

Friday 10 September 2004This is more than 20 years old. Be careful.

Yesterday, a one-hour meeting to finalize some details of another developer’s feature turned into a multi-meeting all-day extravaganza that re-examined a number of central architectural issues, including modularity, data model, separation of powers, capabilities of APIs, and the nature of God.

OK, we didn’t get to the nature of God. But it was exhausting, and at the end of it, a handful of architectural decisions that I really liked were in question. Now I have to put on my thinking cap and make some proposals. It means getting past the disappointment of my direction not being taken, and getting down to the key issue: what is the best design for the current set of requirements. No wonder they call it “work”.

Comments

[gravatar]
I vote for the Ned way...
[gravatar]
Getting people to understand that I am always right is, as they say, a full time job.

Add a comment:

Ignore this:
Leave this empty:
Name is required. Either email or web are required. Email won't be displayed and I won't spam you. Your web site won't be indexed by search engines.
Don't put anything here:
Leave this empty:
Comment text is Markdown.