John Saylor

"Thinking is difficult, that's why most people judge." - Carl Jung

(49/100) #100DaysOfCode #Clojure Will be taking a deeper look into recursion, memoization, and dynamic programming. github.com/jmsaylor/leet-…

(48/100) #100DaysOfCode #Clojure github.com/jmsaylor/leet-…

(47/100) #100DaysOfCode #Clojure Rebooting after a pause. Incorporating tests and enhanced solution design. github.com/jmsaylor/leet-…

(46/100) #100DaysOfCode #Clojure Giving yesterday's code a review, I found some improvements I could make. So funny how sometimes doing anything else but coding will improve your code. Don't overthink it! github.com/jmsaylor/4cloj…

(45/100) #100DaysOfCode #Clojure github.com/jmsaylor/4cloj…

(44/100) #100DaysOfCode #Clojure github.com/jmsaylor/4cloj…

(43/100) #100DaysOfCode #Clojure Great Resource --> 4clojure.oxal.org github.com/jmsaylor/4cloj…

(42/100) #100DaysOfCode #Clojure github.com/jmsaylor/4cloj…

Finally! I got my #arch box set up, and I'll be continuing #100DaysOfCode from it. I'd really like to get #emacs to display firefox and maybe even send tweets from there too. Future seems bright!

(41/100) #100DaysOfCode #Clojure github.com/jmsaylor/4cloj…

(40/100) #100DaysOfCode #Clojure github.com/jmsaylor/4cloj…

(39/100) #100DaysOfCode #Clojure Doing the same thing a bunch of different ways. I love CS because you'd think there's only one way to duplicate something until you study this stuff, among so many other things like that. github.com/jmsaylor/4cloj… github.com/jmsaylor/4cloj…

#100DaysOfCode #Clojure It's not exactly Clojure, but it's still a lisp: elisp is the language implementation for the Emacs editor. github.com/jmsaylor/emacs…

@sabrinaesaquino Rge me flict con

Make a programmer cry with 4 words

(38/100) #100DaysOfCode #Clojure Digging deeper. I had no idea about the lisp-1 / lisp-2 distinction. I put these links here in case you'd like to dive in. The reddit thread is very informative. reddit.com/r/Clojure/comm… clojure.org/about/lisp news.ycombinator.com/item?id=9559770

(37/100) #100DaysOfCode #Clojure I know you're not supposed to peek at the solutions, but you gotta see some of these. I'm always amazed at just how many ways you can express something. 4clojure.oxal.org 4clojure.oxal.org/#/problem/29/s… 4clojure.oxal.org/#/problem/30/s…

@rmcomplexity @willmcgugan I second this. Human language vs. programming language. Perhaps if there is a well defined domain language that facilitates crossover, but I haven't seen it.

@willmcgugan Probably not because whenever this happens what's messy is not the code but the domain. The domain is owned by humans and sometimes people simply complicate stuff. There's other cases where we're looking at it from the wrong angle and changing a small thing simplifies everything

Some code is beautiful, easy to understand, with clearly defined goals, that are easy to test. Some code seems to actively fight against attempts to beautify (and not just formatting). Can all code become beautiful and how much effort should you put in to it?

(36/100) #100DaysOfCode #Clojure Found this code that I just couldn't let my eyes off. I felt I didn't quite understand it so I put some print statements inside to see how it was working. I'm still amazed at this recursive mapcat. gist.github.com/jmsaylor/e55d4…

(35/100) #100DaysOfCode #Clojure Having trouble with the difference between map and mapcat. I understand that mapcat applies concatenation to each result producing a flat result, but using them seems different as well. More to explore. github.com/jmsaylor/4cloj…