r/architecturestudent

How's the acer nitro v15

i5 13th gen 13420 H, 16 gb ram, 512 gb ssd, rtx 4060

For architecture?

I'm a little concerned about the processor.

im struggling with my 1st year at uni here, ive been given the task to create an "abstract" model that rhymes with (my theme) outward and observing. I get what my lecturer mean but i cant seem to execute what theyre trying to say. My model always end up getting called " this is interior design", and i failed to meet the reuqirement a lot. How should i improve ?

I'm almost 5 years into working as an architectural technologist, I picked my degree almost completely unaware of the career path. For years I was convinced I wanted to be an engineer. College introduced me to the career of Architecture. I decided to go to university. My choices were 7+ years to become and Architect or study Architectural Technology for 3 years and do a placement year in between. At the time, it was a no brainer. Looking back, here's what I'd tell my 18-year-old self.

What it actually is (in my experience):
As a generalisation Architects tend to lead on concept and design intent. Technologists tend to lead on making it buildable: junction details, material specs, Building Regs compliance, coordinating with structural and M&E, and answering the "okay, but how does this actually go together?" question. On a lot of projects the overlap is huge. I know Technologists who are fantastic concept designers and Architects who are extremely technical. On other jobs it's very clear who does what. It varies a lot by practice.

What a normal week looks like for me:

• Checking, coordinating and commenting on fabrication, manufacturer or consultant drawings
• Reviewing building regulations and regulatory compliance
• Attending DTMs & meeting with contractors
• 2D/3D drafting on CAD software

The less glamorous bits:

• Less of your name on the "design" side, more of it on the "this is why it didn't leak" side
• Plenty of people outside the industry (and some inside) don't know what an Architectural Technologist is
• Liability is real. Your detail gets built. That's a good thing, but it's heavy sometimes, it needs to be right. Having a good support network within your practice is invaluable.

What I like about it:
I love being the person who helps solve the problems. Looking at all the moving parts and understanding what needs to change and why. Evaluating why trades aren't coordinating, where the discrepancies are, and more importantly, how to solve it.

If you're choosing between architecture, architectural technology and building surveying - anything in the built environment:

The best advice I got was to ask practices what a graduate actually does in year one. The job titles are less useful than the tasks. Networking is a fundamental skill that university does not teach. It is vital for learning about the industry and roles within.

I'm sure people here have different experiences, especially architects, surveyors and other construction professionals who work with technologists. What did I get wrong or oversell?