Robert Avram

@stefanscheidt I sadly don't think so. :(

1.5 years later, another peculiar talk. Thank you #DigitalExchange. As promised, here's the slides to my talk: Lecturs in Wonderland bit.ly/3oqfhgt

@kaiftait CV entry: "Certified hardware engineer with years of hands-on experience"

🤣 embarrassing how long it took to write hello world

@stefanscheidt Let's just say that a dentist's drill is more tolerable than the rules imposed on publishing.

Torture in the middle ages: - Boiling, Iron Chair, Head Crusher Torture in the modern ages: - Deploying to Sonatype

@mrebbert Looks fine to me. Just needs assembling.

@caze73 I'll take some.

Stop snowing! NOW!

@mstk Your functions don't commute

Tell me you're a Haskeller without telling me you're a Haskeller.

@ajchambeaud I'm glad you enjoyed it and thank you for your kind words! :)

This talks is one of the best tech talks I've watched. Not only the topic is super interesting and well exposed but the storytelling is just epic. Extra points for the slides design and time management 💯 💯💯 kudos to @amrobert11 #Haskell #FP youtube.com/watch?v=y5jZnM…

TIL: #Scala 2.13 *drastically* changed the behavior of ExecutionContext.global, which now gives ~zero parallelism in many cases unless you explicitly add blocking{} blocks Time to make friends with Executors.newFixedThreadPool and audit all my use sites github.com/scala/bug/issu…

@thedeemon_lj @candeira The distinction with transducers is that they're designed to behave this way irrespective of datastructure. The idea is you compose these higher level abstractions generically as much as you want and at the end apply them on any datastructure you desire. (or Clojure supports)

@candeira In Haskell this is the default. If you map a list with one function, then another, then third, the list will be iterated only once thanks to the laziness. No need to invent any transducers.

I have this conspiracy theory that Rich Hickey actually knows Haskell inside and out, he just never brings it up. I hope it's true, that would delight me so much

@thovid Compose* ;)

@umuesse Masochismus

Frage in die Runde: Wie lautet der Begriff für die Tatsache, dass man an einem Projekt festhält, obwohl man weiß, dass es sinnvoller wäre, es zu beenden? Man hat aber schon zu viel da rein investiert, weshalb man es weiter durchzieht. #mindless

“This is the first time in human history our planet’s atmosphere has had more than 415ppm CO₂." “Not just in recorded history, not just since the invention of agriculture 10,000 years ago." "Since before modern humans existed millions of years ago." independent.co.uk/environment/cl…

Morgen Abend noch nichts vor? Keine Lust auf Weihnachtsmarkt? Dann komm zum @rewedigital #Ilmenau Meetup mit @amrobert11 und einem super Vortrag. PS: Glühwein gibts es auch! #rewedigitalTH meetup.com/de-DE/REWE-dig…

Danke an unsere diesjährigen Speaker: @cmeter_ mit zwei Einführungstalks und zusammen mit @jbendisposto fuhren sie den Rover über den Mars, @amrobert11 zeigte uns Reinforcement Learning, @Wire_Daemon baute GUIs mit JavaFx in Clojure. (1/2)

A regular salary is a safety net. You can take risks, you can start long-term projects, you can learn things that aren't instantly marketable. We put in the effort, energy, and inspiration because we want to be better, not because we desperately need the money.

Ready to listen to the incredible tale of the consequences of effect models? Travel to the Realm of Programmia with @amrobert11 in his #LambdaWorld storytelling hour: buff.ly/2q98KLe #FunctionalProgramming

@marcoshuttle @Lambda_World I don't know of any piece of literature that molds together a chronological history of them. I sort of derived it based on how they came to be introduced into the world of programming. If you follow the individual paper releases, you can somewhat ad hoc-ly derive a history.

I've told a fairly obscure story in a talk at @Lambda_World a couple of weeks ago. You can find the video here: youtu.be/y5jZnMImbMY