Alessandro Lacava

Let's be honest, learning statically-typed functional programming is harder than the imperative one BUT reasoning about pure functional programs is much easier. I myself prefer to spend more time learning than debugging programs.

@gabro27 Comparing how frequently I change the configuration to how frequently I rebuild the application and deploy, anyway, it’s not a big deal in my opinion. Of course, as usual, YMMV.

@lambdista Except that requires rebuilding artifacts to change a configuration, which is not desirable in my opinion.

Config files should be the exception, not the rule. Configuration is code.

TFW your integration test catches a bug, introduced in an external service, that could have been caught with a simple unit test on their side.

@gabro27 Yeah, probably there are three hard problems in computer science: cache invalidation, naming things and designing a decent Date API.

@lambdista To be fair, java.util.Date getMonth is deprecated and - similarly to java.time - in the future the JavaScript Temporal API will fix this (and many other things)

Now, seriously, why should anyone decide to design it like that? JavaScript is so f*cked up folks! year -> the actual year day -> the actual day month -> the actual...nope! it's 0-based. #syntax" target="_blank" rel="nofollow noopener">developer.mozilla.org/en-US/docs/Web…

@propensive As a firm believer in the presumption of innocence I’m very happy I never signed that letter. Welcome back Jon!

A Statement I am a Scala developer and speaker who was cancelled three years ago. Yesterday I attended the High Court in London to hear an apology from several prominent members of the Scala community for making untrue claims about me on 27 April 2021. I sued them for libel, and they admitted fault and settled, paying me costs and damages. Their allegations were sensational and squalid, but unfounded. Their source was the resentment of one woman following a relationship in 2018, which I ended against her wishes. She fabricated or was offered an alternative narrative, which developed into claims of a pattern of behaviour, and culminated in the defendants’ publication of an open letter, which they now agree is defamatory. In two years of legal action, the defendants never presented any evidence to support their allegations, and admitted in court that they had no proper reason to make them. They have given undertakings to the court not to publish further or similar defamatory statements, or have anyone else do so on their behalf. No signatory contacted me about the allegations before publication. I received no warning, and had no knowledge of the claims’ substance. I only discovered what I was accused of at the same time as I learned of my indefinite exclusion from the community; at the same time everyone else found out. I had no opportunity to defend myself. It is no coincidence that the absence of due process led to an abject injustice. The experience of cancellation and enduring the online hysteria was traumatic. I responded by withdrawing from the life I knew. Its consequences hurt me and people close to me, and have been immiserating. My employment opportunities were obliterated. My charitable and educational projects, and my small business, could not continue. Despite my transferable skills, the allegations were a transferrable red flag recognised across programming communities and industries, and I have barely earned a living since. It has taken two years of legal action to receive fair scrutiny in a forum reliant on facts. This outcome finally vindicates me. Many familiar with the open letter will be surprised by this outcome, given the certainty expressed by some of the letter’s supporters. But they should question why no defence of my libel claim was ever offered. They should seek answers for how so many people became so convinced without evidence. And the defendants’ co-signatories should reassess the credibility of everything that compelled them to support the open letter. Nonetheless, I believe the open letter’s authors were convinced it was the right thing to do. I believe that they wished to show their kindness in response to a story which shocked them. Many of them I have known for years, and know to be good, moral people who were mistaken, and would not wish to be mistaken. Good people can make mistakes, without becoming bad people. So, I offer them the respect and compassion I believe they deserve. I recognise their good intent, and I interpret its consequences charitably. We owe each other civility in ceding the time and space necessary to reflect upon this in open enquiry, without coercion or urgency, so everyone can reach a better understanding of this outcome, and of one another. I have avoided naming any third parties here, and I urge others to do the same. I know too well how it feels to be the subject of online harassment, and I do not wish it upon anyone. I reject the culture of blame and escalation. I have not been idle since 2021. I’ve spent much of my time writing Scala 3, which I believe is an exceptional platform for software development, and deserves far greater success. I am motivated to be part of that success, and I will start sharing my work again soon. pretty.direct/statement.html

So, yesterday I finally decided to tinker with Scala 3. Well, after like 15 minutes I stumbled upon a compiler bug. Srsly, what are the odds? Anyway I discussed it in discord discord.com/channels/63215… and it has readily been reported as a bug by som-snytt github.com/lampepfl/dotty…

A junior dev never applies DRY. A senior dev always applies it. A wise dev applies DRY only where it’s needed.

Don't get me wrong, comments are important. Nevertheless, never stop wondering if what you're writing as a comment can be expressed in your code, instead, and make it clearer.

Annotate every type in Scala. The time you're going to save when you read the code in the future is much more than the one you'd save taking advantage of type inference to avoid some more typing.

When designing your ADTs always keep in mind that: ab + ac + ad = a(b + c + d)

Bollocks! We Italians are great at queueing! (tongue in cheek)

It’s really amazing how many people didn’t understand it was a joke.

@mandubian Congratulations!

Life v1.0 Archived Natural Intelligence On Cuteness Overload Love NaN Sleep Off Life v2.0 Launched

Hey junior devs: many senior devs will suggest you read some academic/difficult books on programming, such as TAOCP. You can be sure most of them read from 0% to 5% of the pages of those books, so don't feel down if you don't fully understand them and move on.

Exciting news: We are starting a large scale research project to develop a universal theory of resources and effects based on capabilities.

@gabro27 Congratulations Gabriele!

Some Scala news: I’m humbled to have been offered a seat on the newly formed SIP committee for Scala 3, alongside a group of amazing Scala experts 🎉

@alexelcu In the context of IO, always. It’s more explicit and always composable regardless of it being top-level or down in the flatMap chain.

@TeddyBeer82 Also `select` or `keep` but not filter, definitely.

Talking about naming things: IMO `filter` is, probably, one of the worst and most ambiguous name ever given to a method of a std lib.