Word! "I feel ya" and I agree with you. :-)
But unobstructive javascript? Why would anyone assume that software
designs are naturally obstructive in the first place? I'm not
debating the term, I am debating the idea that writing clean
modulize, consolidated code is a "new idea" a new awakening that it
requires a new term. In other words, the lack of discipline in the
past 12 years, got people to the point to eventually discover their
great looking software was not too flexible after all. Their focus was
limited. It was obstrusive, as an adjective, not as a design concept
in the ergonomics of the system. So I rhetorically ask, it is because
of ignorance that terms like "obstrusive programming" are invented?
Or that we really needed a new dress to express the behavior as we
know it today?
It has never failed that its a cycle. I've cover the industry for
aleast 3.5 decades now. I'm a programmer at heart. Inevitably, at
some point, we all fall into the same contraints. Your creativity and
flexibility to invent is not like it use to be. At some point, you
are no longer the champion. The product stays however, consistency
and stabliity is required for growth. Otherwise, the next guy with
the better mouse traps comes along.
My point is one of marketing. To maximize its adoption, you have to
craft it in ways that is broadly understood. Sigmour Cray, the father
of the Cray Super Computer, when asked by his engineers, "What
language should we used for our new machine?" He infamously replied:
"I don't care, just make sure you call it FORTRAN."
Even in todays world of new tools, you can also do better, sell and
market it better by labelling the way the entire computer industry
understands. Inventing what I call "Ghetto" terms and worst, every
blogger coming up with dozen of the terms reflecting the same with no
consistently, doesn't help.
Just call it what it is. Good Programming Style! Is that too old?
<g>
Anyway, hopefully I can provide some insight to some who are deeply
involved with this stuff today to add alittle professionalism and
standard terminology. It will help people better understand what you
are doing or saying. They might be surprise by the added success it
might bring.
Just my 1.5 pennies.
--
HLS
On Aug 16, 12:21 pm, "Mike Alsup" <[EMAIL PROTECTED]> wrote:
> Another thought would be to embrace and use the terms that are popular
> today. Names change, even when the ideas remain the same. You can't
> fight that. This is nothing unique to software engineering, it's just
> human nature. I can't tell you how many times my parents have said to
> me, "In my day, we used to call that...."
>
> Mike
>
> > What are you guys? Nuts! :-)
>
> > Use words like Modular or functional programming, "Consolidation" or
> > just
>
> > "Applying Software Engineering Principles to Web 2.0
> > Development"
>
> > and you will begin got turn some heads and get the "Ah ha", the "I
> > feel ya" from managers, and project engineering folks and CTO like
> > myself who are trying to make sense of whats going on here!!
