Tech News
← Home  ·  All topics

Clojure

3 GoKawiil briefs on this topic

Essay recounts 2014 Clojure QA hiring that sidestepped the 'Secretary Problem'

A blog post reflects on a 2014 hiring effort to find QA staff in Pune, India willing to learn Clojure to test a large SaaS backend, describing it as an example of avoiding the classic 'Secretary Problem' from Optimal Stopping Theory by not permanently rejecting candidates once passed over. The author, writing with colleague Mayank's case as the anecdote, contrasts this non-zero-sum hiring approach with what they describe as a currently brutal, post-ZIRP software hiring market in 2026.

Developer observes lasting bias against 'reduce' in code reviews

A software developer shares an anecdotal pattern from years of code reviews: peers rarely object to map or filter functions, but frequently flag reduce as hard to read. The developer notes reduce appears far less often in codebases than similar array methods, despite personally preferring it.

Essay Argues Simplicity in Software Tools Is Overrated Without Deeper Rethinking of Computing

A developer's blog post examines a debate sparked by a talk on debugging a nine-month software bug, questioning whether 'simplicity' as commonly understood in tools like Unix pipelines actually prevents such problems. The author compares a Unix shell pipeline and an equivalent Clojure program for word-frequency counting, showing that while both appear simple on the surface, modifying either to preserve original word order reveals hidden complexity and rigidity in the Unix approach.