Page 1 of 1

volume vs. density

Posted: Fri Feb 20, 2004 8:28 am
by no_memories
My dad told me a long time ago: "Son, it doesn't matter what you do in life, but whatever you do, do it to the best of your ability."

As with all advancements in society, computer related technology/industry has ballooned into a vast array of fields.

My question is this: Would you rather specialize in a few things (i.e. web layout designer, database admin, programmer, PC technician, network admin, ect.); becoming very knowledgeable and an expert in a given area, or become a general practitioner? (Attempting to learn everything)

Let the debates begin!

:arrow:

Posted: Fri Feb 20, 2004 8:32 am
by markl999
I'd try to land somewhere in the middle ;)
Specialise in one area but try to be as knowledgable about as many other areas as possible.

Posted: Fri Feb 20, 2004 12:29 pm
by Draco_03
depend..if you specialize .. then come the $$$
cuz let s face it..no one can excel in everything..
so te best thing it s to specialize (specializing doesn t mean you can t do anything else.. just that someone else will do it better ;))

Posted: Fri Feb 20, 2004 12:37 pm
by ol4pr0
I would have to agree with markl99
markl999 wrote: Specialise in one area but try to be as knowledgable about as many other areas as possible

Posted: Sat Feb 21, 2004 8:11 am
by Nay
yeah, i'd go with the one speciallity plus a few things you're averagly good at. i mean if you're a 'good' programmer and a 'good' designer, i'd think a long term employer would go for two different 'great' designer and 'great' programmer. though it may cost more, in general, they prefer more employees to shout at ;)

-Nay

Posted: Sat Feb 21, 2004 8:49 am
by jason
From an employers perspective, both types are good.

The guy that knows enough about everything has his place, as much as the guy who specializes. I would rather have a guy that is good in many areas than a guy who sucks in one area and is great in another. And I am not just talking about programming. One of the biggest factors in hiring is a person's grasp of grammar and professionalism. Be a specialist or be a generalist, I don't care; if you can't write, communicate, or listen effectively, you are no use to me.

I expect that if you come looking for a job in PHP, you will know PHP, and if you don't know something in PHP (let's say, LDAP stuff), you can always learn. I expect that. That's default. What sets you apart is if you can speak correctly, how you show up for your interview, how you write (did you actually write a cover page, showing me you spent a little time on it).

Obviously, however, you should specialize in some general area. For example, you could specialize in PHP. There are many sub-categories, but specializing in PHP is a good choice. Then, for your own personal enjoyment, you could specialize in security, credit card processing, or content management. When you go looking for a PHP job, you are specialized in PHP, and that's enough.

But don't neglect your other fields. As I said, I don't care if you are the best coder in the world: if you can't perform in a professional environment, you aren't really worth it.

What I guess I am saying (in a really long and confusing way is) if I am hiring for a PHP programmer, everyone who applies I expect to be fairly competent at PHP (and if not, a test will fix that up quickly). It's not what you know in PHP that will get you hired, but your other assests that you bring to the table.

If you come into my interview dressed well (not necessarily a suit and tie, casual is fine for me), are comfortable and relaxed, and seem enthusiastic and generally a happy person, it makes me feel better about hiring you.

From an employee perspective, markl999 has the best answer.

Posted: Mon Feb 23, 2004 9:58 am
by Derfel Cadarn
The thing with specializing is that you need to stay at the top the whole time! Not one second for a rest, because that's where the competition gets its chance! And when that happens or even starts to happen, you're lost. And hardtime: because that was the 'only ' thing you're good in!!

I generally agree with what's been said by Jason and markl999.

My personal method is:
do not try to know all the answers, just be sure to know where you can find the answers!
8)

natural progression

Posted: Tue Feb 24, 2004 9:20 am
by no_memories
Well, here's my .02 cents worth.

It's been a matter of natural progression with me. At first learning the just basics of how to operate Windows 95 was tough. Since I had no prior experience with computers, this was a whole new ball game for me. After time, I was introduced to Windows NT, various RAID configured servers, and eventually (to some degree) Cisco pix firewalls and routers.

As each learning experience unfolded, I gave it my all to learn it thoroughly so to be able to better perform my job more adequately.

Now I have spent the last year really learning xHTML/CSS designs. The next logical step forward would be PhP and MySQL. So I would say my methodology is to take one or two task(s) on at a time, while slowly progressing into other related areas; without over extending the retention of what I previously learned.

Over time, this can lead to knowing almost everything and being really good at the things you learned prior. In short, nothing replaces the expertise of hands on and the experience of the time involved.

So I would say, IMO, to put 65%-70% in becoming an expert in a given area, while taking the other 30%-35% growing branches and leaves into new territory.

Posted: Tue Feb 24, 2004 3:59 pm
by llanitedave
Everyone has a different ability to either specialize or generalize. Some people are extremely focused, and will specialize in one tiny field to the point that they know all there is to know about it, but not much about anything else. Others get bored very quickly with that, and need a broader perspective.

Each type needs the other.

I find that I'm the "jack of all trades, master of none" type. I can do a fair number of things passably, some very well, but none surpassingly so. I depend on specialists to tell me when an idea of mine doesn't work in a certain category, and certain specialists depend on me to tell them when their ideas won't transfer across fields. I can build things that work, but they aren't always pretty.

What it means for this group is that I might post a lot of stupid-sounding questions -- I'm a geologist by trade, not a programmer, but I've done a lot of databse development as part of my work, and that has inspired a lot of other ideas for things I might hack together.

Don't cry for me, PHP. I'm having fun.