I love doing fun things. Don’t we all?
And, all else being equal, I like doing the “more funner” things more than the “just plain fun” things.
However, sometimes priorities dictate doing the “just plain fun” things first. This is one of those times.
For the next few days I’ll be putting my React learning on hold, and dig up my Java programming knowledge from back in my Amazon Prime days. You see, I have an interview coming up with a Java-based shop, and I’ve been told that their coding challenges and questions are strictly Java based.
I’m currently reviewing some of my old Java code (an example of which can be found here : https://github.com/rgmarquez/redis2-codechallenge) to revive the Java side of my brain. I need to be reminded of the the syntax, coding conventions, and concurrency best practices that I used to have in the forefront of my mind, before C#, C, and JavaScript pushed it all to the back.
My next post will most likely be my thoughts on going back to Java after the joys (non-sarcastically) of C# and JavaScript async/await programming. I do remember that with Java SOA, we tended to use dependency injection a lot more than I’ve see in C# or JavaScript. I also remember that DI was particularly useful for decoupling dependencies, and for test mocking with little to no change to the target system.
Hmmm, maybe I should do a future blog post describing Dependency Injection, to what extent each developer community (Java, C#, JavaScript) seems to use the DI paradigm, and why.
But for now, on to refreshing my knowledge of Java syntax, memory model, concurrency, automated tests, and best practices…

