WeSearch

Clojure Freed Me from the Ceremony

Carlos Blanco· ·2 min read · 0 reactions · 0 comments · 29 views
TL;DR · WeSearch summary

The author reflects on their experience using Clojure at Nubank, highlighting the reduction in code complexity compared to traditional object-oriented programming. They appreciate how Clojure allows for simpler expressions of logic without the extensive scaffolding required by languages like C# and Java. While acknowledging the merits of OOP, the author finds that Clojure's functional programming approach aligns better with backend data transformation tasks.

Key facts
About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

Original article
Software Theory · Carlos Blanco
Read full at Software Theory →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherSoftware Theory
Canonical URLhttps://carlosblanco.github.io/clojure/functional-programming/2020/10/15/functional-programming-clojure-backend-simplicity.html
Publication timeMon, 18 May 2026 15:54:11 +0000
Retrieval time2026-05-18T16:04:56.662Z
Last seen2026-05-18T16:04:56.662Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterhrDhvzQPSUNZ
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

How Clojure Freed Me from the Ceremony Oct 15, 2020 • Carlos Blanco A year into working at Nubank — where the backend runs almost entirely on Clojure — I’ve had enough time to form a real opinion rather than a first impression. The thing that keeps standing out to me is how much less code I write to accomplish the same things I used to do in C# or Java. Not fewer features, not less correctness — fewer words. When I was watching Rich Hickey talk about how standard libraries in some OOP languages end up with deeply layered class hierarchies just to represent simple concepts, something clicked. The complexity isn’t always in the problem. A lot of the time it’s in the language’s way of expressing the solution.

Excerpt limited to ~120 words for fair-use compliance. The full article is at Software Theory.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Software Theory