It is the equivalent of building a house without blueprints. You can do it, but if you take the time to plan things out before you break ground you will end up with a stronger product.
Now, if you already have a design style locked down and code you can just puzzle together then sure, go ahead and skip Photoshop. I do that as well. But, as soon as I need to design a new UI element I am back in Photoshop making dozens of variations.
Sketching doesn't give you a realistic sense of space and feel for web design. Very often you can sketch something that looks good on paper, but once you put it on the screen it just doesn't translate well to a pixel medium.
Sketching is great if you are working with a physical medium like brochures or posters though. Then it doesn't suffer from the same translation cost.
For all 37s likes to talk about not using Photoshop they don't have pixel-perfect design at all and yet still had somebody slaving over Adobe products while putting those logos together.
Mocking things up in Photoshop can be really productive because everything you sketch (all of your background images, buttons, and art) can be used as an asset on your site with minimal effort.
As to the general feasibility of jumping straight to code, you might find this post by Andy Clarke interesting: http://forabeautifulweb.com/blog/about/designing_the_cannybi...
The design was all done in HTML & CSS. And I, at least, find it more compelling than most Photoshopped web designs.
I do agree that you need SOME sort of mockup, but I actually think low res mockups are more effective because people aren't distracted by the fact that an underlined link in PS doesn't quite look right.
web designers absolutely should use photoshop, because they are essentially providing the "theme" around the wireframe, that may be designed by the UI designer.
On the other hand, if it's more graphical (eg: http://www.ubuntu.com/desktop) then I'd agree that Photoshop is absolutely necessary.
And no, I still disagree slightly. It's not about the kind of design the final product is, it's about what function your role is fulfilling. Are you designing the way the people interact with the application, the way the application looks and feels, or both?
Depending on your skill levels in various tools, it might be way better to simply start into html + css. I know a couple designer/developers who can go from an idea to visuals dramatically faster in code than they could using photoshop (myself included). Additionally, you get the advantage of being able to style simply effects in right away (ie, hover states, focus states, etc) instead of having to create extra layers or version of a PS file.