still working with clojure for weeks … I feel my code is like imperative/OO but with a brand new syntax can you guys provide some feedback to improve my code ? (usecase: user must activate the account to receive the api-key )

(defn find-activation-code [db user-id activation-code]
    (if-let [user (users/find-activation-code db {:id user-id :activation_code activation-code})]
      user
      :not-found))

(defn mark-user-as-active! [db user]
  (users/update-active-status db (:id user) {:active true}))

(defn activation [{:keys [components params body]}]   <----------------------------- MY WEB HANDLER ENTRYPOINT   (web/POST "activate/:id" request (r/activate request))
  (let  [db (:db components)
         user-id (:id params)
         activation-code (:actication_code body)
         user (find-activation-code db user-id activation-code)]
    (case user
      :not-found (r/not-found)
      (r/ok (:api_key
              (mark-user-as-active! db user))))))

On java probably I would use Optional on find-activation-code return type and on my activation I would map the optional ( chain )

how to increase my code above .. make it more clojure idiomatic

Hi all, I am having problems and just asked a question in the "planck" room. Would appreciate help. 🙂 thanks

@drewverlee filter?

Hey everyone, Is anyone about to load files with references to libraries from cljsjs from a REPL? Whenever I try it always says something like, "No such namespace: cljsjs.moment, could not locate cljsjs/moment.cljs, cljsjs/moment.cljc, or JavaScript source providing "cljsjs.moment"

Hello everyone. I've been dabbling in clojure for a couple years now, I haven't built anything serious due to lack of time, but I really enjoy the interactive development of a lisp and have been steadily improving. I just started at a company and joined a team that's building a new product for the company. We're getting close to releasing an MVP. It's mostly a Java shop using Spring and swear by DDD. I have noticed that this company, and my team in particular is quite open to new ideas and technologies. So, I casually brought up Clojure today with the Team Lead, and he was very open to it. He said that if I could show where in the system it could really improve something, we could write it up as a micro-service, and see where to go from there. 😲 Ok, so I need to identify where in our system clojure would shine vs current java approach. I know that clojure is very good at dealing with concurrency, but afaik we haven't had to deal with any concurrency, or haven't had any issues with it. My first thought was to find something rather complex in our system, and see if I can replace it with something elegant in clojure. Any thoughts? Any good articles that talk about what problems clojure is particularly good at solving? Also, Domain Driven Design is a fairly new concept to me. Is it something that fits well with clojure? atm I'm assuming that it is independent of the programming language. Thanks in advance!

@sammy.castaneda90 This might be a good talk to share at work https://www.infoq.com/presentations/DDD-Clojure

@sammy.castaneda90 For me Clojure’s biggest selling points is about the workflow experience, if you write pure functions and control your state, you end up with a system that is easy to interact with. I would highlight how clojure makes doing the right thing easy, as a bonus, explaining this will hopefully make everyone more aware of some different and helpful software design principles.

I’m also willing to bet, though i haven’t yet experienced it, that Clojure projects tend to evolve much easier then java projects, as despite arguments i don’t understand, i feel like Clojure projects are much more uniform then java ones.

@sammy.castaneda90 We introduced Clojure at work (back in 2011) for a specific background process that continuously read data from a MySQL database, filtered and transformed it, and published it as XML via http to a search engine we use. That sort of continuous ETL process was a very good fit for Clojure.

We expanded from that one process to a code base that is currently around 56,000 lines (production code, and just over 19,000 lines of tests).

@sammy.castaneda90 I would recommend something smallish and self-contained. At $lastJob I built a simple web app for managing our localization strings. Basically a web front end to a db, as new strings are added to our main product, put them in the db, then once per release export to Excel to send to the translators. It was a good “hey here’s what Clojure can do” because if it failed we could always go back to the Confluence page we were using before, but if successful it really streamlined the round-trip from the code to the translators and back.

Something well-defined and straightforward is a good call. You probably won’t wind up with a system architecture with which you’re happy on your first go.

^^^ what he said. If my team were proposing this, I would suggest porting an existing microservice, and likely not the “gnarliest” one, and take it all the way to deployment in a dev environment (if not prod). Keep notes on the development workflow, review and critique the resulting code, observe if there were any complications in deployment, etc.

Even if you’re successful in demonstrating the utility of clojure

@donaldball that's definitely something I'm afraid of: Building something that doesn't seem extendable or maintainable, because I'm new to the language.

I guess I figure that’s not something to be afraid of, it’s just something to expect 🙂 But hopefully if you keep the scope small, you can evolve it into something you do like.

Alright, I'll look for something small, but also something that can show the effectiveness of Clojure. Thanks everyone! I'll definitely stop by again if I have any questions 🙂

I would specifically avoid concurrency on the smallish/self-contained thing that you choose @sammy.castaneda90

having done maintenance on a “I hear clojure is good for concurrency, let’s learn clojure and concurrency” codebase, I heartily agree

@sammy.castaneda90 if you have an existing graphql service, converting it to Lacinia (or parts of it) could be a good start. Clojure boasts a great reloadable workflow and good scalability in practice. In my experience, any kind of service in an object oriented language gets to be pretty bloated pretty fast. In my experience, if you can make the life of a developer easier (i.e. less time waiting on builds and local deployments every day), then you can win them over eventually.