You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+35
Original file line number
Diff line number
Diff line change
@@ -118,10 +118,16 @@ Listed below are some of the important considerations
118
118
## Maven Best Practices
119
119

120
120
121
+
###10 Tips For Maven
122
+
[10 Tips for Eclipse and Maven](pdf/10TipsforEclipseAndMaven.pdf)
123
+
121
124
## IDE - Eclipse
122
125

126
+
127
+
###10 Tips For Eclipse
123
128
[10 Tips for Eclipse and Maven](pdf/10TipsforEclipseAndMaven.pdf)
124
129
130
+
125
131
# Practices
126
132
127
133
## Agile and Architecture
@@ -130,6 +136,10 @@ Listed below are some of the important considerations
130
136
- I think most important part of Agile Architecture is Automation Testing. Change is continuous only when the team is sure nothing is broken. And automation test suites play a great role in providing immediate feedback.
131
137
- Important principles for me are test early, fail fast and automate.
132
138
139
+
###Agile and Design
140
+
[Design in Agile Projects](pdf/AgileAndDesign-Evolution.pdf)
141
+
142
+
133
143
## Modern Development Practices
134
144
- Unit Testing and Mocking : We are in the age of continuous integration and delivery, and the basic thing that enables those is having a good set of unit test in place. (Don’t confuse unit testing with screen testing done manually to check if the screen flow is right. What I mean by unit testing is JUnit test’s checking the business logic/screen flow in a java method (or) set of methods). Understand JUnit. Here is a good start : https://www.youtube.com/watch?v=AN4NCnc4eZg&list=PL83C941BB0D27A6AF. Also understand the concept of Mocking. When should we mock? And when we should not? Complicated question indeed. Understand one mocking framework : Mockito is the most popular one. Easymock is a good mocking framework as well.
135
145
- Automated Integration Tests. Automated Integration Tests is the second important bullet in enabling continuous delivery. Understand Fitnesse, Cucumber and Protractor.
@@ -158,6 +168,30 @@ Listed below are some of the important considerations
158
168
159
169
## Productive Developers
160
170
171
+
##Unit Testing Best Practices
172
+
[Unit Testing Best Practices](pdf/UnitTestingBestPractices.pdf)
173
+
174
+
##Architect Qualities
175
+
!(images/ArchitectQualities.png)
176
+
##Architect Responsibilities
177
+
!(images/ArchitectResponsibilities.png)
178
+
##Architect Review
179
+
!(images/ArchitectureReview.png)
180
+
##How to become a good programmer?
181
+
!(images/BecomingAGreatProgrammer.png)
182
+
##Code Quality Overview
183
+
!(images/CodeQuality.png)
184
+
##Design
185
+
###Focus
186
+
!(images/Design-Focus.png)
187
+
###Review
188
+
!(images/DesignReview.png)
189
+
###Java Performance
190
+
!(images/JavaPerformance.png)
191
+
###Modern Development Practices
192
+
!(images/ModernDevelopmentPracticesOverview.png)
193
+
###Static Code Analysis
194
+
!(images/StaticCodeAnalysis.png)
161
195
162
196
## Code Reviews
163
197
@@ -167,6 +201,7 @@ Listed below are some of the important considerations
167
201
### Peer Reviews
168
202
- PDF : https://www.mindmup.com/#m:g10B8KENIDghuHAbWdfWVdrVU1VMEU
0 commit comments