Patrick Shannon
04-24-2007, 09:57 PM
You know, back in the good old days, HTML...well, just kind of worked. And if it didn't, it didn't at least display cryptic error messages or anything. PHP and ASP were nice enough to tell you what line there was a flaw on. But now in my brand new career as a bugfixer (loooong story), this is what I have to tolerate about ten times a day when I go to try to fix some CSS styling error some other f**Ktard pulled....
http://www.cultureinnovation.com/error.gif
WHAT in the hell does that mean to me? Why should I care? Does it even mean anything? Why can't it just pull up the HTML nicely anyway? Why is it that I can run complete circles around this .NET platform with more traditional XHTML and PHP design? (When I go home and open my own client's websites, they just work.)
NOTE TO EMPLOYERS: DESIGNER. NOT DEVELOPER. MAKE YOUR **** WORK BEFORE I GET A HOLD OF IT.
Phht...that felt good. And remember kids, this is what Microsoft technologies does to your workflow.
http://www.cultureinnovation.com/error.gif
WHAT in the hell does that mean to me? Why should I care? Does it even mean anything? Why can't it just pull up the HTML nicely anyway? Why is it that I can run complete circles around this .NET platform with more traditional XHTML and PHP design? (When I go home and open my own client's websites, they just work.)
NOTE TO EMPLOYERS: DESIGNER. NOT DEVELOPER. MAKE YOUR **** WORK BEFORE I GET A HOLD OF IT.
Phht...that felt good. And remember kids, this is what Microsoft technologies does to your workflow.