|
|
Posted by dorayme on 02/19/07 22:01
In article
<1171919794.587799.258690@m58g2000cwm.googlegroups.com>,
"windandwaves" <nfrancken@gmail.com> wrote:
> On Feb 20, 1:27 am, "Andy Dingley" <ding...@codesmiths.com> wrote:
> > On 17 Feb, 00:47, dorayme <doraymeRidT...@optusnet.com.au> wrote:
> >
> > > The special case of a need to check
> > > every id and class is far fetched but interesting.
> >
> > I work on large projects with large teams. We use Agile techniques and
> > also practice "shared code ownership". This means that one is usually
> > working on other peoples' code (actually it means that there isn't any
> > "other people's code"!). Additionally there's a competency-specific
> > split between the work people do (Java people do Java, JSP people do
> > JSP etc.). As my own job is rather centralised and de-specialised, I'm
> > often trying to integrate these separate efforts.
> >
> > Part of this work involves a lot of code analysis. I want to see just
> > what has been going on: if particular sections are using inlined
> > styles rather than stylesheets, how deep the <table> nesting gets and
> > if anyone's still using their remaining hand to type <font> tags.
> > Reporting on use of class or id values, and whether these appear to
> > correlate between HTML and CSS, is just another part.
>
> so how do you do this?
I have spies and they report back to me that, once the poor
customer has walked out of his office, relieved that the job of
code analysis is being done by others, he takes a quick decko,
sees font tags and stuff and tells his underlings - from the
corner of his mouth - to guess a template for the html from
existing, grab the contents and navigation and rewrite the lot
from scratch with a clean set of css sheets. The customer is
delighted with the result. He is paying less than he thought he
would but has a satisfyingly fuzzy idea of the great complexity
that has been taken care of for him.
--
dorayme
Navigation:
[Reply to this message]
|