"Mario T. Lanza" <> wrote in message
news: m...
> I have a question that deals with one's resume and the skills it
> offers. Imagine that you are a firm looking to hire someone to do a
> very high-end site. You are not as concerned with the precise
> technologies that your candidates have as much as you are concerned
> with their ability to produce a professional, polished result that
> meets your requirements.
This depends...
If you are going to work for a web design company they will most likely have
some preference for procedure and operations. This is just practicality...
if they have 10 people working for them and 9 know PHP and you are the only
guy who knows ASP and something happens to you (you quit, you are sick, you
are on vacation, you are falling behind in your workload) they can't assign
a PHP programmer to go over your ASP code.
If you are going to work for a big company in their web design department...
then again they will most likely want skills that match their needs. Whats
the point of hiring a PHP programmer if their current website is written in
ASP or ColdFusion?
> I am evaluating my skillset and determining what areas lack and where
> I should focus my educational efforts to fill the gaps.
You might be better off trying to master a few things instead of being a
"Jack of All Trades"
> The point is, a person can have one skill (ASP) or the other (PHP) to
> meet one particular need of web design and development (generating
> dynamic database-driven content and online applications).
If you are doing a freelance job for the guy down the street who owns the
autobody shop and wants a website... then he is definitly not going to care
what server side language you know (nor is he going to know what you are
talking about if you even bring it up). All he is going to care about is
what it'll say/look like, how much it costs to build it, and then how much
it costs to keep it up on the web
> With my current skillset I regularly make use of:
>
<snip>
>
> As far as I can tell, I have been able to meet the needs of the
> clients I have worked for using this skillset.
For the most part, what you need is:
- a server side scripting language
- knowledge of database access and SQL
- know how to use a graphics program
- HTML
There is still alot more to it than that,but with the above you can pretty
much cover all your bases.
> Therefore, moving on from ASP to ASP.NET seems like a wise step
> forward from obsolescence, but only because ASP.NET in not an
> equivalent technology but a superior one.
In this business its hard to see anything ever becoming obsolete. Maybe
"old" and "dated" but 5 years from now there will still be designers who
check what their site looks like in Netscape 4.7 and people will still be
using ASP
Personally, I will stick to using ASP for the forseeable future. I have a
decent grasp of ASP.NET but right now I can crank out the code with ASP
pretty fast and things run smoothly here as it is...
In fact, just now I am starting up on the newest version of my website...
pretty much starting from scratch and going to rebuild the entire site from
the ground up (currently its about 650,000 lines of code) so that I can
improve the ordering system and install about 200 new features into the
site... I could do it in ASP.NET but if I do it in ASP I can have it done in
3-5 weeks.
> Futhermore, here are some things lacking from my skillset:
>
<snip>
Ok, you basically mention: Photoshop, Javascript and Flash...
The thing here is it all depends on who you are working for:
If you work for a web design company then odds are they will hire you for
the skills you have. If you are the "ASP Guy" they aren't going to come to
you and say "slice up this PSD file so we can convert it into a website and
then animate the buttons with flash"... instead they will send that over to
their "graphics guy" and if he has flash skills he'll do the animation, if
not he'll pass it on to the "flash guy"
On the other hand, if you are working freelance for a client then you would
have to be pretty stupid to pitch them a site with loads of flash and
javascript if you don't know how to do it.
> Here's what the working list. Please add to it as you see fit. If
> there is a better name for the category please correct me. I won't
> mind.
>
> 1. Server-side dynamic content (such as ASP)
> 2. Client-side dynamic content (such as Javascript, VBScript, DOM,
> DHTML)
> 3. Markup (such as HTML/XHTML)
> 4. Data access (such as ADO, ADO.NET)
> 5. Presentation (such as CSS, XSL)
> 6. Database (such as MS Access, SQL Server, Oracle, MySQL)
> 7. Web standards (as taught by Zeldman -- www.zeldman.com)
> 8. Digital/Graphics design (such as Adobe Illustrator/Photoshop)
> 9. Digital Motion Media (such as Flash or Shockwave)
You pretty much covered the bases here...
Some other important ones to add would be:
Project Management
Structured Programming
Those two would be especially important if you were looking to hire on with
a web design company (you don't have to know how to be a project manager,
but you should know the terminology and how things operate in a properly
managed group)
You might also want to know proper business writing principals and writing
copy. Those skills will be handy if you have to write copy and content for
a website (can be an easy way to pad the bill with a few extra dollars or
move things along if you have a client that is dragging his ass in getting
the site content to you)
>
In any case,
> I'm looking more for a technological skills grab bag. What are the
> most useful tools in your grab bag and why? What technologies did you
> consider a godsend in that they made your life so much easier?
I'm not sure what you want here... you pretty much cover everything you
really need to make serious go at it.
People could sit here and list off the skills you don't have but what good
would that really do? I try to think about what purpose you have in your
post and come to 2 different conclusions:
1) You are looking to hire on with a web design company
2) You are looking to land a big contract with a big company
If its #1 then the company would be more interested in you if you excelled
at a couple of skills, rather than if you knew a little about everything.
If its #2 then you might be going about it the wrong way... usually all they
care about is the end result and if its compatible with their current
technology.
An Example: Earlier this year we did a big job for the US Dept of
Agriculture... we went in there with our presentation... a 35 page booklet
for everybody present and a powerpoint presentation.
The first 5 pages of the booklet covered who we are, what we are going
to do for them, how long it will take and how much it will cost... The next
10 pages were screenshots about what the site would look like... The rest of
the booklet was all project management stuff: procedures they have to
follow, procedures we have to follow, timelines, milestones, when we will be
having meetings, Gant charts, change request forms, etc. Then, on the final
page we listed the technologies the site would use and any custom software
we would need (either to develop or install upon completion)
Anyhow, thats my thoughts... hopefully there is some insight in there
somewhere
Clint