Codetown ::: a software developer's community
What is Groovy and why should I care?
Hello again, it's me, Adam. Earlier this year, I finished my self-published book, Learning Groovy, which is about, well, learning Groovy. It also covers the top Groovy-based tools and frameworks, Gradle, Grails, Spock, and Ratpack.
I've enjoyed using Leanpub as a place to work on my books (What's new in Java 8 and others). It is really easy and developer friendly. It uses a Dropbox folder and you can write your book in Markdown (which I did). I've enjoyed a fairly constant trickle of purchases, but I was frustrated that I never had enough time to devote to the other huge part of self-publishing: marketing. To be really successful with a book, it needs to be marketed really well. You need to put in a lot of time and money. So, when it came to publishing "Learning Groovy," I approached several publishers to do the marketing for me.
Luckily, one of them accepted, and I'm currently in the process of final edits (publisher shall remain anonymous for now).
This means that you can only get the self-published version of "Learning Groovy" for a limited time. Once it goes to the publisher, I have to take down all my versions per the contract.
"What is Groovy and why should I care?" you ask? First of all, what rock have you been living under? Secondly, Groovy is a mature and flexible open-source language that runs on the JVM. Want to learn more about functional programming, want optional dynamic typing, easy restful services, easy reactive web applications (Ratpack)? Maybe you to learn about the most popular build framework and testing frameworks for Java (Gradle and Spock)? Groovy is where it's at.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Pinterest Engineering cut Apache Spark out-of-memory failures by 96% using improved observability, configuration tuning, and automatic memory retries. Staged rollout, dashboards, and proactive memory adjustments stabilized data pipelines, reduced manual intervention, and lowered operational overhead across tens of thousands of daily jobs.
By Leela Kumili
Franka Passing discusses the architectural shift of Duolingo’s 500+ backend services to Kubernetes. She explains the move toward GitOps with Argo CD, the transition to IPv6-only pods, and the "cellular architecture" used to isolate environments. She shares "reports from the trenches" on managing developer trust, navigating AWS rate limits, and productionizing early adopter services.
By Franka Passing
How can you focus in a sea of results from a large regression test suite? This article describes a stochastic approach that relies on some degree of redundancy in your CI regression test set. This approach does not guarantee you will catch every bug every time, but it gives you your best bet of not missing the subtle signatures of all the bugs uncovered by your CI regression test suite runs.
By James Bornefelt WestfallIn this episode, Thomas Betts and Adi Polak talk about the need for context engineering when interacting with LLMs and designing agentic systems. Prompt engineering techniques work with a stateless approach, while context engineering allows AI systems to be stateful.
By Adi Polak
A 600-run benchmark by Ruby committer Yusuke Endoh tested Claude Code across 13 languages, implementing a simplified Git. Ruby, Python, and JavaScript were the fastest and cheapest, at $0.36- $0.39 per run. Statistically typed languages cost 1.4-2.6x more. Adding type checkers to dynamic languages imposed 1.6-3.2x slowdowns. Full dataset available on GitHub.
By Steef-Jan Wiggers
© 2026 Created by Michael Levin.
Powered by
You need to be a member of Codetown to add comments!
Join Codetown