What is good code?
Answers were Sorted based on User's Feedback
Answer / rad
These are some important qualities of good code
Cleanliness: Clean code is easy to read; this lets people
read it with minimum effort so that they can understand it
easily.
Consistency: Consistent code makes it easy for people to
understand how a program works; when reading consistent
code; one subconsciously forms a number of assumptions and
expectations about how the code works, so it is easier and
safer to make modifications to it.
Extensibility: General-purpose code is easier to reuse and
modify than very specific code with lots of hard coded
assumptions. When someone wants to add a new feature to a
program, it will obviously be easier to do so if the code
was designed to be extensible from the beginning.
Correctness: Finally, code that is designed to be correct
lets people spend less time worrying about bugs and more
time enhancing the features of a program.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / radhika
A code whether it is good or bad can be known only if it is
tested. So good coding ,results in low bug density(Low
severity +Low prioirity defects or no defects at all)
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / rajeshwar rao
A good code which is===1. Bug free.2.
reusable.3.independent.4.less complaxcity.5.well documented
easy to change is called good code
| Is This Answer Correct ? | 0 Yes | 0 No |
What is Prototype Testing?
What is the difference between bug and defect???
17 Answers Change Control, Tomax,
What is PBX Testing & What is Test coverage?
Can you explain how state transition diagram can be helpful during testing?
what is configuration testing
Case study like you have been assigned in a team which going through a crucial phase of the project. Then how you can save your project to release on time without any defect leakageā¦.
What is difference between SDLC and STLC?
16 Answers College School Exams Tests, HCL, TCS, Verizon,
what is regression testing and what is system testing? whaen we will do the regression testing and when we will do the system testing?
Suppose you testing Calculator application and you got problems like 1/1=2, 2/2=1, 3/3=6, 4/4=1, 5/5=10. Now how will you describe the bug title as well as give the bug description.
How does one do Functionality Testing?
What is your approach when requirements change continuously?
How Can I do database Testing ?