31. July 2011, 16:32
There are a lot of literature about parenting. In fact, too much for my taste, so that it is very hard to tell right one from wrong one. Therefore I haven’t read much on this topic, especially given the fact such a reading would be in my case quite theoretical.
But recently I’ve stumbled upon an article that has immediately reasonated with me. I thought this article just can’t be wrong. And besides, it is also written in a very delicious style, so if you read Russian, please read the original.
Below is a shortened and helpless translation, which I did using Google translate and some manual editing. This article is written from the first person, who is a female psychologist living in Israel and is currently upbringing her two children.
Continue reading ‘Saying “No”’ »
25. July 2011, 21:18
Software architecture is art of expressing business with technology.
Technology has its limitations. If you pursue business goals without getting in touch with the technology, you will hit its limitations. When business hits technology, the latter won’t be hurt. The former will.
Business has not unlimited time and budget. If you evolve technology without getting in touch with the business, you will hit its limitations. When technology hits business, the latter won’t be hurt. The former will.
Great software architecture is when business dances with technology, and nobody gets hurt.
Rule of thumb: if software architect isn’t in touch with business, the software architecture will be worthless (at best), or dangerous for the business.
Rule of thumb: if software architect isn’t in touch with the source code, the software architecture will be ignored (at best), or dangerous for the technology.
Rule of thumb: software architecture written upon a requirements document (only) is invalid. Software architecture written without (at least) prototyping it in source code (better: implementing first iteration of production code) is invalid.