And I feel a responsibility to make,
make the experience positive for as many people as possible and
for also as a place for wildlife to, to thrive.
>> Mm-hm, mm-hm. >> And, it's something I
feel passionate about.
>> So in software engineering we tend to design our code,
design our programs because, before we go ahead and, you know, actually code them.
So is that somehow equivalent to what you do?
What an architect does?
>> Absolutely, a whole a big part of the architectural process is,
is really understanding what that brief is from your client.
>> Mm-hm.
>> And understanding the context, the constraints and
really exploring everything that you want the building to achieve.
And the actual design of the building comes right at the end when you understand
all the, constraints and opportunities- >> Mm-hm.
>> That you need in that building.
>> This brings me very nicely to the topic of, what we call in software engineering,
specifying your requirements which is basically, I think, what you described.
The, the constraints and the, I don't remember the term you used, functionality?
>> Opportunities. >> The opportunity to use, yeah.
>> To use functionality.
>> Yeah, so. >> Yeah, and so
It always sets the project brief.
>> Mm-hm. >> Really.
>> And how do you gather your requirements in that sense?
Who do you talk to and what do you, what considerations do you make?