regurgitate != knowledge explore+test = have_an_opinion requires_work = 1 sed -i 's/no_time/make_time/g' /my/schedule
I was never one of those little kids that told mommy and daddy what they wanted to be when they grew up. I didn’t even start officially working in the “IT” industry until 1996. I just kind of fell into the career because I enjoyed fixing other people’s computers all the time. The closest I ever came to wanting a particular job as a teenager was being an architect. You know the traditional kind like the dad the “Brady Bunch”? In my mind an architect was always an engineer with a big desk, rulers, calculators, knowledge of complex math, physics, and materials science. They also were visionary creative types that could come up with amazing designs like the Chrysler building, the TransAmerica Tower, or Falling Water. In my mind these architects could do designs in an office, but also go out in the field and do some of the engineering work themselves.
Fast forward to today when the job title of architect can take on a variety of constructs: software, infrastructure, political, health care, network, security, traffic, etc. The job title has morphed into any type of senior design position in some fields. I myself am part of this trend with the job title “Infrastructure Architect” currently. However, due to my admiration for the “traditional” architect job, I feel an obligation to at least try and transfer my ideas of what skills translate from the traditional architect into the modern IT infrastructure engineering space. This has been the cause of some stress for me over the past three years. I will freely admit that today I worry about what it takes to be proficient in this modern “infrastructure as code” world. After having a few beers, I sat on my porch and tried to jot down some notes on what troubled me personally and what the causes might be. I think I have narrowed them down: personal expectations versus market expectations, time management, and ambition.
Personal Expectations vs Market Expectations
I would be lying to you if I did not admit that I struggle every day personally to try and meet what my own expectations are for an architect in the infrastructure space. Infrastructure has several “silos/towers” that represent some traditional capability areas. These are things like servers and virtualization, storage, networking, security, databases, service buses, application hosting, as well as monitoring and performance metrics. Having deep knowledge in more than one of these towers is what I would say an architect should have. Due to the amount of knowledge needed to know multiple silos this can take years of work. In my case this journey has spanned over 17 years since 1997. There is no formal curriculum so to speak for “architect” so it kind of materializes via technical jobs you take and a little serendipity.
My architect journey kind of materialized like so…
- Hardware phase (servers/PCs/peripherals)
- DOS phase (batch programming, emm386 fun days)
- AS400 and VAX/VMS phase
- Token ring and ethernet (10base2-10000) phase (jiggle it just a little bit)
- Novell phase (3 to NDS)
- Windows phase (over a decade of windows troubleshooting madness)
- The whole certification industry treadmill phase (mcse/cne/ccnp/blah thank goodness this is dead)
- The DBA phase (SQL server and Oracle)
- Network engineering phase (ethernet to satellites to sonet rings to mpls and vpn)
- Unix/linux phase (Solaris, Slackware, mandrake and RHEL)
- The Perl/CPAN/Sourceforge phase
- The php/html/css everything phase
- The slashdot addiction phase
- The AWS and Rackspace IaaS phase (ongoing)
- The OSS and Github revolution phase (ongoing)
- The ruby and cm transformation (ongoing)
- The Hacker News addiction phase (ongoing)
The presumed belief is that the more you stuff you learn the more valuable you become from a holistic experience lens. This is likely true in that you learn over time how multi-level dependencies and other design issues can affect resiliency, performance and scale. Eventually the need for this kind of holistic knowledge was enough that the modern job titles of “architect” in the IT space arose. In some ways, the architect position is seen as a more senior role (even though many organizations don’t have an HR job code with architect in it. To be sure, I’m ambivalent on whether the job title even needs to be official). The flip side is that going deep in n+3 or more capability silos becomes increasingly difficult to do well given the other responsibilities that often fall on the shoulders of an “architect”. The funny thing is that these “other responsibilities” often begin to take upwards of 70% or more of the time of an architect type person. There is a constant balancing act going on where one foot is on the hands on (development/testing/research) side of the fence, and the other foot is in things I call CCE like (collaboration, communication, and evangelism) or leadership side of the fence. The latter half inevitably results in meeting hell.
Why do these other things increasingly take over the time of an architect type person? I have thought a lot about this, and I believe it likely boils down in part to the holistic experience thing (others may only have a single silo view of the world and hence need help with understanding about why something could be better another way) and partly because the architect (even though the role may not even be official on paper) is saddled with the overall responsibility that things work cohesively within a given capability area. When someone has a job responsibility to “make things work” together, it implies that they ideally understand and have proficiency in the technologies involved. This gets increasingly difficult the more technology areas you are expected to know. I will be the first to admit that this knowledge responsibility only works when a federated model of architectural ownership is in place. By this I mean that having multiple architect roles within infrastructure is important and many more within an enterprise is absolutely a necessity. The old mindset of someone having the job title of ‘Enterprise Architect” is a farce. It is a feat of impossibility if you expect to have actual architecture efficacy in an IT organization. The archaic “ivory tower” approach to managing architecture in a top down model is just not feasible. To be sure, I don’t think it ever was actually effective; and so in my mind the “Enterprise Architect” is dead and has been for a while. The point I want to make here is that there is just too much to know to be truly effective outside the limited scope of a major capability area. The ability to be hands on and also do requisite CCE I feel is best within a more manageable size capability area.
“The ‘Enterprise Architect’ is Dead”
Pretty much since 2007 the infrastructure as a service revolution inspired by AWS has been a massive snowball of change. This change has and continues to be awesome. I have wholeheartedly embraced it and have been taking part in the transition for years now. The changes have in part re-invigorated the popularity of the open source movement and with it has come unparalleled opportunities for startups. It has inspired the creation and success what has become a literal tidal wave of open-source projects on Github. All one has to do is look at Hacker News on any given day and see that some new project was announced that “fixes this” or “closes this gap in functionality”. One could argue that a business could start and run without much if any proprietary commercial products today (short of the client devices). It is an amazing time that we are living in that maybe 30 years from now will be mentioned in history books as the tipping point for mainstream open-source adoption and innovation. All of this is super cool, especially if you are a small to medium sized startup, and can get everything you need infrastructure-wise from something like AWS or Rackspace or Digital Ocean using an API. Even better, modern configuration management and containerization sits on top of these IaaS platforms and allows you to install packages and manage build outs rapidly using “infrastructure code” as well. If you are a software developer and need to be productive in the infrastructure space (even if you don’t know it well) you can do so effectively with just the knowledge of a given API.
Marc Andressen’s famous callout in 2011 that “software is eating the world” has never been more true than in the IT infrastructure space. I have felt it every day for the past 5 years now. The challenge, specifically for me, is staying productive, efficient, and helpful in a space that is increasingly more software. Software development to be precise. Let’s be honest, even with the cloud NaaS revolution, most enterprises still run the bulk of their infrastructure in house. Part of this is dealing with legacy apps and the baggage they bring, part of it is a pure cost play where the bandwidth and storage used by an enterprise can still be less in house than using AWS or Rackspace, and finally, part of this is security and performance concerns. So with many enterprises trying to take part in this “infrastructure as code” revolution while still maintaining significant internal hardware, the need for someone to know both traditional infrastructure management and new code based approaches is critical. To be sure, a software based management abstraction layer (api) is increasingly meaning that the work an an infrastructure architect does is more dev and less ops. Since I want to be an architect that does both hands on coding and traditional architecture work (to remain relevant), I need time to focus on development. Getting the time to do the work and focus is a real challenge. But dude, the thing is I have to do this to enable infrastructure to provide any value for the app dev teams in the enterprise. If I can’t help make internal infrastructure as easy to consume and programmable as Amazon AWS, then the Devs increasingly see me (vis-a-vi infrastructure) as a blocker and I don’t blame them. At least for now, because of the need for supporting legacy and all the painfully inflexible COTS packages (hello Oracle), Infrastructure ends up also having to play a type of luxury one-on-one concierge service for app teams. I don’t know how long this “concierge” style need will last, but I’m gonna be pushing as much self-service infrastructure via API as fast as I can make it happen. Things like Openstack and SDN are making this possible for me, but doesn’t address everything needed.
Pressure on Myself in the Valley
If you buy into the software will eat the world argument (and I feel like I do) then the question becomes: How can I be the best at my job as an infrastructure architect?
- What is valuable work?
- What are valuable skills?
If the answers are only writing code, then there are lots of questions I have the keep me stressed. First off, is this thing endemic to Silicon Valley only or is more widespread? I feel like the mass transition is already well underway. Right now the change is already prevalent in Silicon Valley. There may be a three to five year delay before it hits middle america, but its probably coming. But how will these changes (for all their merits) scale? Are all the old sysadmins that can’t code pretty much SOL? I think perhaps so. I said the traditional sysadmin was dead in a paper published last year, but I wonder if middle america can keep up. I mean this stuff is not exactly easy. Is this an example of the robotization of everything? If everyone is writing code, then who is spending time communicating and collaborating (remember this takes a buttload of time) and who maintains the code down the road? What about all these small IT consulting companies that handle outsourced IT for the space between mom and pop businesses to the enterprise? Is the “Geek Squad” of the near future going to need staff that are polyglots understanding CI pipelines and Git? Writing code takes a singular level of focus and time that is already a challenge for even seasoned developers. The needs for the people (often architects) that sit at the event horizon of software development and collaborative design and communications won’t simply go away. The difference is now I think they need to be doing both. Architects, as I have mentioned, often have a lack of time due to the immense gravitational pull of CCE (collaboration, communications, and evangelism) that needs to be done with all the stakeholders/customers of infrastructure. If I were to surmise that my ideal job time split between “hands on keyboard” time coding and CCE were 50/50, then I’m gonna have to change the way I manage my time. The balancing act of hands on work and meetings is just way fracking hard. I may have to start being more selfish with my calendar and time. I’m just not sure how best to solve this yet.
“The balancing act of hands on work and meetings is just way fracking hard.”
Another issue I struggle with is the perception that the ability to do both hands on development and CCE or leadership well is commonplace in the valley and elsewhere. This is buttressed by the examples of exceptional people like Elon Musk, Sergey Brin, Larry Page, Mark Zuckerberg, and Max Levchin as bellwethers for how to work. I feel like these guys and others like them are truly exceptional people. They garner media attention because they are success stories, but the translation in the valley is perhaps that their skills are as obtainable as riding a bike. I feel like this is just not the case. I don’t necessarily want to lend too much credence to the Malcolm Gladwell “10k hours” argument, but this shit is just not easy. The competition here is high, especially if you truly want to make a difference and want to think of yourself as good at your job. Perhaps I am just too hard on myself, but here lately I have gotten to where my blood pressure rises, I get hot, and feel overwhelmed when I read HackerNews. Sometimes I feel like all the article titles are flying by my eyes like data in the matrix making me feel more inadequate by the minute (the Oracle said I was not “the one”). Is this is the bane of type A personalities who want to be the best and are competitive? I rarely think of myself as an “expert” at anything even if I am kicking ass at something. Sometimes this personality trait of mine helps me and drives me to be better, while other times it exhausts me and gets me down. Am I a little out of balance with incessantly wanting to be a better programmer, a great speaker and leader, a great skateboarder, up to date on all the latest geopolitics, and be able to write eloquent comments on HN? Maybe. I might need to wean myself off HN for a little bit for my own mental health. I think when you start to get jealous of the gas station cashier for having a simple and less stressful job, it might be time to level set. Than again, I just want to do a good job in this rapidly changing infrastructure as code landscape. So what is a modern infrastructure architect? Is it a software developer, a shoe salesman, or a crisis negotiator?
Wait, sorry I have another meeting to attend. Let me know if you approve and merge what I perceive to be a market pull request.
I decided to take my many years of skateboarding love and pour it into my own new company. So, after a lot of of hard work, product development, and testing, I created of San Francisco Skateboard Company (SFSC). There are so many things I want to do for the sport of skateboarding and this company and brand will provide me a way to make things actually happen. I plan to do a lot and I will be sharing it with you here. I would really appreciate your support for the company. Try out my products and let me know what you think.
Check it out here: San Francisco Skateboard Company