I’ve heard lots of people talk about architectures and their impact on building systems. Most people seem to agree that building systems need to be well designed and optimized to work together efficiently. This is a concept that we often hear about and try to implement, but I am convinced that there is an even more important aspect to architecture that deserves attention. The term I’m referring to is “information technology architectures.
Information technology architectures are the software that allows computers to operate. The computer that you are using to play the game you are playing in your browser is a computer. The computer that your kids are using to play video games are computers. The computer that your friend uses to access your email are computers.
This is an important point because it helps us think about what we are building. We build software, then we put it in computers and then we put it back into computers. It is this cycle that can make us think of the architecture itself. A computer’s architecture is what permits it to do a certain specific job, and then we put this architecture into a computer. We put it back into another computer and we put it in another computer.
We don’t get to know computers or the computers yet. We don’t know what computers are, how to build them, how to get them to do the job we want. This is also an important point because it helps us think about what we are building. Some of the computer architectures are very complicated, but they are also not complicated in the “wrong” ways. Some of them are very easy to build, but they are also not easy to get right.
This is the problem with the new computer architectures. They are as alluring as they are complicated. The computer architecture is such that it is so easy to build, it’s hard to get it right. I suspect this is true for all computer architectures. We want computers to do the job we want them to do, but we do not want them to be doing the job we do not want them to be doing.
The problem is that the architecture of modern computers has a tendency to try to do too much too soon. This may be good for the end user and for the end users of the product, but it usually leads to headaches for the engineers and designers. The architects and designers have to figure out how to keep the designers from doing the work the users want them to do, meanwhile keeping the engineers from doing the work the users do not want them to do.
Architects and designers have always been at odds with each other. The need to architect and design was a reaction to the need to design and build. Nowadays if you design and build, you tend to get all the work done for you, and that is often just as well. On the other hand, if you architect and design, you may get little or no work done for you. But the two sides tend to become more at odds over time.
Architecture and design often go hand-in-hand in a lot of fields. In fact there are many architectural designs for building things that have been made (or are made) for the purpose of being designed. The architects and designers who come up with these designs usually are the ones who are making the designs.
Design is all about creating a solution that works. It’s about creating a solution that is functional, that performs, and that gets the job done. Architecture and design are often used as the opposite of each other. Architecture is concerned with how things are constructed. You see buildings, you see the buildings. Design is concerned with how things are put together. You see the design, you see the design.
Architecture and design are often used as the opposite of each other. Architecture is concerned with how things are constructed. You see buildings, you see the buildings. Design is concerned with how things are put together. You see the design, you see the design.