I did not intend to stop blogging in 2015 but that’s certainly what it looks like here!
So what kept me so busy that I didn’t get around to blogging anything?
I’ve often said that I try to follow The Pragmatic Programmer’s advice to learn a new language every year. I don’t always achieve it, but I try. As I’ve settled into Clojure as my primary language over the last several years, I’ve made a fair attempt to learn Python, Ruby, Racket/Scheme, Standard ML and more recently Elm. I learned that I like Python, I don’t like Ruby, Racket/Scheme is “just another Lisp” (I already have Clojure) and SML is very interesting but not really widely useful these days (it’s a great language for learning Functional Programming concepts tho'!). I also spent some time with Go last year (don’t like it).
The Elm language is really nice - and useful for building interactive browser-based applications (and games). I’ve been meaning to blog about it for quite a while, and I hope to get around to that in due course. Elm is sort of inspired by Haskell, and that’s really what this blog post is about. Sort of.
Last week I attended The Strange Loop in St Louis. I attended in 2011 and was blown away. I missed 2012 but attended again in 2013 and was blown away once more. I already have 2015’s dates in my calendar. How was 2014?
This was originally posted on corfield.org back in April 2013 and I noticed it was recently referenced by Eric Normand in his recent blog post Convince your boss to use Clojure so I figured it was time to update the article and bring it onto my new blog.
A question was asked in early 2013 on a Clojure group on LinkedIn about reasons to migrate to Clojure for enterprise applications in a Java shop. It’s a fairly typical question from people in the Java world when they hear the buzz about Clojure, and of course asking the question on a Clojure group garnered a lot of positive responses about why Clojure is a good choice. I didn’t feel anyone had really addressed a core aspect of the original question which was, essentially, “Why should I, as a Java web developer, using JPA, JSF etc, choose Clojure instead for an enterprise application?”.
Adapted from a post I made on my old blog in January, 2014, about the first few workshops being planned.
I’ve been an advocate of diversity in IT for a long time. I’m very pleased to work in a company that has an above average ratio of female to male employees, as well as very diverse cultural backgrounds amongst our staff. In most tech communities, diversity is pretty low. It’s why organizations like RailsBridge and Women Who Code and numerous others exist. The lack of diversity hurts us all because a homogeneous community doesn’t have diversity of thought either: diverse teams outperform homogeneous teams.
Originally posted on Google Plus on June 14th, 2014.
Why Java 8 might win me back…
I first started doing Java development in 1997. I was pretty invested in this “new” technology after being initially skeptical with my strong C++ background. I even wrote an editorial in a C++ journal about “the new kid on the block”, casting aspersions as to whether it had what it would take to become popular. Over time, Java became the juggernaut of corporate development and I actually found it quite refreshing after C++’s somewhat obtuse syntax and complexities: Java was a simple language by comparison, with a well-structured, modular library.
At least, it started out that way.
Sometimes it’s very enlightening to look back at the beginning of a project to see how things got set up and how we started down the path that led to where we are today. In this post, I’m going to talk about the first ten tickets we created at World Singles as we kicked off our green field rewrite project five years ago.
We’ve recently started evaluating the New Relic monitoring service at World Singles and when you use their Java agent with your web application container, you can get a lot of information about what’s going on inside your application (JVM activity, database activity, external HTTP calls, web transaction traces).