Coming off of the talk of constructors and variables, we’re going to move on to the concept of inheritance.
We’re going to build off of the method discussion from yesterday a bit more and cover the topic of sending n number of parameters of a specific type to a method.
Today we’re going to take a look at overloading in Java.
Today we’re going to take a look at constructors in Java.
Wanted to use a YAML file for some config settings in a new app I’m writing, so I needed to look up how to do so in Java. Lots of people pointed to using Jackson for doing the loading, which seems to be the defacto when doing json reading as well.
Wasn’t really sure what to call this, but it’s something neat and also something that really shows just why using exceptions is so much better than returning back some other junk.
So yesterday I talked about how you can create your own unique exceptions within your package. But how do you go about testing for them? Or testing for any exception for that matter? Let’s take a little look into it.
Honestly this is something that I learned many many months back but evidently never wrote about (I’m not really sure why). I had to do a small side project at work and I needed to revisit how this was done. Thankfully I already had a project completed that I could steal off of!
Today was a weird day. I spent most of it looking through our code at working and being completely confused as to how it’s actually working. The more I read the more confused I got which started me down the path of googling random things to try to escape from drowning.
As unit testing is still very much a new thing to me, I was interested to see how much of my code my tests were actually hitting. I knew that there was some functionality built into intellij, but I was under the impression that it was locked behind a paywall. Turns out it’s completely free to use in the community version!