Java on about:rileycsillag fka drewcsillag

Jan20 - A Java Succession Library

Thu, 08 Dec 2016 15:53:40 +0000

Since it’s related to my day job, it’s over on Medium.

Java Server Best Practices

Sat, 25 Apr 2015 11:18:00 -0400

When writing Java servers (or servlets that run in a container), I’ve learned a few things that have saved me a bunch of trouble during development, as well as later on.

Dependency Injection

Injection: if something is singleton (request, global or any other scope), the only things injected to it should also be singleton – otherwise you get implicit singletons of things the singleton holds, and may not be what you want – and generally harder to reason about. Better to have the singleton instances be leaves in the tree of injected things.

Dependency Injection Without A Framework

Thu, 19 Feb 2015 11:18:00 -0400

I think that most people would agree these days that dependency injection is a good thing for many reasons.

It allows you to decouple concrete classes from each other
It makes for a uniform method of object construction
It simplifies plumbing
Makes it easier to make testable classes

The problem that I have with it is that, at least in Java, the main frameworks for doing it, being Guice and Spring, can sometimes be as bad as the problem DI tries to solve.

Why Java?

Sat, 24 Jan 2015 11:18:00 -0400

Background

I started my professional career with a Pascal program (I know that dates me a bit) and then continued with C and C++ and discovered Python around version 1.4 and used it heavily for over ten years, and really didn’t like Java when I first met it (version 1.3-1.4 time frame).

I’ve also used a ton of other languages for real deployed projects, like Python, Ruby, C, C++, Common Lisp (which I <3 love), C#, Clojure, Visual Basic, and Go, so I’m a not the average “blub” programmer saying this.