• General pacing is way too fast
  


• Using keybinds (Control + Shift + O) can also confuse these people
  


• You should have no issues of your own present (confusion moments, jdk8 vs jigsaw, exceptions, clicking buttons accidentally) while presenting a topic (If I do this I fix it and backtrack a bit, then continue on in the same recording. Editing can cut out the mistake)
  

• Fine as is
  

• Too slow, obvious sections can be sped up / cut out and redubbed in editing
  


• Simplistic implementation, you can make this more abstract and then dive into proper software engineering principles like architecture & maintainability
  

• Proper logging would be a bonus (Then using the logging framework to log the exception rather than letting it be raised all the way to the entry-point)
  


• Client and server in this example have some common logic, a common parent can be made to keep things simple.
  


• Using Serializable is simple, but ineffecient. Plus it makes code version-specific, so if you had an outdated packet structure being sent to a new server (With a modified packet class), it wouldn't be able to properly deserialize the incoming packet. The link before is a bit old, but gets the point across.
  

1. Maven
   • Using dependencies (Looking stuff up on maven central / google)
     
   
   
   • Using build plugins to generate jar files for you that include your dependencies instead of relying on an IDE's jar export feature
     
   
   
   
   


2. Unit Testing
   • JUnit 5 as a maven dependency
     • Why do we write tests?
       
     
     
     • Good practices while writing tests
       
     
     
     • Actually writing the tests, what the different annotations mean, etc.
       
     
     
     
     
   
   
   • Using a proper maven project structure so that you have the following:
     • src/main/java - Used to write the client logic
       
     
     
     • src/test/java - Used to verify client logic
       
     
     
     
     
   
   
   • Using maven's surefire plugin to do automated testing when building your project to verify that things work before you generate your jar file
     
   
   
   • Test-driven development & other design philosophies
     • TDD: The design approach where you write test cases that outline how you want your code to work. It won't compile at first, but then after you write something that looks and feels pleasing you start filling in the holes until it works as you intended when writing the example code.
       
     
     
     
     
   
   
   
   


3. Git
   • Why is version control useful?
     
   
   
   • Examples:
     • Cloning an existing project online and contributing
       
     
     
     • Making a new project and uploading it somewhere
       
     
     
     
     
   
   
   • Online services with Github (Continuous Integration to verify that your commited code compiles and passes unit tests)
     
   
   
   
   


4. Maintainability principles
   • Writing code that is easy to understand, why it is important, and why it should be more important than writing fast/efficient code.
     
   
   
   • Refactoring existing bad code into something that is maintainable.
     
   
   
   • The importance of writing documentation (Javadoc & inline comments)
     • When and how to write comments... Don't write comments like "constructs the XYZ class". Write comments that explain the logic of a whole block of code in a TLDR way. Give examples of this in realistic samples.
       
     
     
     
     
   
   
   
   


5. Java core (Give small examples of what packages do. Keep the samples minimal)
   • Regular expressions
     
   
   
   • Stream & functional programming
     
   
   
   • io vs nio
     
   
   
   • Concurrency (Bit dated, but using RMI as an example to work off of would be killing 2 birds with one stone)
     
   
   
   • The UI frameworks (Swing vs JavaFx)
     
   
   
   • Reflection & Invoke
     • Annotations
       
     
     
     • Meta-programming concepts
       
     
     
     
     
   
   
   
   


6. Java 8 vs Jigsaw & the future of Java
   

(Jun 8, 2019 11:05 AM)GenericSkid Wrote:  -snip-