Hard when you can't select the text to catch the difference in the 2nd one. But I'm all for localizing stuff :)
Sick and tired of the same old social media platforms? There are now 93 #fediverse-powered alternatives in the wild, so feel free to pick and mix 🍡 Next on my list? A #GoodReads replacement https://fediverse.party/en/miscellaneous
RT @PR0GRAMMERHUM0R@twitter.com
Code dependencies be like https://www.reddit.com/r/programmerhumor/comments/q3keud
🐦🔗: https://twitter.com/PR0GRAMMERHUM0R/status/1446369810649133084
Services4U by toot.koeln
#cryptpad https://cryptpad.toot.koeln/
#freshRSS → https://rss.gronendahl.de/
#openproject → https://project.gronendahl.de/
#searX → https://search.toot.koeln/
#xmpp → https://xmpp.toot.koeln/register/new/
#wallabag → https://wallabag.gronendahl.de/login
---
Generell gilt bei meinen Angeboten: Eure Daten sind euch !!!
RT @peterhil
This applies to all Lisps — and every other language actually as well.
Cyclomatic complexity is a common measure of the complexity of a piece of code:
https://en.wikipedia.org/wiki/Cyclomatic_complexity
#CodeReadability #CyclomaticComplexity https://twitter.com/askonomm/status/1446112797956325383
Just read a libraries code to figure out how to supplement its Transit readers, easy peasy, because the docs haven't been updated in years and didn't include that tidbit. Feels good! #Clojure #ClojureScript
in #clojurescript
(clojure.string/replace "Hello World Johnny" #" " "")
---
RT @swapnakpanda
🚀 Problem Solving
Given a string input, you need to extract only non-whitespace characters and returns the string.
Example:
Input → "Hello World Johny"
Output → "HelloWorldJohny"
Can you write just a one-liner code for it?
Hint in JavaScript: You can use split, join etc.
https://twitter.com/swapnakpanda/status/1446029146853818368
Very much this! I consider that kind of conscious effort part of learning the language and, indeed, of becoming a better programmer in ANY language. This is one of the super powers of functional programming, and is also a valuable part of algorithmic thinking.
---
RT @askonomm
The thing with Clojure is that unless you make concious effort into splitting functions into small pieces of < 20 lines whenever possible, Clojure is horrid to read…
https://twitter.com/askonomm/status/1446112797956325383
"iterate" is a bad concept for 95% of use cases; it requires thinking about "steps" and aggregators and side-effects. List Comprehensions are usually much better, with the idea being "give me a collection of stuff, and I'll give you some other collection back." Many languages now have these as foreach (instead of for), map, and filter. Only on special occasions does an algorithm actually require consideration of each step in context of the other steps.
RT @scicloj
Do you like #Clojure and wish to know more about #DataVisualization ?
Join our study session this Saturday.
(We're also continuing our usual path with data science study sessions on Sunday.) https://twitter.com/clojureverse/status/1445684349492289544
Full Stack Clojure web app engineer