From: Rod Pemberton on
"Alexei A. Frounze" <alexfrunews(a)gmail.com> wrote in message
news:9a9478c2-66cf-4f3c-8a4b-0f6c6da34643(a)s20g2000prd.googlegroups.com...
> On Sep 13, 1:16 pm, "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote:
> > I posted this link a while back. Have you seen it?
> > http://www.strauss.za.com/sla/code_std.html
>
> Sweet. What a collection of all the worst practices and some
> perversions. I've seen code with a few items from this doc. And I
> doubt that was intentional. Simply incompetent.

I love this line:
"marypoppins = (superman + starship) / god;"

I was LMAO with first third. I'm curious as to where #28 came from. The
"On the Proper Use of Design Documents" is an absolute gem...

The "...document hidden on some dusty shelving in the back room near the
dead [...] computers" quip reminded me of a few similar situations at a
company I worked for. :-)


Rod Pemberton

From: Rod Pemberton on

"Rod Pemberton" <do_not_have(a)nohavenot.cmm> wrote in message
news:gahqfi$dgr$1(a)aioe.org...
> "Alexei A. Frounze" <alexfrunews(a)gmail.com> wrote in message
> news:9a9478c2-66cf-4f3c-8a4b-0f6c6da34643(a)s20g2000prd.googlegroups.com...
> > On Sep 13, 1:16 pm, "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote:
> > > I posted this link a while back. Have you seen it?
> > > http://www.strauss.za.com/sla/code_std.html
> >
> > Sweet. What a collection of all the worst practices and some
> > perversions. I've seen code with a few items from this doc. And I
> > doubt that was intentional. Simply incompetent.
>
> I love this line:
> "marypoppins = (superman + starship) / god;"
>

"Cd wrttn wtht vwls s mch trsr"

[Code written without vowels is much terser.]


Very true... :-)

ROFL,


Rod Pemberton

From: Alexei A. Frounze on
On Sep 13, 6:55 pm, "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote:
> "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote in message
>
> news:gahqfi$dgr$1(a)aioe.org...
>
> > "Alexei A. Frounze" <alexfrun...(a)gmail.com> wrote in message
> >news:9a9478c2-66cf-4f3c-8a4b-0f6c6da34643(a)s20g2000prd.googlegroups.com....
> > > On Sep 13, 1:16 pm, "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote:
> > > > I posted this link a while back. Have you seen it?
> > > >http://www.strauss.za.com/sla/code_std.html
>
> > > Sweet. What a collection of all the worst practices and some
> > > perversions. I've seen code with a few items from this doc. And I
> > > doubt that was intentional. Simply incompetent.
>
> > I love this line:
> >   "marypoppins = (superman + starship) / god;"
>
> "Cd wrttn wtht vwls s mch trsr"
>
> [Code written without vowels is much terser.]
>
> Very true...  :-)

How about this one?:
o y o uea a I oe ee <-> Now try to understand what I wrote here.

Alex
From: Alexei A. Frounze on
On Sep 13, 6:46 pm, "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote:
> "Alexei A. Frounze" <alexfrun...(a)gmail.com> wrote in messagenews:9a9478c2-66cf-4f3c-8a4b-0f6c6da34643(a)s20g2000prd.googlegroups.com...
>
> > On Sep 13, 1:16 pm, "Rod Pemberton" <do_not_h...(a)nohavenot.cmm> wrote:
> > > I posted this link a while back. Have you seen it?
> > >http://www.strauss.za.com/sla/code_std.html
>
> > Sweet. What a collection of all the worst practices and some
> > perversions. I've seen code with a few items from this doc. And I
> > doubt that was intentional. Simply incompetent.
>
> I love this line:
>   "marypoppins = (superman + starship) / god;"
>
> I was LMAO with first third.  I'm curious as to where #28 came from.  The
> "On the Proper Use of Design Documents" is an absolute gem...

Happens all the time. Even despite the fact that there exist a tool to
check that the file/function header comments are in place and
minimally correspond to the file/function.

> The "...document hidden on some dusty shelving in the back room near the
> dead [...] computers" quip reminded me of a few similar situations at a
> company I worked for.   :-)

How about complete absence of design/functional specs? "The code is
your doc, stupid!" being the policy :) Or design specs that are merely
self-contradicting ramblings and suggestions/vision for the actual
design?

Alex
From: Wolfgang Kern on

Alexei A. Frounze mentioned:
....
> How about complete absence of design/functional specs?
> "The code is your doc, stupid!" being the policy :)

Please don't laugh too loud about the latter line above, it's
in fact the way I have to use since my very first attempts
in modifying already existing code.
This made me an expert on 1802/HC11/etc. ROM-analysis and I could
make good money out of it for many years.

But windoze and L'unix analysis would be a horroid time waste if
I'd try to do it manually. So I started to write an automated tool.
At the moment I lack on the several Tbytes required for a static
code analysis including a whole OS behind it.

> Or design specs that are merely self-contradicting ramblings
> and suggestions/vision for the actual design?

When I look at my own notes yet, it's about time to clean up the
mess with all the changes and added things in my latest version. ;)

__
wolfgang