Browsing all articles in Professional Development
Mar
7

What’s it take to be a Software Architect

Today on twitter, I noticed the following tweet fly-by:

It struck a chord with me. A few years ago I got into an interesting conversation with a Security/Database Architect and a high level Systems Engineer regarding what it means to be a Software (or Systems or Enterprise) Architect. Long-story-short, the Engineer had been burned quite a few times by self-made Architects (think entrenched “Ivory Tower” Architects) while the Security Architect had actually met other Architects with passion, technical know-how, and the desire to truly develop value within their organizations. After a bit of thinking, I came up with the following definition:

Becoming an Architect is an exercise in personal, technical, and professional growth.  The role of Architect is multi-faceted and includes disciplines such as: Leadership, Stewardship, Technical Knowledge, Communication, Management, and Planning.

An Architect is a leader, first and foremost.  Not a Manager and not a guru.  An Architect is someone with the technical knowledge, vision, imagination, and the sense of humor needed to negotiate the difficult path towards the success of a project that may touch every level of an organization.

@JuanKRuiz asked:
No, I don’t think age is a factor.  Becoming an Architect can be equated with becoming a master artist: some are born with a gift for their specific area of expertise and can communicate their art in a meaningful way.  Others spend their whole life pointing at a canvas only to learn that to touch the heart of the community one must share their passion.

So, can you be an Architect but not touch the technology?  No -  there’s a reason doctors in the US must go through a residency period.  Can you be an Architect and be a guru?  Not necessarily – most of the experts I know are “heads-down” developers.

I still think that is a fairly straight-forward definition and would follow it up with the article from Wikipedia: Software Architect.  This article from Ted Neward is an especially excellent outline of what it means to be an Architect.

My advice to those seeking to become Architects?  Choose a path: Systems, Integration, Software, Enterprise, Database, among many others.  Learn, practice, and understand the technologies you are working with.  Share that knowledge and express your passion, but do not do so to the exclusion of others’ opinions.  Learn what it takes to be a leader.  And finally, keep a sense of humor.

Jan
6

Who’s on your networking bucket list?

About three years ago, I decided to get into social networking.  No, not Facebook or Twitter.  I mean real, live, old-school, networking.  I’d like to pretend it was an active decision, but we all know the truth (more on this later).  Regardless, I set up a meeting with an old friend, Brian Kelley (web | twitter) — who is a community leader in the Sql Server world (as well as security, youth ministry, and a host of other things) — to get his take on how to get started.  He recommended looking into Never Eat Alone by Keith Ferrazzi.  It’s a great book and a quick read, I’d definitely recommend it.  From there, I went on to have a -lot- more lunches, go to more conferences (and host a few), extend a few greetings to people that I’d never have approached in the past.

After while, I realized I needed a little more direction and to set a few goals.  I began planning how I would attend a conference and use the resources at-hand.  After meeting a few people that I thought I’d never meet in real-life – sometimes completely by accident – I decided to make a list of people that I’d love to have lunch with or otherwise just sit and chat: the Networking Bucket List.

What is a networking bucket list, and why should you care?  Anyone who has attended a conference, met with a customer, or even gone to the gym has done some kind of networking.  You can’t even go to the store without making contact with at least one person (unless you’re a huge fan of self-checkouts and they -always- work for you).  Why not set some goals regarding networking?  It’s not hard, and you’d be surprised how something this simple can be incredibly fulfilling and rewarding.

Here’s just a few people on my list that I’ve met:
Scott Hanselman (twitter | blog)
Andy Leonard (twitter | blog)
Andy Warren (twitter | blog)
Brian Moran (twitter | web)
Margaret Weis (twitter | web)
James Callis (twitter | web)
George Takei (twitter | web)

And here are a few people still on my list:
Buck Woody (twitter | blog)
Steve Jones (twitter | blog)
Brent Ozar (twitter | blog)
Sebastian Marshall (twitter | blog)
Steve Kamb (twitter | blog)
Joel Spolsky (twitter | blog)
Oren Eini (twitter | blog)
Keith Ferazzi (twitter | blog)
Seth Godin (twitter | blog)
Jeff Atwood (twitter | blog)
Rick Strahl (twitter| blog)
Kelly Sommers (twitter | blog)
.. and boatloads of others!

Are you on the list and wondering why?  Drop me a line, let’s get together!  Don’t see you name up there?  Drop me a line anyway, I love hearing from new people!

Networking is definitely an art.  Luckily, you don’t have to be Picasso.  It’s a skill you can build and develop, and unlike snow skiing, you don’t have to worry about a trip to the emergency room..

 

 

Recent Tweets

Archives

Categories