In love with FP and type systems. Scala developer. Coauthor of Professional Scala - Wrox
Italy
Joined January 2013
- Tweets3.4K
- Following76
- Followers477
- Likes3.7K
Pinned Tweet
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.
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.
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/…
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/6321504… and it has readily been reported as a bug by som-snytt github.com/lampepfl/dotty/is…
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.
Bollocks! We Italians are great at queueing! (tongue in cheek)
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.
Alessandro Lacava retweeted
Exciting news: We are starting a large scale research project to develop a universal theory of resources and effects based on capabilities.
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.
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:
Every programming language provides ways to express our ideas and then translates them into reality. This thread will explore ten #Java programming features used frequently by developers in their day-to-day programming jobs.
Good news
Proposed to target JDK 19: JEP 425: Virtual Threads (Preview): openjdk.java.net/jeps/425 #jdk19 #openjdk #java
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.
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.
Added 0 after 18 and then halved it
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Alessandro Lacava retweeted
Il programma per #ScalaItaly2021 è ora completo! scala-italy.it Ci si vede Sabato 23 per una edizione "spaziale" con @DanielaSfregola @and_prf @AL333Z @lorenzoglorenzo @nivox @massimosiani ed altri!