4 ms·
There are many points worth of discussion in your comment. I just pick one for now. The details of the architects work. I am no architect, so all I think about
by erikb 12y ago
There are many points worth of discussion in your comment. I just pick one for now. The details of the architects work.
I am no architect, so all I think about it can be true or false. But what I remember from an architect friend is that an architect's work is not really that detailed. It's like the photoshop mockup of a website, not like its source code. It doesn't say exactly which materials should be chosen or how many screws should be used to connect two ends. An architects design says "There is a wall x cm thick and y cm long". The source code says "There z bricks and the last one we had to cut to n cm" (sometimes a comment will state why it had to be cut). For the source code it is to some degree by accident the amount of bricks creates something that can be called a wall.
- cam_l 12y agoWell, my work is pretty detailed! But all the information about the correct numbers of bricks, the slump of the mortar, the number and type of screws - these are all just library functions. Why would you re-write all that perfectly serviceable code for each project?
- erikb 12y agoGetting a library to work for your use case is exactly one of those things that needs quite a few workaround which the bricks are not part of the library. The library is the earth you build your bricks on top and you need to put in some work that your bricks can stand on it.