also try #code-reviews perhaps?

I though about that, but it's not about Clojure code.

Ah, right!

Off topic - it would be more accessible (for me) to have this info in ClojureVerse instead. As it is slack will disappear everything in a few days.

That's a good suggestion

Doesn’t NoStarchPress usually have robots doing interesting things?

Certainly they have a distinctive aesthetic at a minimum, even if not consistently robots.

Indeed, thanks!

Packt publishing use flowers

I would use variations on Islamic or Celtic patterning fwiw 😃

Seems like they use flowers very occasionally though. I can't find any particular pattern to their cover designs at https://www.packtpub.com/eu/all-products/all-books Patterns are nice! And I don't think you could ever run out of them. :)

I would have every cover be a slight variation of the one before it, so it would make a giant unwieldy flipbook.

And the book series itself then could be about creating flipbooks.

Exactly

Or different breeds of cows. It’s amazing how many there are.

I can't seem to open the link but i'll take a guess. To me, it's about learning the right level of communication for the problem at hand. Consider that our programming languages are made for humans to communicate with other humans. When people say clojure is more data flow/data oriented they mean that it promotes communication through datastructures (lists, hashmaps, sets, vectors) Which both let us easily write programs that write programs (macros) and communicate important common performance considerations (e.g hashmaps constant lookup). It also makes those data structures (shorter syntax) and easy to compose (they share a common interface "seq"). The result is that its very easy to communicate high level idea's about how the data flows through your system. The best place to go to learn more imo is reading the history of clojure by the author himself. I'm working through it now and its very enlightening. You should feel free to ask questions about it here.

Java helps you put data in a easily identifable place to get and act on it. Clojure easily lets flow the data to where it needs to go. Given business data typically needs to either be persisted (e.g browser) or stored (e.g postgres) its more important for the programming language to facilitate "data flow". Which are the types of problems uncle bob tackles.

if you haven't seen https://www.youtube.com/watch?v=ROor6_NGIWU , I would check that out. the talk covers how you can build a system of simple machines that you hook together. it's focused on systems in the large, but you can do similar things in the small.

there are even two transcripts for that talk here: https://github.com/matthiasn/talk-transcripts/tree/master/Hickey_Rich :)

Thanks guys for the tips, today I've seen the Rich's talk (again) and some things make more sense now. In general, it seems to me to be the difference between a place and flow orientation, or Turing machine and lambda calculus in the most general sense. Don't you think? Anyway, I've found more sources on this topic and find it very interesting. Seems like a great idea for my blog.

I think this is the best talk regarding this topic https://youtu.be/kP8wImz-x4w

Thanks!