Hands-on experience on the .

NET platform with Architecting/ Designing experience

on at least 3 .NET full life cycle projects
Hands on experience in .NET 2.0 / 3.0 + Database + AJAX, Web Services, Design,
Hands-on experience on the implementation of .NET migration projects (tool based
etc.),
In addition of technical depth and breadth, architect requires excellent communi
cation, interpersonal and leadership skills
==>>
What fascinates me the most in this IT development field? Hmmm... Actually I don
t need to think so much and try to give a polished answer. Honestly, I've always
tried to automate routine tasks that I do on a daily basis. Can I say something
like Pet Projects. It all started when I got my first hands-on on Visual Basic.
That's when I really saw the ease in developing applications. I used to do some
small stuffs, that helped me a small way. But yes, it was rapid development. Al
so it was easier to develop.
Programming, it was always a nightmare for me, because I didn't know C, C++. I t
hought not knowing these 2 languages meant I don't know programming! As blunt as
that! It was a shame that I didn't know these 2 languages. In fact I did try to
learn, but the concept of pointers, references etc drived me crazy. I couldn't
grasp the concept. It was all virtual, more of a mind job. I was not tuned for t
hat.
As a kid, I remember very well; I could easily fix a broken clock or fix a fan b
y joining the correct polarities or kick-starting a choke from an electrical tub
elight. Experimenting with electricity at the age of 12 was not ordinary. Atleas
t I did not know kids who could do such a thing. Think about a small alarm clock
, the same one that we use to wake us up during exam days. I was so curious one
day that I started seeing the mechanics of it to fix a erroneous one. I slowly d
isassembled it and I started pulling each & every part one followed by the other
. But I made sure that I kept the parts in the same order as it was assembled in
side the clock pastic case.
After a while I realized that I almost pulled everything out and I was kind of s
cared that I may not put it back to work. I almost decided that I'm going to dum
p all this junk, giving up without a second thought. Moreover, it was already du
mped by my people at home, so it wouldn't have made any difference if it lied in
the garbage bin.
But something encouraged me to put it back. To fix it, to give it a try! I then
started slowly. As I progressed, I felt confident that I could achive it. As I c
ontinued fixing it, the small parts functioning together amused me. It was a sma
ll gadget, but yet the discovery process that I went through while assembling it
was an awesome experience.
Coming back to my development world, I did get a chance to work on ASP during th
e year 1999 as it was a hot technology. I did some self-learning by creating sma
ll applications here & there. Trying to understand on how it all worked to enabl
e applications to be hosted on the web.
ASP.NET was the next big thing on the .NET framework. Currently we get to see .N
ET 4.0 framework.
I was more of an application development person, with the knowledge on designing
only on the modules that were assigned to me. With this mindset, I wasn't even
aware of the difference between Designing & Architecting.
Now that I think I have the understanding of the difference, I was more interest
ed in gaining hardcore experience in designing/architecting.
My first stint was @ Intel where we were trying to re-design one of the commonly
used application. I was trying hard to get my design pattern knowledge straight
. Everytime I used to question myself, I used to vomit out a bookish explanation
of what that pattern meant and supposed to work. I googled & searched throughou
t the internet to understand the functioning. I should've realized that my appro
ach was wrong. In fact whenever I used to refer again on how a design pattern wo
rked, I should have realized that I was not learning it the right way.