Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through)

On 5 Aug, 01:56, docdw...@xxxxxxxxx () wrote:
In article <1186273171.573267.132...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,

It might be reasonable to conclude, however, that such
managers are attempting to reflect accurately the goals and attitudes of
the organisation in which they function.

It seems to be about losing face by failing to achieve the agreed
implementation date. Or losing one's job.

Then the goals and attitudes of the organisation would seem to include
'greater face is garnered by generating short-term advantage over
long-term savings' and 'we would rather fire people who insist on taking
more time to remove bugs up front'.


Rather more about losing business through not meeting the agreed
schedule. I only know of one person who got sacked and that was for
not doing work at home when he was supposed to be at home working.

There is something poetic about that statement.

If you really want to debate the
difference in style - and I believe mine is superior, of course, as any
decent, sane, well-educated, clean-fingernailed programmer can see - then
that might be subject for another thread.

No we shall let it pass.

I *told* you not to feed green peppers!


I can eat Jalapenos (mild), scotch bonnets/habaneros/nagas with no
problem. A word to the wise: if you wish to impress on the chilli
front, and still be able to walk, eat naga chillies coz they don't
burn on the way out.

[snip]

Definitely not me. The spec probably said that all dates should be
validated and left the detail to the snoozy programmer (who is not my
boozy chum).

Let it be assumed, then, that the spec contained an ambiguity... nothing
new or unusual there.

Not an ambiguity, just an omission.

The spec is not available to me to determine this, Mr Maclean, and I erred
on the side of generosity. Consider:

'An input record will be read and the following verifications will be
performed:

Customer number
Date
Product number.'

Now... does this indicate sequentiality of action? It can be read as
such, certainly - 'I got to the store and bought a loaf of bread' - but
not necessarily, as the sentence 'The hotel provides customers with
wonderful rooms and tasty meals' indicates.

'Yes, I'm going to the hotel... but I'll makes sure that I don't arrive
before my room is ready, if I go to the restaurant before I am provided a
room I will not get a tasty meal.'


I would expect that, in visiting umpteen hotels in one day, that the
programmer would eat no more than three meals in total. I expect that
programmers will think about efficiencies; after all, that is part of
their job. But now we are back to criticising the younger generation
for not being aware of the things to which we had to pay attention.



Who sat in on the code reviews and neglected to point out the waste of
machine time?

Code reviews? If it worked on one record in test then it was probably
passed as is.

So the programmer's work was not reviewed or inspected by a suitably
trained/skilled/experienced individual... I'm certain there was a Very
Good Reason for that.

Saves money. One less body to employ.

Costs money... even if coders being woken up at night are for free jobs
have to be re-run and one can lose customers because of dissatisfaction
with shoddy results.

Short- versus long-term.


Agreed.

What kind of volume-testing was done to show the amount of machine-time
used by the method was unacceptable?

None.

So unreviewed code was implemented into Prod without volume-testing... I'm
certain there was a Very Good Reason for that.

Saves money. One less body to employ.

Costs money... even if coders being woken up at night are for free jobs
have to be re-run and one can lose customers because of dissatisfaction
with shoddy results.

Short- versus long-term.


Did you cut-and-paste that coz I didn't on my bit!?


I think that the abilities of programmers declined with the generation
following on from me (apologies to Kellie et al but please indulge an
old fogey) whilst the management expectations rose (we all have seen
job ads for senior analyst/programmers with 18 months experience, and
ads for managers with 6 months experience).

I think I smell an 'Ahhhhhh, for the Oldene Dayse' there, Mr Maclean.

Yes indeed. Standards are in decline.

Not to worry, Mr Maclean... I won't get you started on the bunch o' durned
noise them kids nowadays're callin' 'music', neither.

I like some of that noise.

Don't make it any less noise... an' th' clothes they wear, ain't they got
no mothers ta shame 'em?

You should see what the mothers wear!


.

Relevant Pages

  • Re: ALTER design (Was: Code problems with Perform Thru Exit causes fall through)
    ... Or losing one's job. ... long-term savings' and 'we would rather fire people who insist on taking ... have to be re-run and one can lose customers because of dissatisfaction ... certain there was a Very Good Reason for that. ...
    (comp.lang.cobol)
  • Re: Why Is This Bad Code?
    ... What happens if the programmer ... If there were some other reason to abstract them, ... > polymorphism. ... time permits. ...
    (comp.lang.cpp)
  • Re: Stroustrups FAQ causes infinite loop when executed
    ... There may be ways in which inheritance could ... programmer could not have foreseen. ... >> complex calculations such as multiplying numerous transformation ... >> reason to cap the class. ...
    (comp.lang.cpp)
  • Re: When will Federer be cured of mono ever?
    ... likely reasons for Fed's drop in results than some horseshit mono excuse. ... set from losing in q/f? ... out of USO in q/f? ... and I've had no reason *at ...
    (rec.sport.tennis)
  • Re: should every thing be zero indexed?
    ... they usually count with zero indexed ... > There is a logical reason why you should do this with arrays, ... I just don't know why a programmer would want his 4th ... efficient code is probably produced by counting down, ...
    (comp.programming)