-----<br />SCJP, SCWCD, SCMAD, SCEA, CAPM
Originally posted by David Aslan:
Would you resign if the code is unmaintainable?
Mani
Quaerendo Invenietis
Originally posted by David Aslan:
Would you resign if the code is unmaintainable?
Originally posted by Shankar Sidhaarth:
However my boss is not technical guy but functional guy. ... When I speak complex jargons
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Mark Herschberg
quote riginally posted by David Aslan:
Would you resign if the code is unmaintainable?
Of course not. If you resigned every time you encountered a problem you'd never last in a job. The only time to quit is when you have a serious problem which impedes work/success and will not be given the support (tools, time, help, etc) to change it.
5. You're just as appreciated as the the junior programmer.
Tony McClay<br />Architect / Developer, SOA and Jave Enterprise Edition 1-5<br />---------------------------------------------------------------------- <br />Sun Certified Enterprise Architect, Enterprise Edition 5 (Step 1 of 3)<br />Sun Certified Web Component Developer, Enterprise Edition 4<br />Sun Certified Business Component Developer Enterprise Edition 5<br />Sun Certified Programmer , Standard Edition 5.0
Originally posted by David Aslan :
Would you resign if the code is unmaintainable?
1. No comments or javadocs.
2. No design methodology.
3. Boss doesn't know or appreciate a singleton, factory, or even what is the meaning of encapsulation, coupling.
4. Boss only cares on the bug or feature added. He doesn't want to know about how to do unit testing, defensive coding.
5. You're just as appreciated as the the junior programmer.
6. Code looks like C disguised as Java.
Even after you've spoken up that there needs to be coding standards, design documents, etc. and he won't listen to you.
[ August 08, 2007: Message edited by: David Aslan ]
CIAO Peter M. Cooke
-----<br />SCJP, SCWCD, SCMAD, SCEA, CAPM
Originally posted by David Aslan:
Would you resign if the code is unmaintainable?
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
OCUP UML fundamental and ITIL foundation
Gabriel
Software Surgeon
Originally posted by san ban:
NO,we took the crisis as an oppurtunity to turn things in our favor and went ahead with full passion.The result? Similar to what Grabiel achieved. The product not only scaled but also became aound 900-1000% more efficient.
Originally posted by Luke Kolin:
Perhaps I'm being overly pedantic here, but by definition the code was maintainable, since you got it to work and achieved good results.
Personally, I'd be more curious as to the responses if one was placed in a situation where one was incapable of fixing the code, due to some combination of excessive complexity combined with management (or other team members') refusal to make the investment in a significant refactoring.
Cheers!
Luke
Gabriel
Software Surgeon
Alongwith being a good coder, try to be a good professional as well!