I started a LinkedIn group. It has a grandiose title: Future of Architecture and the Built Environment. You can join the group by clicking here. Why did I start a LinkedIn group when there are already a million billion groups to join. Well: The Main Reason is that there really isn’t a group focused on the things I want to discuss and share. I want a place to share articles
Doing measures of existing conditions in Minnesota usually meant one of two things: a hot summer day with no air conditioning, or sub-zero temperatures and snow. Plus if the site was outside the Twin Cities (Minnesotans love their cabins): a couple hours of driving and a marathon session trying to get everything in before dark. Crawling around buildings with a tape measure, a pad of paper, and a bunch of
Designers masquerading as architects is a topic within the profession that bothers me deeply. I have had numerous co-workers (architectural educated/trained designers) publicly call themselves architects at cocktail parties, around their peers, to the general public… One even went so far as to be published being referred to as an architect in printed media. I contemplated calling the California Architects Board and filing a complaint against him as he was working
I talk a lot about the future of practicing architecture. I’m really interested in how our tools and processes evolve. I am curious about what common frustrations we will soon no longer need to deal with. A lot of these changes are subtle. Others are a bit more overt. Here’s one example that comes to mind: the switch from film to digital cameras when photographing existing site conditions. Are you
I’ve now written three articles for the AIA CRAN Chronicle. The first two articles gave me a chance to talk about some different things than I usually do. Or than I usually did. Both those topics have now migrated into my regular writing as I evolve the blog from just ArchiCAD and BIM to all the various aspects of being an Architect in the 21st century. My most recent article
Jared’s Note: As should surprise no one, Kristian’s post comparing ArchiCAD GDL vs Revit Families caused quite a stir on both sides of the ArchiCAD vs Revit divide. I am both thrilled and honored that Martijn de Riet has written a wonderful response to Kristian’s comparison, from the Revit side of things. Martijn is one of my favorite Revit pros on Twitter (more so after reading this post while doing
Jared’s Note: Jeremiah originally wrote this post for his own site. I asked him if I could share it on Shoegnome because it fits so well with the recent discussions on the use of the word architect and what to call people who work in the field, but aren’t licensed architects. Turns out Canada has a nice solution already. Jeremiah graciously said yes to letting me repost and also promised
Recently I spent a great deal of time working with Revit Families (RFA’s) to determine their capabilities. I approached this endeavor with no bias; as most mathematicians will tell you, it is all about potential with personal preference a liability. Though I could write a book on the topic of ArchiCAD GDL vs Revit Families I’m going to be as brief as possible and hopefully expand in later posts. Basic
This is the second post dedicated to all the emotion and confusion surrounding the word architect. In all fairness, I could have used the person I singled out in the first post as the non-architect instead of Carlos for this post. The results would be pretty much the same. But I wrote this article first and I also know Carlos, so there’s some added personal touches that I find poignant.
