The 'Jam Echelon Day' word list is not realistic. The NSA could care less about the Davidians, or even the FBI for that matter. Permit me to suggest a better list:
Want to produce really bad software. It's easy if you follow just a few simple rules:
1) Produce no documents - avoid creating requirements documents, design specs, etc. Just jump right into coding.
2) If it's a large project, divide the work into several different development groups, and make sure they don't communicate. If they can be geographically separated, so much the better.
3) Don't hire any experienced programmers, or if you make the mistake of hiring them, don't listen to them.
4) Make sure that managers create impossible schedules. Nothing produces bugs like highly caffeinated over-worked sleep deprived programmers.
5) Change requirements (unwritten of course) frequently. Be sure and add plenty of new features at the last minute.
6) Be absolutely certain, that you don't learn any lessons from industry history. Don't read Brooks, Deming, Humphrey, or any other Software Engineering or Quality literature. And for God sake's, DON'T look at 'http://www.sei.cmu.edu/'!
7) Avoid any and all code inspections.
8) Avoid creating any sort of development processes, or if you do, make them so pointless and burdensome, that they are self defeating.
9) Do believe that you can test quality into a product. But be sure to compress the testing schedule just in case.
I think you'll find that 'windows' were invented and patented by Bell Labs (whether the patent now resides with AT&T or Lucent - I don't know). I recall using the 'Blit' windowing environment at Bell Labs in the early '80's. Certainly before the first Mac and well before MS Windows. It used a large (portrait) page size green screen and a large red mouse (a Xerox invention).
As for side by side text comparison's - the 'sdiff' command has been available in Unix for ages.
Slashdot Mirror
The 'Jam Echelon Day' word list is not
realistic. The NSA could care less about
the Davidians, or even the FBI for that
matter. Permit me to suggest a better
list:
Weapons: Nuclear, VX, Sarin, Stinger,
AK-47, Anthrax, Back-hoe
Bad Guys: Saddam Hussein, Slobodan Milosovic,
Mad-Dog [Qu|K|Kh][a|i][d|dd]a[f|ff|ph]i,
Kim Il Sung, Osama Bin Laden, Lucifer,
Bill Gates
Good Guys: Bill Clinton, POTUS, Slick, Burger boy,
Al Gore, Tony Blair, Linus Torvalds
Verbs: nuke, assasinate, attack, defenestrate,
hack, mung, frobnicate
Countries: Cuba, Libya, Syria, North Korea,
Afganistan, Redmond
Targets: White house, Congress, Cheyenne Mountain,
Pentagon, Washington, New York, L.A., that-big-
area-between-the-coasts, Fry's, Poke-Joe's
Organizations: NSA, NRO, MI5, Interpol, IRS, BBC,
B.B. King, Illuminati, FSF, Slashdot, We'd-tell-
you-but-then-we'd-have-to-kill-you
Want to produce really bad software.
It's easy if you follow just a few
simple rules:
1) Produce no documents - avoid creating
requirements documents, design specs,
etc. Just jump right into coding.
2) If it's a large project, divide the
work into several different development
groups, and make sure they don't
communicate. If they can be
geographically separated, so much the
better.
3) Don't hire any experienced
programmers, or if you make the mistake
of hiring them, don't listen to them.
4) Make sure that managers create
impossible schedules. Nothing produces
bugs like highly caffeinated over-worked
sleep deprived programmers.
5) Change requirements (unwritten of
course) frequently. Be sure and add
plenty of new features at the last
minute.
6) Be absolutely certain, that you don't
learn any lessons from industry history.
Don't read Brooks, Deming, Humphrey, or
any other Software Engineering or
Quality literature. And for God sake's,
DON'T look at 'http://www.sei.cmu.edu/'!
7) Avoid any and all code inspections.
8) Avoid creating any sort of
development processes, or if you do,
make them so pointless and burdensome,
that they are self defeating.
9) Do believe that you can test quality
into a product. But be sure to compress
the testing schedule just in case.
10) Three words - "Ship it anyway".
I guess this is what Gates meant when he said :-)
"Microsoft must be free to innovate".
I think you'll find that 'windows' were invented
and patented by Bell Labs (whether the patent
now resides with AT&T or Lucent - I don't know).
I recall using the 'Blit' windowing environment
at Bell Labs in the early '80's. Certainly
before the first Mac and well before MS Windows.
It used a large (portrait) page size green screen
and a large red mouse (a Xerox invention).
As for side by side text comparison's - the 'sdiff' command has been available in Unix for
ages.