Re: [MACCAWS] been thinkin' ...
"Jon Dillon" <[email protected]> Thu, 1 Aug 2002 18:02:08 -0700
| Newsgroups | gmane.comp.web.vkit |
|---|---|
| Message-ID | <[email protected]> |
> > I was thinking along the lines of treating building a site the same > > as building, > > for instance, a shop. You have to pay attention to building > > regulations, in some > > countries you aren't allowed to make it inaccessible by law, etc. > > So, can we impose fines for using FrontPage? ;) > Hell yea. ;-) At least, one should anyways. I like the anology, but it's more of an anology for builders than for managers. If you're trying to make a business case, I don't think the building inspection process is really a good anology. Most building inspection is done to mantain public safetly standards, to keep people from dying if there is an earthquake, fire, etc. I don't know if we need an anology. I mean, it's a good mechanism, but IMHO, I think we'd be well off with a business case. I'm a business manager, and I've got to put web standards into my organization. I know it's a good idea, but I'm in an MS shop, and everybody thinks Microsoft's "standards" are web standards. What do I need? If I raise the issue, I put my own ass on the line, and I am accountable now for how this new "standards thread" turns out in the organization. I need heavy weaponry to protect my ass. Seriously, isn't this why we need this "guide" for business folks. This is just one use case, but isn't corporate politics and lack of educational awareness the reason for it? 1) I need a very good business case. I'm not talking about "because it saves time and money," that's bullshit coming from one of the engineers from a manager's perspective. How much money and time is another matter. You see, most folks who are fighting for web standards are the UI guys, and they don't often hold as much clout as the backend engineers. 2) We need a VERY compelling arguments for why web standards make sense in a development project. How does "using standards" change the development cycle. Certainly, if you do, you can no longer have your engineering staff building your html. You must follow a prototype model or you'll end up with total shit at the end right? Just some thoughts. Too much coffee today folks. ;-) Jonathan To unsubscribe from this group, send an email to: [email protected] Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/