Sumant’s Reviews > Code Complete: A Practical Handbook of Software Construction > Status Update
Sumant
is on page 51 of 914
One common rule of thumb is to plan to specify about 80 percent of requirements up front, allocate time for additional requirements to be specified later, and then practice systematic change control to accept most valuable requirements as the project goes on.
— Nov 17, 2017 08:48AM
Like flag
Sumant’s Previous Updates
Sumant
is on page 575 of 914
If you choose this approach, be sure the architect really is respected. Sometimes a project architect is just a senior person who has been around too long and is out of touch with production coding issues. Programmers will resent that kind of "architect" defining standards that are out of touch with the work they're doing.
— Mar 24, 2019 02:10AM
Sumant
is on page 123 of 914
The more dogmatic you are about applying a design method, the fewer real-life problems you are going to solve. -Plauger
— Dec 01, 2017 03:50AM
Sumant
is on page 87 of 914
Overly costly, ineffective designs arise from three sources
1. A complex solution to simple problem.
2.A simple, incorrect solution to complex problem.
3. An inappropriate,complex solution to a complex problem.
— Nov 22, 2017 09:25AM
1. A complex solution to simple problem.
2.A simple, incorrect solution to complex problem.
3. An inappropriate,complex solution to a complex problem.
Sumant
is on page 70 of 914
Programmers who program into a language first decide what thoughts they want to express, and then they determine how to express those thoughts using the tools provided by specific language.
— Nov 18, 2017 11:49PM
