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
+10-13
Original file line number
Diff line number
Diff line change
@@ -134,7 +134,6 @@ Best practices in Coding, Designing and Architecting Java Applications
134
134
- Onboarding a new programmer. Makes him comfortable with all the new things he has to encounter.
135
135
- Implementing a complex functionality.
136
136
- Next question is how to approach a Code Review. Difficult to cover everything. I would make a start. When doing a code review, I start with static analysis results (for example, sonar). I spend 10 minutes getting an overview of components and/or layers (focusing on size and dependencies). Next I would pick up a unit test for a complex functionality. I feel unit tests are the best place to discover the dependencies and naming practices (I believe good names = 50% of maintainable code). If a programmer can write a simple and understandable unit test, he can definitely write good code. Next, I look for 4 principles of Simple Design. After this, there are 100 other things we can look for - You decide.
137
-
- PDF - https://www.mindmup.com/#m:a1972695706ab201340d4b0beac29b8bfc
138
137
139
138
### Why should you not take code quality tools at face value?
140
139
- If a project has a great Sonar report, does it mean it is perfect?
@@ -144,7 +143,7 @@ Best practices in Coding, Designing and Architecting Java Applications
144
143
145
144
## Security
146
145
Hmmm... Should I really explain the importance of Security?
- PDF Presentation https://www.mindmup.com/#m:g10B8KENIDghuHAUjlYVmlfSllzTzg
162
+
- PDF Presentation https://github.com/in28minutes/java-best-practices/blob/master/pdf/LoadAndPerformanceTestingBestPractices.pdf
164
163
- Have clear performance objectives. That’s the single most important objective. Decide Peak Load, Expected Response Time, Availability Required before hand.
165
164
- Establish clear performance expectations with the Interface Services
166
165
- An application does not work on its own. It connects with a number of external interfaces. Establish clear performance expectations with the Interface Services
- PDF : [https://www.mindmup.com/#m:g10B8KENIDghuHAZWh2SEhSNTdNNjA]
197
+
- PDF - How to be a good architect : https://github.com/in28minutes/java-best-practices/blob/master/pdf/How%20to%20be%20a%20good%20Software%20Architect.pdf
199
198
200
199
### Architect Responsibilities
201
200
- Having good governance in place. Good review processes in place for Architecture, Design and Code.
@@ -220,7 +219,7 @@ Most important qualities I look for in an Architect are
220
219
221
220
222
221
### REST Web Services
223
-
- PDF https://www.mindmup.com/#m:g10B8KENIDghuHAYmFzM0daOU80SDA
222
+
- PDF TO UPDATE https://www.mindmup.com/#m:g10B8KENIDghuHAYmFzM0daOU80SDA
224
223
225
224
#### How should you document your REST Web Services?
226
225
- Swagger
@@ -229,7 +228,7 @@ Most important qualities I look for in an Architect are
229
228
230
229
231
230
### Layers
232
-
- PDF https://www.mindmup.com/#m:g10B8KENIDghuHAemVIS2RvT1JDOUE
231
+
- PDF https://github.com/in28minutes/java-best-practices/blob/master/pdf/LayeringInJavaApplications.pdf
233
232
234
233
#### Business Layer
235
234
Listed below are some of the important considerations
@@ -323,16 +322,14 @@ Listed below are some of the important considerations
0 commit comments