jakub holý

building the right thing, building it right, fast

Most interesting links of May ''13

2013-05-31 21:59:35General

Recommended Readings

  • Discussion: World's Biggest 'Agile' Software Project Close To Failure - what is/isn't agile, agile vs. waterfall etc; a nice collection of all the possible opinions and misunderstandings. Some of my favorites: waste: '[..]An "agile" project cannot fail and cost Billions because it must always deliver runnable software with a maximum of a few weeks delay[..]' (runnable = delivering value), separation: '[..] my experience has been that separating the designer/architect role from the developer role is fraught with pitfalls. The people writing the code should be the ones designing it, [..]', stability: '[..] On the successful projects that I've worked with in Agile, there's strong stakeholders, good architecture keeping the vision in place and project management that keeps things well orchestrated. Without those in the mix, it'll fail just like all software projects. [..]', waterfall success, people issue: 'The problem here isn't waterfall/agile. The problem here isn't .Net/Linux. The problem here is the parties involved. [politicians and IT dinosaurs]' (learn what's needed from drunk, bitching employees; ignore official nonsense requirements),: simplicity '[..] It would probably be a lot easier if they started by making a simpler tool - instead of trying to calculate everybody's entitlements everywhere [..]', agile suitability: '[..] You cannot use Agile to build a 100-mile canal, as the whole thing would be useless even if you completed 99 miles. [..]'. Some people seem to believe that agile means no architecture and no/too little planning. Some believe that agile = hack now, fix later.
Startups etc.

Clojure Corner

  • B. Batsov's Clojure Style Guide (based on JoC etc.) at GitHub
  • Code quaterly interview with R. Hickey (2011) - motivation behind Clojure (simplicity,..), reusability in C. (vs. Java); many valuable things
  • Clojure in the Enterprise? - about the differences between the Clojure and the enterprise java  (with heavy frameworks such as JPA, JSF, mutable state) ways and difficulties of introducing Clojure due to old-fashioned thinking, limited skills, etc. "Take away objects, mutable state, variables, loops... a lot of Java developers are immediately all at sea and have no idea how to solve even basic problems. They'll try to bend Clojure to their OOP way of thinking and they'll most likely fail." World Singles' experience with Clojure: "We love Clojure. It's made development a lot more fun. We're able to solve harder problems, make changes faster, leverage multi-core concurrency more effectively, and we have a much smaller code base to maintain."
  • Replace Temp with Query in Clojure - in this post we can follow an interesting refactoring from a deeply nested if & let code to a much flatter one (featuring cond to test multiple conditions (instead of guard conditions used in imperative languages) delay to be ably to bind an expression to a local variable without evaluating it yet)
  • The Why and How of Clojure on Android (4/2013) - about the experience of using Clojure on Android, which is little slow and crazy but fun. From the author of the Nightweb app. Key components:  neko Clojure wrappers for Android and for lein-droid building w/o an IDE. Nicer than Java! (This GSoC proposal shows the limitations/future of neko.)
  • Reconstructing Clojure Macros With Speclj - a good idea to learn macros by trying to create one's own implementation of existing Clojure macros, driven by tests that define the expected behavior of the macro (using macroexpand, macroexpand-1, macroexpand-all)
  • Advanced inspector middleware for Clojure nREPL and Emacs (nrepl-inspector on GitHub) - C-c C-i or nrepl-inspect to inspect interactively the value of a var (beware: (require 'nrepl-inspect) fails, however calling nrepl-inspect as a function is ok). Related: Clojure Debugging ’13: Emacs, nREPL, and Ritz (May 17th) - what works, what is missing, how to set up
  • Pithering About » REPL bootstrap pimpage - neat tricks with a custom bootstrap REPL namespace - print last few commits and git branch, pre-loading common libs


Favorite Quotes

C, C#, and Java: Applying some of the best ideas of the 1970s to the problems of today.

- Stuart Halloway in Clojure in the Field, 2013 (slide 6)