Our tools/toys/poisons:

• Perl
  Truly the "swiss army chainsaw" of any programmer's toolkit. Perl can make managing servers easier, create lightning fast and lockbox-secure web applications and do everything in between. Pretty much anything that has to do with shuffling packets around the 'net perl is up to. Perl also has an impressive code repository, free for the using (CPAN) that is really its killer app in disguise.
  My favorite thing about perl is mod_perl, which embeds perl into the incredible Apache web server, giving you enormous speed and control.
• XML/XSLT
  XML (eXtensible Markup Language) is a way of marking up information to make it more flexible, compatible, and adaptable. XSLT (eXtensible Stylesheet Language Transformations) is a "language" for turning XML documents of one type into another.
  XML, XSLT and the other TLAs (Three Letter Acronyms) in the XML universe allow you to have information that you can repurpose and is separate from how you present it to the world at large. Theoretically you'll have obsolescence-proof data that is infinitely flexible.
• PHP
  PHP (PHP - Hypertext Preprocessor) is a great choice for creating web applications. Because it's fast right out of the box on most third-party web-hosts, it's an economical way to have a very fast web app. It's also designed specifically to make a web programmer's job easy and speed development, with many web specific functions built in.
• MySQL:
  Think of MySQL as Oracle's immature little brother. While MySQL lacks some features the big RDBMS's have,  it's improving rapidly.
  If you need a fast data store that mostly issues read queries (which most dynamic web sites fit into), MySQL is a great choice. Where I've used it, I've got nothing but good things to say.
• PostgreSQL:
  PostgreSQL is the "most advanced open-source database" according to the project homepage. I have to agree. Pretty much everything MySQL doesn't support, PostgreSQL does, and does beautifully. Why isn't PostgreSQL as ubiquitous as MySQL? I don't know. Marketing? Supposedly MySQL is faster, but I've heard benchmarks that put them neck-and-neck, and PostgreSQL ahead in some cases. I'd recommend either wholeheartedly depending on the project.
• HTML:
  Most folks that design HTML have a love-hate relationship with it. I mostly hand code mine, because it gives me finer control and allows me to create more browser/platform agnostic pages than most WYSIWY(-sometimes-)G editors.
• JavaScript:
  I don't think anything has ever frustrated me more than debugging javascript, considering that there are like a zillion different browsers you need to take into account. I use javascript simply as icing, and never rely on it for anything I really care about or that is central to the function of a page. That said, it does have its uses.