Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed).

It is critical for interoperability that architects interact often
with TAG and be exposed to a variety of use cases and, of course, the Web, itself.

(I tried to submit this drivel before, but the amazingly flexible
PHP/Ruby/Ajax “submit comment” button architecture laughed at
my kung fu….)

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed).

It is critical for interoperability that architects interact often
with TAG and be exposed to a variety of use cases and, of course, the Web, itself.

(I tried to submit this drivel before, but the amazingly flexible
PHP/Ruby/Ajax “submit comment” button architecture laughed at
my kung fu….)

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed).

It is critical for interoperability that architects interact often
with TAG and be exposed to a variety of use cases and, of course, the Web, itself.

(I tried to submit this drivel before, but the amazingly flexible
PHP/Ruby/Ajax “submit comment” button architecture laughed at
my kung fu….)

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed).

It is critical for interoperability that architects interact often
with TAG and be exposed to a variety of use cases and, of course, the Web, itself.

(I tried to submit this drivel before, but the amazingly flexible
PHP/Ruby/Ajax “submit comment” button architecture laughed at
my kung fu….)

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed). It is critical for interoperability that architects interact often with TAG and be exposed to a variety of use cases
and, of course, the Web itself.

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed). It is critical for interoperability that architects interact often with TAG and be exposed to a variety of use cases
and, of course, the Web itself.

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed). It is critical for interoperability that architects interact often with TAG and be exposed to a variety of use cases
and, of course, the Web itself.

Training architects is not always easy: it requires a lot of work,
as they do not know right from wrong and must rely on the TAG for
guidance. Since architects are so impressionable, it is important
to begin explaining the rules right away. Often, aggressive or
skittish architecture (e.g. slow response times and “404 problems”)
can be blamed on lack of discipline and training by the TAG (in bed). It is critical for interoperability that architects interact often with TAG and be exposed to a variety of use cases
and, of course, the Web itself.