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 it obvious?
Well, most of the stuff is obvious when mentioned. 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".
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, so a lot of those problems have been ironed out long before somebody starts removing soil.
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 places, because they are willing to learn and they come with a good background (they learnt at other places). Also they stay at their jobs because they are paid more. 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 people and also the company's income per worker is higher, meaning their selection has better results.
Having worked at those environments I can tell you shat it feels like: It feels like you are working with smarter people and that they are therefore more autonomous. They make fewer mistakes and they feel free to steer the way they work when the results are not ok. The results can be seen on a daily basis, so there is always room for improvement. You have a lot to learn when you arrive and you keep learning for a very loing time, while at the same time being productive in a very short period of time (around 2 to 3 months).
The architect shoudl 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.
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:
Publicar un comentario