domingo, 7 de octubre de 2007

I usually agree against corporate standards

I usually agree against corporate standards ;-), but this got me thinking:

http://blogs.tedneward.com/2007/09/20/Hard+Questions+About+Architects.aspx

Are you really trying to say that the architect should not consider his job seriously?

I mean, do you realy think this architect should say: "Ok, let us do it your way" I wouldn't seem serious. And although deep down it is not serious at all, it still have to seem serious. This sounds cynical, and maybe it is, because I'm thinking on my convenience, but also an strategy that doesn't seem serious to your partners, even if it is a great strategy, is impossible that it achieves success.

Actually you can be pretty serious, doing unit tests and functional tests all over the place, but you still have to play your role. Your architect role.

Although that I agree that anyone who critics XP better doesn't tell me XP is not about not writing documentation, because in that case it means they have an opinion about something they have not read, and the XP documents are readily available, so it means they:
  1. Advocate writing a lot of documents.
  2. They do not read them.

Lame architects!

And yet the world is full of lame architects.

But imagine an XP architect. One that advocates not writing documentation if it is not needed and one that reads all the documentation and signs off projects once all the documentation is in place... (I suppose you agree the architect is not the only one who writes documentation, but the one who supervises the documentation and the code).

Would you fire him for having a strong opinion about how things should be done? (For those who do not know XP, XP have a very strong opinion about almost everything). Furthermore being an architect means that you have had successes and failures and therefore you can guide a team about certain choices because you have more experience.

An architect needs to have an opinion. A severe opinion, about everything (ok, I'm exageratting here, but in the matters that matter to the project, he needs to be opinionated). From how you document to how you should test. From how to do code reviews to how to incorporate new designs and third party code into the systems you are designing.

And if he thinks your code does not belong to the project, maybe he is right. Also maybe you can do things to prove him wrong, in which case he could be happy because he is learning, or otherwise he could be fired because he is unwilling to learn.

The last project I was on went smoothly in every possible way, except in the Workflow team. The workflow code was crap. It was my opinion and the opinion of most developers. But the project manager and the project director defended this developer, who was a pretty good developer, but did not understand the rest of the architecture. They defended him until it was not possilbe to defend him anymore, so they passed me the problem for me to fix it.

What? >8-O

It is my opinion that before making any changes you need to assess what is working and what is not. This is called "making a diagnosis".

And the only way of knowing if the project is ok is to know what the requirements are, what were the design decisions in order to satisfy those requirements, do the adequate prototypes and then integrate them.

XP doesn't say exactly so, but it is pretty close. In XP you need to work in iterations and show the iterations working (the same happens in Scrum sprints). The main difference is that I care less about iterations and care more about doing prototypes (spikes in XP terms).

But the Workflow code was already embedded in the system and surely most of the business objectives were not met by the design. What is the point then of makiung trivial changes to convoluted code, if what was needed was a massive rewrite?

I mentioned that it would take 3 months and 3 developers. But I was denied the resources, which in my opinion was nothing compared with the 1.5 years and 30 people in the project.

Reasonable?

I stand from my point of view.

As C.A.R. Hoare, the inventor of QuickSort, once mentioned: "I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies."

You can read it here.

I don't endorse XP, although I recognize it would be better for 99% of the projects to apply it. Both XP and Scrum. And I recognize you need an XPer and/or an Scrum master to apply them correctly, because reading books is not enough. The main reason I don't endorse XP is that when you finish a project it becomes boring. And most projects I work on, become boring pretty fast, since the possibility of failure decreases very quickly, while XPers advocate that if a project is boring is because you are not doing it right. I understand why XPers mention that. A project may become boring by repetition and repetition must be avoided at all costs. But anyway, a multitude of different projects all look and feel the same after a while, so even starting new projects becomes boring after a while. You can tell in the first day or two if the project is going to be a raving success or a raving madness.

Time is money

Time is money except in one respect. From wasting money you can recover. From wasting time, you can't. Therefore if you are not going to succeed in your endeavor, it is better not to even start. I've seen many projects fail and most of the time the problem is that no one knows what needs to be achieved. Massive amounts of people are hired and no one has an idea of what the objective is.

Therefore you first need to know the objective. Then do the minimal to achieve success. Once finished, verify you have succeeded. Wash, rinse, repeat.

Make sure you are solving real business requirements. Making sure your objectives are important enough as to get promoted once finished. Or at least to get filthy rich, as a second option. There is no worse waste of time than achieving unimportant goals.

No hay comentarios: