Blog posts index page 9

Why do we allow poor software quality?

Midjourney prompt: Top down view of a wooden table top with one half clean and with neatly stacked papers while the other half is a mess. The mess consist of pensils, curled paper, coffee stains and trash. Colorful oil painting. Midjourney edit prompt several: 1. Clean wooden table top with neatly stacked paper and a single pencil. 2. Messy wooden table top with trash like curled paper, stains half eaten fruit and a broken pencil. 3. Colorful wooly yarn on table. Poor software quality stems from inexperience, time constraints, and software decay, but these can be countered by prioritizing quality. Not prioritizing quality leads to inefficiencies like slow delivery and higher costs. Investing in maintainability ensures long-term success. Read more...

Creating a Clojure client library for InfluxDB

I’m working on a project where a time series database makes sense and the choice fell on InfluxDB. I found mnuessler/influxdb-clojure an aged Clojure wrapping an older version of the Java InfluxDB client. Being all excited about diving into this new area I thought it would be best to leverage the existing efforts put into making InfluxDB accessible in Clojure. It took me a while to realize that I wasn’t comfortable with all the layers put between me and InfluxDB server.

Read more...

Recent findings on Clojure testing

These days I’m spending time looking into testing in Clojure. I’ve been writing my share of test cases in PHP at work. There we have several tests “freezing” time or mocking services. Both practices are common and something worth learning for Clojure.

Read more...