During a code review.

The first thing I notice is the creation of a thread pool with a configurable size. Great I thought, that fits nicely in our ecosystem where resources are constrained. Services can register themselves, ask for a thread and everyone will play nice.

Then I notice that the code consumes all available threads from the pool for the duration of the applications fucking lifecycle. It holds on to them tightly with it's sticky little fingers. Fucking Gollum.

I asked why they chose a thread pool, because they weren't using it for reasons intended. The answer was, because they saw it used somewhere else and thought it was cool.

Only sheer determination stopped me from beating them senseless with their collection of over-sized plushies.

Your Job Suck?
Get a Better Job
Add Comment