HNHacker News
TopNewBestAskShowJobs

trptcolin

606 karma · joined June 3, 2010

[ my public key: https://keybase.io/trptcolin; my proof: https://keybase.io/trptcolin/sigs/6TgQ66pzm2ixGKeblPe7xsKy6XNzzbWE6lDkCt4bHhs ]
submissionscomments
trptcolin··on Free coding exercises for budding gophers (2017)
Super useful exercises, very practical. I can definitely see myself doing some of the paid courses if I'm focused on Go at work longer-term.
trptcolin··on Axes of Quality
Yep, fair, "axes" / "dimensions" was overstating - they're not all actually all orthogonal (all models are wrong, some useful, etc.). Mature engineering discussions have plenty of examples of those tensions, e.g. is it more important for this system to be available or consistent?
trptcolin··on Learn Clojure with Clojure Koans
Right, this needed to be cleaned up and clarified. The only thing you have to do is `lein koan run`, which was listed as an option but the ordering was confusing. I've reworked it a bit now, but feel free to open an issue/PR if things are still hazy: https://github.com/functional-koans/clojure-koans-web
trptcolin··on Learn Clojure with Clojure Koans
Yeah, I hear you. There's definitely room for improvement here. I'm not sure what you mean by not greppable - the file is listed, as is the name of the particular koan. If there's a way to get line numbers displayed here that would be great.

I agree it does make it easier to solve when you can see what you're trying to evaluate to. It was actually a conscious decision to make that not be the case, because it seemed too easy to just fill in the blanks without thinking about what should go there.

trptcolin··on My IQ
Google cached version: http://webcache.googleusercontent.com/search?q=cache:vIrXiKk...
trptcolin··on Why I switched from Ruby back to C++
I hope it was because of this: http://gosu-lang.org/comparison.shtml
trptcolin··on The Groupon dirty secret
ooh, pie charts!
trptcolin··on Ask HN: Best book you read in 2010 and briefly why
The Joy of Clojure - Michael Fogus and Chris Houser (http://www.manning.com/fogus/) Riveting look at the language and functional programming - covers edge cases, gives lots of idiomatic examples, and goes deep into the really interesting parts.