5 ms·
Besides, when I hear someone referring to themselves as "I am an architect" (in the context of software development) I usually read between the lines as "I have
by rdtsc 12y ago
Besides, when I hear someone referring to themselves as "I am an architect" (in the context of software development) I usually read between the lines as "I have a rather inflated sense of self and am quite susceptible to flattery".
It is kind of like the milder version of Rockstar or Ninja Developer.
I know it is an official title in many organizations (unlike say titles like "Rockstar Dev IV"), nevertheless, it still sounds a bit silly to me.
- ChicagoDave 12y agoThis is funny. At one client, my team would yell, "The Architect!" in a very sarcastic manner to remind me I was just a developer with a few years on them. I agree, the title can be misused or offer an inflated sense of self for some. A reminder though... I was considered a .NET Architect from about 2004 to 2009. I'm an independent contractor, so I'm always changing clients. In 2009/2010 I would get calls and the recruiters would talk to me about senior developer roles. I would complain, "I'm really an architect," and they would say, "Not anymore. You don't have any front-end architecture experience and your JavaScript background is weak." Lesson learned. You may be an architect for a moment, but to maintain that title, you have to continue to learn and grow. If you don't, you may find out you're just a legacy programmer. I'm sure that can be very humbling.
- yitchelle 12y agoGood points. For an architect, maintaining your knowledge set is important so that the correct decision is made. However, I think it would be done in a contextual manner. Ie, if you operate in the world where Cobol is main technology driver, would you have to continue to keep up your knowledge?
- benjaminwootton 12y agoIt's a bit unfair. It's a job title, a career, and a full time job for a lot of people. Whether or not it's necessary and how architecture should interface with everyone else is open for debate, but it's not really an indication of the persons level of ego.
- tracker1 12y agoI've bounced from UX developer, to systems developer, to architect, director and back to senior developer... I'm currently working in an architect/senior developer role... The title is just that.. it associates with a role you play. I'm designing a relatively large system, and making suggestions towards the tools, technology and implementation (as well as doing a lot of said implementing). I can't speak for most... but for me, it's the position I'm in... Of course my role is much closer to that described in TFA... which is what being in a smaller organization calls for. I like solving problems, and developing solutions.
- firebones 12y agoI was getting ready to undergo a surgical procedure once. The doctor looked at my chart and saw I was (by title) a "software architect". He asked me to clarify. I described what the job entailed. He scoffed, "So you're not a REAL architect," as though I were inflating the title my organization had given me. Didn't really give me any reassurance as he wielded the knife.
- kragen 12y agoDid you tell him he wasn’t a real doctor because he lacked Ecclesiae declaratio?
- pavlov 12y agoWell, your doctor did have a point. In most countries, "architect" is a protected title. Architects are required to register and they must meet very specific requirements. If a hardware repairs guy adopted the title of "Doctor of Computer-Medicine", I think most of us would find it silly. Personally I agree that we should let real architects keep their title rather than muddy it with the confusing baggage of our business.
- icedchai 12y agoHah. It's true. We're not real engineers either.
- dwenzek 12y agoYes, there is a risk to be boastful. But the risk is shared by many positions and roles. It's not enough to say I'm an architect or a full stack developer or UX designer, there are a lot of skills and attitudes to have along the days to fill plainly the role in a team. It's why, I totally agree the post. To fulfill the architect role, you have to be on a daily basis with the team, to design, develop and debug with them. This is not about being a Rockstar, but yes, this requires some broader and smarter vision on how the whole system is being developed. And this implies responsibilities too and even a bit of humility when things do not go like expected: it is at these difficult times that we can judge whether you deserved the role. Besides, titles have their importance. This is maybe a pity, but, for sure, you don't have the same audience from the management when you are introduced as a software architect rather as a developer. Same thing, when you are looking for a job. I'm a freelance developer with 20 years of experiment and I introduce myself as a software architect even if I'm looking for contracts where I will be plainly involved in development tasks. Each time I failed to do so, I put myself in situation with no chances to use my skills and to help the project at the level I could have. On the contrary, with an architect hat, I have been often welcome with some suspicion ("how can this guy fix the mess we're in?"), but this gave me the opportunity to work effectively with all team members and to truly help them.
- keithnoizu 12y agoNice description. On a side note but related, I really think one of the major difference between a developer versus an architect is having strong grasp of how components can fit together and impact overall costs, quality and timelines for a project even if you aren't familiar with the specific details of those components. For example if you need to design out something highly distributed you don't necessarily need to be proficient in erlang, or scala + akka, or clojure before you start but you do need to understand the pros and cons of each system, the underpinning philosophy on how they work and basic behaviors of the solutions in terms of speed to develop, benchmarks, known scaling problems, trouble spots etc. Sometimes you need to use the right tool for the job even if you don't know the tool yet. Sometimes that means taking a deep dive to get to know the technology, talking to experts on the technology and fitting their feedback into the overall picture of what the system needs to do. Which is a very different skill set then being able to pack as much functionality as possible into an MCU, or improve average performance on an algorithem, or being able to rapidly construct a component. Which is why I advertise myself as architect and not as systems developer, or ux guy or full stack engineer. It's the type of work I enjoy doing, and it's the work that clients get the most bang for their buck out of me for their retainers. It doesn't mean I think I'm a better developer than non architects. In a lot of ways I'm not, but I does mean that I think (rightly or wrongly) that I am often better at sleuthing out the rough behavioral characteristics of components or technologies needed for a project and knowing how to leverage that high level understanding together for designing or improving a project.
- keithnoizu 12y agoMaybe. Although I think there is a distinct mindset difference between someone who is a really good coder versus a really good designer. Personally I refer to myself as a software architect, partially because it's one of my job titles and partially because laying out large multi-component systems comes very naturally to me and is something I seem to be more proficient at than many developers I meet. Meanwhile when it comes to actually sitting down for implementation work I'm just on the average to high-average side of things. Finally when it comes to algorithm design and analysis I'm pretty mediocre. Although, I hope, that is mostly from never having to work in that area very much. I sort of think it boils down to if you are a forest or trees sort of person. Normally I approach writing code as modules, then classes and then methods working my way down to implementation instead of going the other route and starting with methods and building up to classes and modules. So when I sit down to start a new project I normally plug in most of the classes and interfaces first for the sections i'm working on and then implement down from class design to coordinating logic to specific methods (tweaking my interfaces as I go). Meanwhile I know some other developers that take the opposite route and start with low level implementation and work from there up to coordination level stuff. They can't really feel out the big picture until they have a solid grasp on the low level implementation details and I can't really feel out the low level implementation details until I have a good idea of the big picture in my head.