Il programma per #ScalaItaly2021 è ora completo! scala-italy.it Ci si vede Sabato 23 per una edizione "spaziale" con Daniela Sfregola Andrea @AL333Z lolgab Andrea Zito @[email protected] Massimo Siani [email protected] ed altri!

Added 0 after 18 and then halved it

When you write the docs for the Scala library you created, may I humbly suggest you include type annotations in the examples? That would make "following the types" much easier.

In the future IDEs might even think and write code themselves, but I'm pretty confident that, nevertheless, they won't get matching parenthesis/brackets/quotes/... right.

Good news

Proviamoci: vendo due biglietti per Brunori Sas a Firenze il 24/5 (un rt → un aneddoto da aperitivo)

As a former Java dev I appreciate the effort its community is making to improve it. Nonetheless this thread reminds me how lucky I am to use Scala and have that and much more with a less verbose syntax. E.g. see the CompletableFuture example? Here is the return part in Scala:

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.

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

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.

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

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

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

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.

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.

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

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…

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. developer.mozilla.org/en-US/docs/Web…

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.

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