Slashdot Mirror
Future Skills for a Budding Web Designer?
ericdfields asks: "One of my lifetime career goals is to establish myself on some decent level or another as a well-rounded, (mostly) standards-based web designer with some backroom web development knowhow. The problem is I have no clue where to begin. HTML, CSS, JavaScript are an obvious start, but what about other web-driven languages? PHP, XML, SQL, Perl... the list goes on. Should I be looking to grab hold of some Flash and Director skills? What abilities will be needed on the horizon that I can get an early start on learning today?"
Make sure that you have a good grasp of graphic design and layout/text editing. The best web-designers know more than just the techincal skills, they also know what a good looking page is supposed to look like. Most people are surprised that there are real and time-tested design standards. Violate them and no amount of techincal knowledge will make a webpage look good.
or master of none?
your choice.
However, praises are sung of masters.
would you want that as a career? The only career I can see shrinking as rapidly is the support centre phone operative.
Daniel
Carpe Diem
I'm going to assume by "designer" you really mean a graphic designer, and not a web developer. That is, you'll be greating the UI and maybe putting together the pages, but not doing heavy development.
If that's true, I'd say the most important thing you can learn is what a dynamic site does. Understand that content will grow/shrink depending on the database at that moment and make sure your design can accomodate that.
I've been developing web sites for close to 10 years now and the ones that are the hardest are those where the designer thinks of a web page like a magazine page and doesn't understand that things stretch/shrink/flow.
That said, I'd also learn as much as you can about *how* the backend languages work (PHP, XML, etc.) but you don't need to know the specifics. But if you understand the relationships and their capabilities you'll be your developers best friend.
There are too many facets to learn it all. Pick the arena you are interested in, and work with others to develop the entire package. A "Jack of all trades" will usually create software that is mediocre in all areas.
10b||~10b -- aah, what a question!
JavaScript, used correctly, is good. Look at all the compliments Google gets on GMail and Google Suggest or what people are doing with unobtrusive DHTML.
If anything you should be encouragine this guy to write good JavaScript so you don't have to put up with the bad stuff.
Why can't I moderate something "Wrong" or at least "Grossly Misinformed"?
HTML is a must. Learn it from the w3schools website - their tutorial rocks. Also check out XHTML, and see if you can conform to the standard in everything you write, whether it is required by your job or not. Standard conformity is a good way to save yourself when all the browsers in the world render differently.
CSS is good to know, BUT: most of the time, a company will have a CSS template that they use over all their web pages. Sometimes you'll just have to include this template in your HTML (a one tag thing), and sometimes you'll have to edit it a bit. If you ever have to make your own, a quick look at the above website will help you do it immediately (if you can already do HTML, CSS makes a lot of sense), although I wouldn't focus on it initially.
ASP (& VB), JSP (& Java), PHP (& Perl). Most companies are going to be tied to one of these three. The best thing to do is be a beginner at all of them - take a look at sample code from all six - and then become an expert on the job. My current employers (a university) are tied into Microsoft products, and politics (and other interesting financial things) keep them from changing. However much I would like them to move over to LAMP, I'm not going to sit and mope and lose my job. THUS, I code in ASP with Microsoft SQL-Server, and write VB programs for another section of my department. Be flexible. Don't assume you'll get to use your language of choice, wherever you work. Sometimes conditions prohibit it.
Learn SQL. Forget all this "learn MySQL" stuff. The connection to the database is generally something you'll write in 30 secs - with some template somewhere - and the SQL code to actually query and update that database is going to be the important, life-changing stuff. Learn SQL. On that note, if you're planning on being more of a back-end web developer (like me), learn database management. Learn how relational databases work. Learn how JOINs are your friend, and multiple relations (or tables) are a good thing. Ugly database code kills me.
And, to take a note from Joel yesterday, know how to communicate. Most web designers - the people who will be giving you changes that you absolutely must make or they'll die of horror at that color scheme - are art or design majors who have the elite thing going just like most of us programmers. Learn how to talk, how to listen, how to accept someone else's decisions when you don't have the power to make them - yet.
If you're planning on being back-end, there's a lot of other stuff you might need to know: how virtual directories work, how IIS sets up ASP applications, how Apache's configuration file works, how home directories are transferred over, how server scripting actually works, how to lock down a web server, etc. But if you have a good grasp on the above, and you stay flexible, you should be ok in the job market.
(That, and having all those acronyms on your resume will get people hooked if you can actually confirm your knowledge!)
I [may] disapprove of what you say, but I will defend to the death your right to say it.
One of my lifetime career goals is to establish myself on some decent level or another as a well-rounded, (mostly) standards-based web designer with some backroom web development knowhow.
4-5 yrs down the line you will probably want to be doing something else less web related - most people want basically the same thing from their websites. And once you have built umteen sites for umpteen different client - you will find your self wondering what other interesting development jobs there are about. I'd advise getting some other more generic skills - C/C++ maybe something else but that can easily be leveraged when you decide websites are'nt challenging any more...
Electronic Music Made Using Linux http://soundcloud.com/polyp
One of my lifetime career goals is to establish myself on some decent level or another as a well-rounded, (mostly) standards-based web designer with some backroom web development knowhow.
Lifetime goal? Either you're twelve years old, or you're setting your sights really, really, really low. Or both.
Web design used to be tough a long, long time ago. These days, saying that you're going to be a well-rounded web designer is like saying you're going to be a well-rounded word processor user or desktop publisher. Off-the-shelf tools like Dreamweaver can produce web code more than good enough to get by. The challenge is no longer the tool, but the content: businesses have a greater need to put together sensible content that users want to consume, rather than just putting together a well-formatted web site.
If you want to build a set of lifetime career goals, get a role model and ask them what skills they use in their daily job. Don't make the mistake of asking them how they got their start, because lots of us got started in web design because it was tough ten years ago. It's not tough anymore, and it's not a great place to start now.
If you want to make money on the web, don't get started with design - get started with content. Find a subject that you're an expert on, and build out your content using any run-of-the-mill web site management system like Plone or Xoops. Forget getting good at HTML - any monkey can do that. Get good at providing content that users want to return to, and then you have a shot at making money.
What's your damage, Heather?
Primarily for enforcement of how a form should be filled out. ...and that's basically it. JavaScript is pretty much 1% form validation and shopping cart updates and 99% usability impairment. CSS is the way to go.
-- Microsoft is the most expensive commodity operating system and office suite vendor in the marketplace.
Becoming a good flash developer is significantly more difficult than learning HDML/CSS tags. If it is used in the proper context Flash is a great tool. Unfortunately it is rarely used in a productive manner.
I would agree that you *shouldn't* need Flash to build a web site (at all). I hate flash. It doesn't do anything functional that can't be done without it, and it requires a proprietary plug-in, and I hate needing to download plug-ins.
So much for my personal rant, because if you're looking for web-development jobs, a lot of people hiring are going to be looking for flash. Often people who don't know better, but sometimes people who just want something.... ehrm.... "flashy".
It's a sought-after skill, and if you're looking for a career in web-development (though I must echo the people who've been asking "why?") it's a good skill to have. However, I would agree that one ought to learn the practical stuff first, namely XHTML, CSS, PHP, SQL, learn that stuff first. Flash is fluff (regardless of what Macromedia says).
"except that i would suggest he learn XHTML 1.1 rather than HTML"
:/
Aside from pointless spec (or IE) breaking, what does this achieve over XHTML 1.0 or HTML 4.01? Markup wise, HTML 4.01 Strict is pretty much identical to XHTML 1.0 Strict and XHTML 1.1, but there are a whole load of other issues with using XHTML (1.1 especially) you need to be aware of that suggesting everyone use it is just.. well, silly. This is not a place you want to version-chase unless you like unnecessary hacks and more points of failure.
"a compliant, doctype'd page renders faster than HTML 4.0 in Mozilla and IE"
Wrong. IE supports XHTML the same way it supports tag-soup HTML, and so does Mozilla unless you serve it with a Content-Type IE doesn't support. Unless you have a real reason to use XHTML, it's generally better to use HTML 4.01, especially if you're playing with JS and DOM. Seriously, you're recommending to a newbie to use a doctype who's entire DOM model changes depending on how correctly you serve it?
..why?
:)
It's an underlining point of CSS - separation of data flow and styling. Lynx is used to force this into the developer's mind by doing exactly that -- only showing the flow of content.
If you content doesn't flow properly, regardless of what you do to it, it's not going to "work"; thus, get a working flow first and it will "look good" under anything.
That's my experience, at least. For whatever the heck it's worth these days.
"An infinite number of monkeys typing into GNU emacs would never make a good program."
In my capacity as a web developer, here are the software packages that I feel you should have a firm understanding of:
And now for some soft skills. First, you'll need to learn to give effective presentations. You could use Powerpoint for this, or Keynote or Impress or just print them on transparencies and put them on an overhead projector. How you do it is up to you. Will you ever need to give presentations? Not really, but effective presentations require a lot of soft skills - eye contact, graphic design, pacing, speech tones, body language - that to be skilled in presentations in general means to be skilled in a lot of other areas.
You should also familiarize yourself with colour. Learn about Pantone, just so that you know about it. Learn how colours play off each other, which colors look good on which backgrounds. Learn about bordering, whitespace, balance, and form. Consider the Pantone Guide to Communicating with Color - out of 61 reader reviews, it got 4.5/5 stars, and is a good place to start.
Learn about logos. How companies make logos, and why. What goes into making a logo, subconscious suggestions from logos (there's a reason Playboy picked a bunny for their logo, and it's not obvious). This will help in your graphic design and page layout.
Learn about accessibility and colour-blindness.
I'm probably missing a ton of important stuff, but if you do it right and are willing to learn (and posting on slashdot seems to imply that), you'll probably learn what you need to know as you go. If not, just come back and post another Ask Slashdot.
java script and active x websites force people to surf randomly with that stuff turned on. Why do you want to do that? There's more than enough evidence to show that basically it's a bad idea. Your particular site might be totally innocent, but you have no guarantees about other sites, so you force users to set preferences back and forth constantly. This is the 21st century, people use tabs and multiple pages open, not just one...page....at .....a ...time, and jump back and forth. JS and Active X is a *threat* in general if you do that.
I avoid sites that use javascript now, especially because rarely do they provide an alternative way to navigate inside the site, and they usually don't use alt tags on image links either. JS *works* and does all kinds of nifty cool keen stuff, but it's bad for security, you can't make it work to be good for security,so, why do it? Convenience? For whom? The visitors? No it's not it's a threat and useability flaw. And as such my personal opinion is it shouldn't be used for web pages. On your closed intranet, sure, go for it, no probs. I am just not going to keep jumping back and forth in preferences to turn it on and off. To me, telling your webpage visitor that they have to use JS just to see and use your site is absolutely no different from coding it to only "work" under one web browser. It's just too easily abused and it's insulting actually. I haven't kept track but I can asure you there's more than a few web merchants who haven't gotten my cash business because they insist on JS, and I am able to find an alternative that doesn't, so they get my money instead. Just how it goes. And Flash without an option, just click on a link then it's a 50/50 crapshoot if it will lock up your browser or not. Well, to be fair that is only one guys experience, mine.. Again, no thanks. Give me an option to click on the flash, just don't spring it on me on the homepage of some site.
First, you've set your lifetime goals way too low. If you are any good at all, you will have achieved this in less than a decade (probably half that) and then it's crisis time. Set your lifetime goals higher, the higher the better.
Second, while you do need to know this technical stuff, that's not all there is to it. On top of HTML, XML, CSS, JavaScript, Java, PHP/ASP and SQL, you will need to understand (and be good at) graphic design, and have some other domain knowledge that gives you insight into the business reasons for the web design work you do. You can't get most of this knowledge quickly or easily, some of it you simply must be born with and some of it will only come after decades of experience.
Your best bet is to go straight to your local community college and enroll in the Web Design or Web Programming certificate course. While you're at it, think about enrolling in some other, largely unrelated major (business management, visual arts, chemistry, psychology, english literature, whatever) which will give you some outside perspective to ground your technical skills. You can finish up both the certificate and the AA in two or three years as a full-time student, or four years of part-time school/part-time work. While you're there, take advantage of an internship or cooperative education program.
If you're feeling really energetic, replace community college and AA in the above paragraph with university and BA or BSc. Lather, rinse, repeat.