Ramesh’s Reviews > The Productive Programmer (Theory in Practice > Status Update

Ramesh
Ramesh is on page 99 of 222
TDD Creates consumption awareness when you create a unit test – You are creating the first consumer of the code under development.

TDD requires you create the first consumer. The code will then be written in a way that makes you think how this will be used. BETTER TO BE TDD all the time.
TDD Forces you to mock dependent objects
Nov 29, 2021 05:25AM
The Productive Programmer (Theory in Practice (O'Reilly))

flag

Ramesh’s Previous Updates

Ramesh
Ramesh is on page 207 of 222
 Usage of Groovy to Generate XML files rather than writing XML.
 If you already have XML then use Groovy to build builder files and then switch to Groovy as below

 Installation of CYGWIN – Need some good examples to demonstrate the power of Unix Shell Scripting like find, grep etc

Completed (for now) on Boxing Day 2021
Dec 25, 2021 10:53PM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 178 of 222
Polyglot Programming
Ola Pyramid
DSL on top of the pyramid for business-domain based work
Groovy for day-to-day coding - Dynamic Language
Java at the bottom for a stable steady language - Statically Typed

Editors and the features that are required
Dec 25, 2021 07:42AM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 165 of 222
Composed and SLAP - Single Level of Abstraction. Page - Code at Page 156 is clearly refactored using composed method, it could have been extended to SLAP also not sure why new classes were introduced.
But a fantastic chapter on refactoring and introducing Abstraction, Method < 15 lines, Single Responsibility
Dec 25, 2021 06:55AM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 155 of 222
Groovy
Angry Monkeys
Fluent Interfaces - Method Chaining
Use Groovy and Spock for faster and expressive Unit Testing
Dec 23, 2021 03:04AM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 143 of 222
YAGNI and
Essential and Accidental complexeties
Maximize work on Essential Complexity; kill Accidental Complexity
Law of Demeter - " never use more than one dot for any method call"
eg homer.getJob().setPosition("Janitor");
Dec 21, 2021 09:39AM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 135 of 222
Dec 18, 2021 09:12AM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 129 of 222
Good Citizenship
Do not break Encapsulation. Dont put Public setters/getters for Private variables. Calendar is a good example.
dont rely on default Constructors
Dont rely on static Methods therefore dont rely on Singleton Objects instead use Factory method
Dec 12, 2021 11:18PM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 129 of 222
Dec 12, 2021 11:16PM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 119 of 222
Hamcrest, PMD, FindBugs, Cyclomatic Complexity of Nodes and Edges
Formula is
Number of Edges - Number of Nodes + 2
Edges represent the execution path and Nodes represent Lines of Code
Dec 05, 2021 02:34AM
The Productive Programmer (Theory in Practice (O'Reilly))


Ramesh
Ramesh is on page 94 of 222
dbDeploy not sure what it accomplishes.
yDoc - Now yWorks is a UML doclet and is it only for Java?
Nov 27, 2021 11:16PM
The Productive Programmer (Theory in Practice (O'Reilly))


No comments have been added yet.