Imagine if all Open Source work was done to a standard that allowed integration to become easier. It is achievable in principle but needs an architecture model definition and adherence to it.
A personal dream of mine is that with the plethora of Open Source that exists, all the active projects that are in a silo and all the broken and dead end projects that are no longer needed can somehow be integrated and communicate with each other. If only there was a structure in which they could all be integrated.
Imagine being able to use some Open Source projects together because they followed standard interfaces. Usually to do these needs the services of a programmer to link the data from one project to another, by some conversion, or import/export process. Quite often this isn’t a difficult thing to do functionally but the data may not fit together easily, they may look the same but in different application have different meanings.
One of the greatest strengths in the field of information technology is the conforming of interfaces to common structures, the reusing of common architectures. The World Wide Web relies on these structures at so many levels to deliver the content to your browser and make it look close to what was created by the author. If these common structures didn’t exist, if these common interfaces or standards were never used, the whole of the Internet just wouldn’t exist. Nothing would be able to talk to each other.
We need structure, and our structures need structure. The more structure that exists the more leverage we all have in the world, to reuse all the work that has been put into it to and create something new or evolve it.
The development and thinking of how structures or interface themselves are modelled is an area of absolute importance. By knowing what we need to achieve when we create a new function, of how it can talk to the millions of projects out there existing already, we are given the ability to always add value to the existing knowledge of the world.
It is sad, and something I have seen happen so many times, when so much effort is made by so many different people, in writing the same process, over, and over, and over again. Reinventing wheels is a job that is only useful if the person that does it, only does it because they enjoy it.
I have made no attempt in defining it, because the problem isn’t in defining it, it is in the kind of process that creates the definition of structure that itself needs defining. An architecture creation mode of thinking that itself needs formalising.
Continue reading about Architecture Model Definition to Allow Open Source Interoperability
Whether the project involves hard or softscape, improving your property can be a big investment. But you don’t have to go it alone. Put your money and trust in a landscape architect to get the beautiful results you want.
After deciding on the overall scope of your project, go architect shopping. The best way to do this is to ask for recommendations, whether they be from friends or neighbors, or even a stranger whose yard you admire. Always make sure to ask why they would recommend this person. If you are looking for someone whose expertise lies in designing swimming pools, then a planting expert may not be right for you.
After getting several recommendations, narrow down the list by getting bids and checking out references. Above all, make sure that no matter the person’s area of expertise, he or she has experience in and knowledge of local regulations, construction oversight, and site engineering and building techniques. As with any contract work, make sure that the architect has professional liability insurance for the service you require.
Once the playing field is cut to two or three potential designers, interview them on the phone and ask to see examples of their work. If a designer comes to your home to give you a bid, he or she should also bring a portfolio of their past work. Going through the portfolio ensures that you like the architect’s style and solidifies their work history. A word of advice: Only invite the most promising designers to your property to give you an estimate. This will save time and allow you to make a quicker decision.
Two final but very important considerations: A degree in landscape architecture is always a bonus, so if you it comes between two designers that you like equally well, you can never go wrong with one that has the most qualifications. Second, during the interview establish in the designer’s mind a clear understanding of your expectations, and choose someone that you can communicate this vision to easily. Look for signs that the designer is listening to you and translating your words into your dream landscape. While every designer’s aesthetic is different, you want a designer who is working for you, not for your money or worse, for themselves.
Continue reading about How to Find a Good Landscape Architect