Back to Java

Java was (essentially) the first language I really dove into. It all began with my Introduction to Object Oriented Program class at UNC, where we learned the fundamentals of Java classes, child classes, and interfaces.

By the end of the class I felt pretty adept in the language. The final project was a sort of Instagram emulator, where an image was submitted and sliders changed things like contrast and grey scale.

After this class, my utilization of Java lagged. Subsequent classes (involving coding) focused on Python, which I personally prefer. Starting Flatiron, I utilized Ruby and Javascript.

On my career journey, I’m trying to put in time improving mainly my Java, Python, and Javascript in order to be competitive. Refreshing myself on Java has been an… interesting process. I’ve forgotten just how clunky the language can feel; explicit variable declarations just feels annoying after working in so many language where it doesn’t matter.

On the other hand, there is a sort simplicity to Java that can be refreshing. The explicitly class-based approach can help with how overwhelming languages can be; there’s very little ambiguity other confusing things like prototyping (no shade to prototyping, I’m just too dumb for it at the moment).

I’m hoping to soon become adept enough at Java that I can incorporate it into my backend development toolkit.