lunes, 5 de mayo de 2008

Architecturally Poor J2EE Applications

Structuring systems around objects or beans and lacking abstraction is like building a building around bricks.

You can do that, but a pile of bricks is not a building.

In order for a building to be functional, well, it has to be able to interact with its environment. For example the entrance must be big enough for humans to enter, and it must be open to a street. Isn't this obvious?

Well, most of the stuff is obvious when mentioned in retrospect. But it has to be mentioned for people to make the right decisions at the appropiate time. That is, when a guy is closing the entrance, he must speak up and say "we shouldn't be doing this, because we are closing the entrance, people won't be able to enter the building anymore".

Yet we don't expect people to find out things like that when they are actually putting the bricks, because there is a model of how the building will look like before they start to make a hole in the ground, the so called blueprints, so a lot of those problems have been ironed out long before somebody starts removing soil.

If we only could build software like that. Most projects are severely underspecified.

Even in buildings, yet there are lot of technical decisions to be made inside every appartment, from the point of view of each individual worker. Irrelevant from the point of view of the architect of the building, but important from the point of view of the person who is inhabiting that building if they turn out to be bad decisions.

It turns out that good developers are hired at the best job, because they are willing to learn and they come with a good background (they either learnt at other places or they came with straight A's from their PhD). Also they stay at their jobs because they are paid more and they get recognition. Eventually all those little differences make a huge difference in income for the company and you can see that in that most successful companies pay more for their developers and also the company's income per developer is higher, meaning their selection has better results.

Having worked at those environments I can tell you what it feels like: It feels like you are working with smarter people and that they are therefore more autonomous. They make fewer mistakes, they do things that seem impossible and they feel free to steer the way they work when the results are not ok according to their own criteria. The results can be seen on a daily basis, so there is always room for improvement. Whe you arrive to such a job, you have a lot to learn and you keep learning for a very long time, while at the same time being productive in a very short period of time (around 2 to 3 months). When you arrive to the worst jobs, they have been doing nothing for 6 months, they have mandatory overtime and it doesn't matter how much time you spend at the job, nothing ever gets done. If something looks like it is going to get finished, it will get redone using a different format, just for the sake of it.

Some pitiful companies are struggling for money so they can't keep their developers long enough for them to learn, they produce mediocre products that no one is proud of and finally either developers quit or they are fired. Therefore this perpetuates bad developers job hoping and good developers stay at the best jobs, learning and improving.

So the first job for a job seeker is to work at companies that consider hiring developers as an investment. The first job for a manager is to hire the right candidates. No, they are not going to learn Java on the job. They need to know Java and algorithms right away, so that they can learn the advanced stuff.

There is a need for an architect on every project, although most probably you need one architect for each 10 projects, if you have hired expereinced developers. If you are hiring unexperienced developers, no architect is going to solve your problem.

The architect should concentrate on looks and interactions, for example: will the system have scroll? Most usability experts agree that web applications should never scroll, but sometimes you have so much information that you need a scroll here and there. I would reasonably try to remove those scrolls and exchange them by something else. For example it is typical to have "pagination". Yet what is pagination if not another kind of scroll? Yet pagination is simpler from the point of view of the user.

Companies can produce technology, like Sun, Bea, IBM and Oracle. When a company, say a bank or a health insurance company wants to develop an information system, it selects one of the providers mentioned and then one integrator to implement the system. The provider does nothing but selling its trademark and gets the lion share of the profits, while the integrator does all the work, gets all the risk and gets almost no profit.

Providers usually seat on their pants with mediocre products.

Take Google for example. It has pagination and scroll. Its a terrible user interface, since I can't paginate without using the scroll. Also it could be done using Ajax and it could sort results by different criteria and it could do so much things. Web search is not finished, yet it seems they think they have reached a plateau.

No hay comentarios: