IT Archtiect - different types

ctai010

Hi. Sorry for slow response.

Firstly IT architect is a very generic title, in some cases architect is no different to senior developer. And there is some very specialised architect roles out there where you are only expected to work on a very specific area / project.

So architect don't 'need' to know a bit for every domain. But the more you know the better, software solution is rarely isolated in one domain (at least in enterprise context).

Generally speaking, because you are the architect, people will expect you to know everything and have a solution for every problem. Sometimes you’ll get put under spotlight and expected to solve the problem instantly. Have multi-domain knowledge maximise your chance to do well. If you are able to consistently resolve problems quickly and effectively, you’ll quickly earn respect in the organisation and build a reputation among your peers. So to answer your question, how far you need to understand? You need to understand to a extend where:
1. Able to design the solution where you can justify that it will work (regardless it's single domain or cross domain) and able to convince business to spend big money on your solution. You may get challenged from all angles, technical, financial, future-proof, architectural elegance, and general good software engineering principles and design patterns.
2. When something went wrong, you can jump into the shit hole, find the root cause of the problem and come up with a idea to fix it. In a ideal world Architect just give instructions and let the dev/op team to fix it. But we don't' live in a ideal world, sometimes architect need get hand dirty and fix it yourself. So both development and OS / Unix skills is extremely handy.

Now, even if your role is, for example, WCM Architect. But when you work closely with Project Manager / Business owner / Senior manager, they don't know (or care) about any technical details. If there's a problem, they'll expect you to fix it, end of story. And for instance if you are able to trace the problem to integration layer, in a perfect world you should able to just hand over this problem to integration team and they should be responsible to fix it. But again, we don't live in perfect world.

Sometimes the downstream team can be extremely unhelpful for all sort of reason. If you also know a lot about integration, you'll able to spell out to them exactly what went wrong, where is it happening, proof that this is their fault, and how to fix it. This way you'll make your PM happy, and earn respect in the organization.  

Having said that, the soft skills of how you handle the problems is actually more important. If you have the ability to handle tough situation with ‘silky smooth’ response, you’ll also do well as architect. An essential skill for top architect is able to make everybody feel the problem is solved, but actually we are still in square one - nothing is resolved. And the sad truth is talker actually progress further than doer. So there will be people just talk their way to a very high level role without any real skill / knowledge. That's just life.

117wik

ctai010 发表于 2015-4-14 21:32
Hi. Sorry for slow response.

Firstly IT architect is a very generic title, in some cases architect ...

Hi,

How long have you been in the industry, how did you get to where you are today (sorry if someone has asked the same Q already).

I am someone that work on the other side of the fence (i.e. not a developer, started as support and move up to senior, tech lead, ops manager etc, in system & infrastructure ==> network & firewall ==> security). I have done a lot of design and architecture work on the network security side of thing, my title was never really an architect (they wanted me to go to architecture team multiple times and i refuse), however i pretty much architect, design and build up all the security capabilities current company is using. Currently working as a manager with 15 direct reports. 15 years IT experience if anyone ever wonder.

We can almost start a AMA (ask me anything) thread for people wanting to know how to get into IT, how to career progress etc? :P

If you work in town, and keen for a coffee sometime, drop me an IM (always good to get to know fellow chinese working in different part industries).

ybbest

ctai010 发表于 2015-4-14 21:32
Hi. Sorry for slow response.

Firstly IT architect is a very generic title, in some cases architect ...

Thanks for the reply , it definitely helps me to look what I need to work on for the next 3 to 5 years.

Eastpark

117wik 发表于 2015-4-15 08:13
Hi,

How long have you been in the industry, how did you get to where you are today (sorry if some ...

I remember you. Seem you are also a living fossil in IT industry just like me.

How do you value CISSP in your work?

117wik

Eastpark 发表于 2015-4-16 16:05
I remember you. Seem you are also a living fossil in IT industry just like me.

How do you value  ...

It really depends on which field of security are you in. If you are in Ops, becoming CISSP certified doesn't make you a better engineer or analyst. I still encourage most people to do it as that's almost the only certification recognized by recruitment agents.

Who are you again? (i don't recognize your online forum handle). Do you work in security too?

xp_theman

AMA Question 1:

which skill is most important, if your goal is to earn more.

Eastpark

117wik 发表于 2015-4-16 16:56
It really depends on which field of security are you in. If you are in Ops, becoming CISSP certifi ...

You were recruiting some guys on the forum and said you are from Security background. That's why I remember you. I am kind of a security practitioner, people are calling me security consultant, though I don't think I am. :)

I work on application level only, including Single Sign On, Identity and Access Management etc.

ctai010

117wik 发表于 2015-4-15 08:13
Hi,

How long have you been in the industry, how did you get to where you are today (sorry if some ...

Hi there

Yeah I work in town but flying in-and-out a lot recently. Caught in middle of few crazy projects recently.
Def happy to catchup when I'm back to normal schedule.

I have 10 years exp. Start as developer, moved on to team lead / tech lead, and eventually luckly enough to move to architect role.

For me I set my goal to be a architect very early in my career. I changed my job ever 1-2 years for the sole purpose of build the right expereince to help me in the long term.

a AMA topic sound great, and everyone will be welcome to chip in.

ctx2002

这个题目好，有空能出来谈谈吗。