M0dev

Yeah, I lately tried to do some kind of automated migrations between an old and a new format which requires expert knowledge I don't have myself. In the end the solution also was way to creative with things that don't exist.

About improving development: A colleague suggested what github did with its code review feature (for pull requests) for our on prem bitbucket server.

Got some time at work to work on this topic, but can't come up with a good idea yet.

  * Introduction to Java Programming and Data Structures
  * Head First Java
  * Think Java
  * Clean Code
  * Pragmatic Programmer
  * Effective Java
  * Refactoring
  * Java Concurrency in Practice
  * Test Driven
  * Head First Design Patterns
  * Release It!
  * Kotlin in Action
  * Spring in Action
  * Spring Boot in Action
  * Cloud Native Java
  * Spring Microservices in Action
  * Learning Spring Boot 2.0

Feel free to add more suggestions for the list. Also make sure to share your experience with the ones already on the list.

Thinking about my own career progression so far I came up with the following post.TLDR: I have no clue.

What is your opinion and experience about switching jobs never/once/every 6 months during your first 5/10 years?

Posting this because it bugged me a bit over the last weeks.

Is the only way to increase your salary to jump ships once per year? Also do you think it is valid to stay in a technical role?

Thanks for giving this suggestion, somehow missed the name of that principle until now.

I second that, especially about the good commit messages. At work we have very different work ethics when it comes to commit message.

Another dev working on a different code base was blown away on how I was able to reconstruct a requirement change 6 months ago. Just looking at the last 3 commit messages where the file was involved.

Since then I see him writing better commit messages too :) Think it was one of these eye-opener moments for him.