This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aleph (3)
- # aws (5)
- # beginners (65)
- # boot (17)
- # cljs-dev (112)
- # cljsrn (5)
- # clojure (146)
- # clojure-austin (3)
- # clojure-dusseldorf (3)
- # clojure-italy (18)
- # clojure-norway (13)
- # clojure-russia (84)
- # clojure-serbia (5)
- # clojure-spec (24)
- # clojure-uk (84)
- # clojurescript (204)
- # css (1)
- # cursive (21)
- # data-science (3)
- # datascript (21)
- # datomic (26)
- # emacs (5)
- # euroclojure (1)
- # hoplon (8)
- # jobs (7)
- # jobs-discuss (2)
- # keechma (35)
- # lumo (92)
- # mount (1)
- # nrepl (2)
- # numerical-computing (16)
- # off-topic (10)
- # om (58)
- # re-frame (13)
- # reagent (90)
- # remote-jobs (2)
- # ring-swagger (1)
- # spacemacs (9)
- # specter (6)
- # unrepl (17)
- # untangled (56)
- # yada (2)
I started summarising an outline for my talk idea yesterday. The main section is currently defined with two words: "Do magic"
Random word of the day: "covfefe" https://twitter.com/realDonaldTrump/status/869766994899468288
@yogidevbear if you think Martin Kleppmann's book is thick you should read @henrygarner 's https://www.packtpub.com/big-data-and-business-intelligence/clojure-data-science (P.S. I have both. I've read Henry's haven't started Martin's yet)
agile_geek: Can you take a pic of the physical book? Always difficult to gauge a book by a 2D image of it's cover 😉
I will do when I get home..I have two copies one in London (in flat and I'm in office atm) and one at home. I'm travelling home tonight as I'm off tomorrow so I'll do it tonight or tomorrow.
@agile_geek that's really nice to hear, thats exactly what I was going for! The stats side of things will go out of date much less quickly, so it was partly an attempt to ensure some longevity for the text. I'd already make some very different decisions about the libraries I made reference to if I were to write it again, but I'd keep the basic structure and techniques exactly the same
I think that is why I was looking at it initially. I wanted a book that could teach some of the actual DS/algorithm concepts alongside actually doing it in Clojure
@henrygarner yeah, it's a much better book that way. Focusing on libs makes the content 'stale' really fast, although you might sell more books that way! For example, I have two copies of "Web Development with Clojure" and even the 2nd edition is out of date now!
@yogidevbear that's exactly what Henry's book does...take it from a man with two copies (and the eBook so that's 3!) 😄
Must admit I'm looking forward to read Martin's book...I've watched all his talk videos from various conferences. I love his idea of turning the database inside-out with Samza
with pleasure @agile_geek! The least I can do for a valued two-book patron such as yourself
And to think Martin took more than 3 years to write his... still amazes me that @henrygarner only took a year!
I saw a slide deck from @henrygarner entitled Clojure for Machine Learning. Does this mean there's another book in the making?
@yogidevbear not from me! One's quite enough for the time being. It's much more fun to write code instead
au contraire @mccraigmccraig - I think the breakages to existing tech (ie. Clojure) might be quite overwhelming
Java 9 isn't so much about language features as architectural and tooling stuff. From memory the most significant stuff is fine control over imported and exposed code in modularisation of JARs (Project Jigsaw) and the Java REPL.
I can’t remember the details, but something about jigsaw was going to mess up Clojure’s class-loaders iirc
I always said that the one thing I learned at Big Blue was how not to do software engineering.
@agile_geek my friend Mark Stringer is writing a book about project management called "Late and Over Budget"
@agile_geek should be writing, “The Developer on the Trains, Notes from the Previous Day’s Commits”
Jade, () do you feel the content in your book is still relevant 2.5 years after initial publishing?
@jasonbell the random characters introduced into my commits by the erratic movements of the carriage when the Driver's got the "hurry up" are always entertaining. #randomCharacterGenerator
@yogidevbear Mostly yes, it will get the concepts down. There are chapters on Hadoop, Spark and R too and though the tools have changed the concepts are pretty much the same. The chapter on SpringXD is probably as dead as a dodo but it was just before Kafka hit the big time. I’d do all the streaming stuff in Onyx or Kafka Streams now.
@yogidevbear Weka is rock solid and is used a lot in the book, Mahout is just about past it’s sellby date I think, not much reference to it now.
Hmm I want to revise my phantom book title, I think "Unreadable and unchangeable" is probably more my field of expertise....I've only rarely had to tune code for performance....and that's most frequently been SQL!
I really need to write a blog post on monads and explain them... as I don't understand them at the moment 😉
the only reason I would have to write a blog post on monads is to understand it in the first place.
Sorry @seancorfield. Just seen this, but also saw you asking in the other slack group 🙂