Pinned Tweet
If you've worked on a team who struggled with lots of bugs and maintainability issues, I have a book for you! 📖
You will learn how to use functional programming techniques to create bulletproof and readable codebases. ✨
➡️ Check it out: manning.com/books/grokking-f… @ManningBooks
Michał Płachta retweeted
Not sure why this book isn't more standard when people are asking how to learn FP. Even though it's examples are in Scala (no offense @miciek) lol. I've been adapting them all to Haskell.
Michał Płachta retweeted
📣Deal of the Day📣
SAVE 45% on Grokking Functional Programming & selected titles: mng.bz/WrEx @miciek
This friendly, lively, and engaging guide lays out the principles of #functionalprogramming simply & concisely & will help you understand what #FP is all about.
Michał Płachta retweeted
🎶 It's the final countdown 🎶
github.com/scalalandio/chimn…
Dear @scalarconf! Check out @siriusxmlife 's contest where you can win "Grokking Functional Programming" (or a Lego set 😅).
Michał Płachta retweeted
Most people using #Scala are happily and quietly shipping code, instead of looking left and right whether Scala is increasing/decreasing in popularity.
If this quiet person is you, we need to hear more from you!
Michał Płachta retweeted
See you at the Kraków Scala User group meetup in a week (29.02.2024)! We will discuss practical apps with Typelevel stack and serverless Scala Native.
meetup.com/krakow-scala-user…
Michał Płachta retweeted
わいわい。日本語版ポチった / “Grokking Functional Programming - たけぞう瀕死ブログ” htn.to/2fsnfPXoZj
Dear @oredev! Thanks for joining my session. I enjoyed all the great discussions about functional goodies that solve real-world problems. You can find the slides and more info here: speakerdeck.com/miciek/immut… #Oredev2023
Working with different functional types causes a déjà vu, but in a good way.
- Option has toRight ↔️ Either has toOption
- Option has toList ↔️ List has headOption
- Option has toValid ↔️ Validated has toOption
Discovering these connections will help you write maintainable code
249
If you want to learn functional software architecture, don’t start with LEGO blocks, railways, or burritos. 🌯
Start with immutability. Ask yourself: can this feature be done exclusively using immutable values?
Michał Płachta retweeted
Now available for ACM members: "Grokking Functional Programming," by @miciek. This book starts w/the familiar ideas of OOP & introduces FP to imperative developers step-by-step using relevant examples, engaging exercises, & lots of illustrations. bit.ly/43Xvnzp
Michał Płachta retweeted
You can still become a productive functional programmer by reading "Grokking Functional Programming"!
I am honored the book has been featured on the @ManningBooks bestseller list. 🏅
🎁If you are thinking about holiday gifts, the book is 50% off today! manning.com/books/grokking-f…
Michał Płachta retweeted
Here's a myth new programmers believe in:
❌ A typical programmer's career consists mainly of writing code. ❌
The facts are different: we spend most of our time reading and maintaining someone else's code.
Being able to read and understand code quickly is your superpower! 💪
Michał Płachta retweeted
Why teach Scala? (Or: Why teach with Scala?) This page explains it really well, with a number of insightful comments by experienced faculty:
scala-lang.org/teach.html
If you also teach Scala, add your name here:
github.com/scala/scala-lang/…
Michał Płachta retweeted
try the new Scala homepage!
🧐 Did you notice our new home page? @bishabosha just finished overhauling it 🤩
🎺 And by the way, all our scala-lang.org websites should now be reachable from VPNs! 🛜
Read more in our blog article 👇
scala-lang.org/blog/2023/07/…
Michał Płachta retweeted
Ever called a function that didn't quite behave as expected? 😨⚠️
Worse, perhaps you've built a whole functionality around a misleading function that promised one thing and delivered another 💥
In FP, you construct functions with signatures that rarely, if ever, deceive!
Michał Płachta retweeted
Don't leak your `db` domain into your `core` domain
Separate them, and your code will be more robust and easier/safer to evolve
You'll not have to deal with `db` domain issues in your `core` domain, everything being isolated in your `db` domain
I advise you to have 2 sbt modules:
- `core`
- `db`
`db` depending on `core`
So that the separation is clear and is harder to break
The SQL world doesn't match our Scala ADT world, we need denormalization.
That's one of the purposess of this `db` domain. That's not a concern of your `core` domain
The `db` domain should not leak into your `core` domain
Michał Płachta retweeted
🏷️Deal of the Day🛒
Why bother with functional programming?
How about powerful & reliable programs?
@miciek will teach you the principles & advantages of #FP in a simple way: mng.bz/RvO0

























