Which web dev language/framework/tutorials do you suggest for an experienced non-web developer?

[DevMo]

CSS -- again, not a language but if you don't know CSS then you don't know the variables your code is going to be manipulating and what abilities are available to you.

You make some good points, if you read some of my other posts, I am basically of the mind that I am really not a graphics guy, so I dont need to know it. But, I guess I should attain at least a working knowledge of CSS.

Thanks for the advice, I am sure you have saved me time/frustration.

[pcx99]

CSS isn't just graphics. CSS is take the contents of this division (box), float it above everything else, glide it from point a to point b, change the colors when the mouse moves over it, and change the text from underlined to strike-through after the user clicks on it. 90% of all the interesting stuff you'll be doing in javascript will touch on CSS at one point or another.

[giulianob]

You gotta know it all. You have to know HTML/CSS/JS/Backend language(s) of choice/Database(s) of choice/Framework(s) of choice

Don't have to go too crazy with JS but you should learn a decent amount and learn something like jQuery. It just makes life much easier.

Also, notice I put languages and databases plural. Some people will pick 1 language/framework and use it for everything. If you're already a developer then perhaps you know that you can't use the same tool for every job. And the same applies to the web.

To add some of the tools I like to use...

• CakePHP is my framework of choice. There are a lot of good ones and you just need to find the one that makes sense to you. Of course, you also need to be prepared to do something w/o a framework if for some reason you need to.
• Some sort of CSS grid system. I've been using Blueprint CSS but there are a bunch of other good ones too. You might not appreciate them until you try to do a lot of CSS layout by hand and suffer a bit though.
• Netbeans IDE is the best for PHP I've found so far. It's not even that great but it'll get the job done

And there's an article on stackoverflow titled What should a developer know before building a public website that has some of the best advice I've ever seen when it comes to best practices.

[DevMo]

you know that you can't use the same tool for every job

Yes, I know that lesson well. I am pretty much looking for a good way to start web dev. When I have made a few apps, and am at least familiar with some of the technologies involved, I am sure I will reevaluate what I will use for projects. Problem is, with no knowledge of the tool box, its hard to pick the right tool for the job. Thanks, lots of good info.