If you liked this video and want to support my channel, please consider buying me a coffee ☕. Your contribution helps me create more content like this. You can donate at: 👉 Ko-fi: ko-fi.com/andreyfadeev 👉 Buy Me a Coffee: www.buymeacoffee.com/andrey.fadeev I'm truly grateful for your support, and thank you for watching! 🙏 P.S. Please like, comment and subscribe to the channel 🚀 Forgot to mention in the video, there is a repository in github with all source code, link in the description box. Happy coding 🎉
Amazing content so far! I am using your videos to re-learn Clojure development. I enjoy the language a lot but since I don't work with it sometimes I lose contact with Clojure. This time I came back and found your material and it's being very useful to remember the language and some of the libraries.
Thanks a lot for this video Andrey. In deed testing one of the initial parts when learning a new language to start appplying TDD. As a personal note I am learning clojure for a personal motivation, coming from the software craftmanship in Barcelona, with the aim of rising my skills with functional paradigm. My interests are also into the use of clojure for data analysis so let see. By know I would like to have a simple application (an army builder for a miniature games called mordheim) with clojure and clojurescript or HTMX...let see. Thanks again!
That's cool 👍 I've personally never regretted my decision to switch to Clojure many years ago and I've definitely learned a lot from the language and the community!
Great video, like all the others on this channel. I noticed one point that was once pointed out to me during a review. Instead of constantly generating a new random-uuid in tests, I was recommended to generate a static uuid once and use it in the test all the time. Of course, the chance of generating the same uuid is negligible, so it’s just interesting to know what you think. Do you use random uuid in your tests at work or do you prefer a static option?
I just tend to use random-uuid in tests (like in the beginning of the test in let block generate test data and than use it in assertions), same in the production code
Hi @andrey.fadeev, I am working through this tutorial and have been stuck for a while on an issue with the function get-tod-by-id. Specifically, I was receiving "Cannot invoke "java.util.concurrent.Future.get()" because "fut" is null" when dereferencing the :state-atom. This was causing an issue in the tests when caling client/get for get-todo-test. Why would this be happening? I can provide more details but either way, thank you for the time you've put into this tutorial!
Hi, hard to tell what is exact problem, but feels like when you get atom from deps it's nil for some reason, can you add println before and check what do you have in the state-atom (without destructuring)
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
If you liked this video and want to support my channel, please consider buying me a coffee ☕. Your contribution helps me create more content like this. You can donate at:
👉 Ko-fi: ko-fi.com/andreyfadeev
👉 Buy Me a Coffee: www.buymeacoffee.com/andrey.fadeev
I'm truly grateful for your support, and thank you for watching! 🙏
P.S. Please like, comment and subscribe to the channel 🚀 Forgot to mention in the video, there is a repository in github with all source code, link in the description box. Happy coding 🎉
You are doing great work by passing the knowledge gained in the industry back to the community. Hope you get to 1k subs soon!
Hi, thanks! Comments like this are really giving motivation :)
Amazing content so far! I am using your videos to re-learn Clojure development. I enjoy the language a lot but since I don't work with it sometimes I lose contact with Clojure. This time I came back and found your material and it's being very useful to remember the language and some of the libraries.
Good stuff! 👍
Great videos bro
Cheers mate 🙌 much appreciated 👍
Thanks a lot for this video Andrey. In deed testing one of the initial parts when learning a new language to start appplying TDD. As a personal note I am learning clojure for a personal motivation, coming from the software craftmanship in Barcelona, with the aim of rising my skills with functional paradigm. My interests are also into the use of clojure for data analysis so let see. By know I would like to have a simple application (an army builder for a miniature games called mordheim) with clojure and clojurescript or HTMX...let see. Thanks again!
That's cool 👍 I've personally never regretted my decision to switch to Clojure many years ago and I've definitely learned a lot from the language and the community!
Thanks!
Great video, like all the others on this channel. I noticed one point that was once pointed out to me during a review. Instead of constantly generating a new random-uuid in tests, I was recommended to generate a static uuid once and use it in the test all the time. Of course, the chance of generating the same uuid is negligible, so it’s just interesting to know what you think. Do you use random uuid in your tests at work or do you prefer a static option?
I just tend to use random-uuid in tests (like in the beginning of the test in let block generate test data and than use it in assertions), same in the production code
Hi @andrey.fadeev, I am working through this tutorial and have been stuck for a while on an issue with the function get-tod-by-id. Specifically, I was receiving "Cannot invoke "java.util.concurrent.Future.get()" because "fut" is null" when dereferencing the :state-atom. This was causing an issue in the tests when caling client/get for get-todo-test. Why would this be happening? I can provide more details but either way, thank you for the time you've put into this tutorial!
Hi, hard to tell what is exact problem, but feels like when you get atom from deps it's nil for some reason, can you add println before and check what do you have in the state-atom (without destructuring)
I had the same problem. Everything go right after re-jack-in my REPL. Do you resolve your issue ?