Week 2 Retrospective

I have to say that the most challenging part of learning programming so far is keeping track of the syntax between the languages. For example, it’s easy to forget that length is a method in Java and a property in JavaScript.

Google has been my best resource this past week. It’s great to be able to google and read up on how to use functions/methods on the fly.

When it comes to my experience with Clojure…..

This is a very neat language to learn yet incredibly frustrating at the same time. What I love about Clojure is that you can accomplish tasks using way fewer lines of code. The syntax is straightforward yet unforgiving (try omitting one parenthesis and see what happens…)

I keep on forgetting that Clojure does not explicitly return things which really threw me for a loop:) I found myself spending an inordinate amount of time trying to figure out how to make a function return a vector/list with the correct results when tackling today’s Clojure hw.

It didn’t dawn on me until I recently started re-reading lecture notes and online resources that each function returns something in Clojure. Using the item returned and nesting it in another function is how you program in this language.

Goodness — it may take me a while to get used to Clojure.

The biggest thing I learned this week is that testing each line of code is an absolute must with Clojure!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.