Sitting on a flight from Dallas/Fort-Worth to Orlando for Gartner’s Orlando Portals, Content, and Collaboration Summit, I just observed an event that reminded me of why I believe so strongly that architects ought to cut code themselves. We’re being redirected around the leading edges of a storm line stretching from southwestern Arkansas all the way down to Houston. I am lucky enough to be riding my frequent flier status to an upgrade at the front of the bus, while coach is filled with already-exhausted parents and screaming kids excited to spend “quality time” with the Rat. Yeah, I am pretty happy to be up here.
Anyway, the row in front of me is filled with a familial unit, including 2 kids. I love kids (especially my 2 boys). But more to the point: I love kids who behave themselves. And for the most part these kids behave (if only due to their mobile electronic distraction units). That probably shouldn’t surprise anyone – if you’re in business class as an 8-10 year old kid, it’s because your parents are either very well-off financially, or because one or both parents work in a field demanding a lot of travel, and upgrades were made. In the latter case, these kids are probably still pretty well-off. Children of financially secure parents tend to be children of well-educated, well-behaved parents. Maybe not fair, but there it is.
Because we are being diverted around a storm system, we are enjoying a bit of a bumpy ride. The pilots have turned on the fasten seat belt sign, made announcements about the importance of remaining in your seat with the belt fastened, and our flight attendants have reinforced these ideas. When the plane is rocking side to side, the pilot is telling you to stay in your seat, and your friendly flight attendant is doing the same thing, you should probably stay in your seat.
So, back to my in-flight neighbors. Well-behaved in general, they don’t know how to follow the simple request to stay in their seats for their own safety. It is patently obvious why they don’t “get it” – their parents don’t get it either; they get up and use the bathroom, change seats, and so on, generally serving as a bad example of how to behave yourself as an air traveler. Kids parrot their parents. Fortunately, in the case of in-flight turbulence, most of the time nobody gets hurt, even if they can’t follow rules.
How does this relate to your role as an architect? Well, line programmers parrot you the way that kids parrot their parents. If the rules don’t apply to you, they won’t be taken seriously by the people you’re to nurture and develop. If you act like coding is a big imposition, gifted yet ambitious developers will aspire to a role where coding no longer matters. If you don’t experiment, create prototypes, and research new technologies, you certainly won’t engender interest in same from your programmers. Unfortunately, most of the time, someone or some project will get hurt by such behavior.
I don’t mean to draw an unfair comparison between developers and children (although in some rare cases, such a pure comparison is appropriate). What I mean to say is that everybody needs to be led. In your organization, architects probably don’t lead people in a traditional hierarchical sense – but architects certainly lead by example. How you conduct yourself matters. Choose to spend some of your time coding, even if you believe it isn’t the most valuable use of your time in a pure business sense. In terms of the example and inspiration you supply your organization’s line developers, it matters a lot.
Read Complimentary Relevant Research
Top Strategic Predictions for 2019 and Beyond: Practicality Exists Within Instability
Technology-based change is happening continuously, and most organizations struggle to see the change in advance. Continuous change can...
View Relevant Webinars
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.