Jun. 14th, 2009
on variance
Jun. 14th, 2009 03:24 pmJust wrote about it in blogspot: tried to come up with an explanation for Java OOP programmers.
откуда эта идея...
Jun. 14th, 2009 04:20 pmчто на каждое явление природы должно быть министерство? Я не думаю, что это чисто российское явление; в Британии как плохая погода, так министр окружающей среды виноват. А вот в США как-то на министров не принято валить; да и министерств-то, собственно, нету. А ведь в России так и принято полагать, что врач подчиняется минздраву, сантехник Минжилкомхозу, плотник Минстрою, а рыбак Минрыбпрому.
Странное явление. Вот легализуют парады гомосексуалистов, заведут и госкомитет, типа Госкомпидарас.
Странное явление. Вот легализуют парады гомосексуалистов, заведут и госкомитет, типа Госкомпидарас.
architecting vs refactoring
Jun. 14th, 2009 10:31 pmLast week I spent a couple of years hours "architecting" with my colleagues. They are all smart people, yes. They just talk and philosophize too much.
I'm talking about designing a structure of one single application, not a network of applications. One single application running on one single machine. I do not think it needs an architecture. I think what it needs is robust coding principles, a good set of unittests and an ability and willingness to change fast, to refactor mercilessly. Do big refactoring as soon as one is required, overturning any stone as necessary.
In this case we don't need an "architecture". The application fluently transforms from one structure, instead of being frozen with a solution from several years ago.
See what I mean?
I'm talking about designing a structure of one single application, not a network of applications. One single application running on one single machine. I do not think it needs an architecture. I think what it needs is robust coding principles, a good set of unittests and an ability and willingness to change fast, to refactor mercilessly. Do big refactoring as soon as one is required, overturning any stone as necessary.
In this case we don't need an "architecture". The application fluently transforms from one structure, instead of being frozen with a solution from several years ago.
See what I mean?