Does strtok require a non-null token?

[Al Balmer]

My appologies for an unintended insult.



I agree. Maintenance is difficult work and the best programmers
should be placed on maintenance, not new development.
In my experience, however, this is not the case. The term
"Maintenance drone" is all too often appropriate.

You may well be correct. Although I've worked for large companies,
their product focus was never software, and I often worked alone, so
I'm in no position to know how qualified an average maintenance
programmer is. I can relate my experience that many programmers who
consider themselves too good for maintenance work are incompetent,
though

(I worked for one very small company where the entire programming
staff was top-notch - my own <g>)

 

[William Hughes]

You may well be correct. Although I've worked for large companies,
their product focus was never software, and I often worked alone, so
I'm in no position to know how qualified an average maintenance
programmer is. I can relate my experience that many programmers who
consider themselves too good for maintenance work are incompetent,
though

Which touches on an important point. New development is more
fun than maintenance (at least this seems to be a fairly widely held
opinion). Now, as a manager you decide that your are going to
put the best programmers on maintenance. You do this, all your
best programmers leave, you get fired.

- William Hughes

 

[Bob Martin]

Which touches on an important point. New development is more
fun than maintenance (at least this seems to be a fairly widely held
opinion). Now, as a manager you decide that your are going to
put the best programmers on maintenance. You do this, all your
best programmers leave, you get fired.

In my experience the maintenance guys are the real heroes.
The developers quickly knock off something which roughly corresponds to
the original spec then move on.
The maintenance people then get all the bugs out, change it to what was really
required then add all the nice features.

 

[raxitsheth2000]

Which touches on an important point. New development is more
That is the reality...(up to my limited knowledge.)
In someone's Signature in comp.lang.c i have seen,

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."

Derivation From the above stmt.

"If you are doing debugging/Maintance of software you are more clever
than devloper, most probably your senior "


Actually Wrong Thinking here, for detailed discussion there is a thread
on
comp.software-eng named "most software jobs are software maintenance
rather than new development?" and i think some Interesting Thoughts are
there.

In my experience the maintenance guys are the real heroes.
The developers quickly knock off something which roughly corresponds to
the original spec then move on.
The maintenance people then get all the bugs out, change it to what was really
required then add all the nice features.

Have To Agree...


Sorry for giving reply on Not "C lang" related answer,


Cheers
--Raxit

 

[Richard Bos]

Which touches on an important point. New development is more
fun than maintenance (at least this seems to be a fairly widely held
opinion). Now, as a manager you decide that your are going to
put the best programmers on maintenance. You do this, all your
best programmers leave, you get fired.

IMO, the best thing (but probably equally infeasible) would be not to
have maintenance or development programmers, but project programmers.
You developed it, you maintain it.

Richard

 

[William Hughes]

IMO, the best thing (but probably equally infeasible) would be not to
have maintenance or development programmers, but project programmers.
You developed it, you maintain it.

Two problems:

- the lifetime of many (most?) projects is longer that the
time a programmer spends with the company.

-if there is more than one person on the project the
maintenance will be done by the more junior
(an edict that maintenance work is to be distributed
in any other way could only come from a soon to be
fired member of senior management)

- William Hughes

 

[av]

"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it."

yes, but for debug can be enought some routines that find errors
*time* and luck