
ManningBooks
Grokking Simplicity (Manning)
Eric Normand
As you write software you should distinguish between code that alters your system’s state, and code that does not. Once you learn to make that distinction, you can refactor much of your state-altering “actions” into stateless “calculations.” Your software will be simpler.
The book also teaches you to solve the complex timing bugs that inevitably creep into asynchronous and multithreaded code. In advanced sections of the book you learn how composable abstractions help avoid repeating code and open up new levels of expressivity.
- Full details: Grokking Simplicity
Don’t forget you can get 35% off with your Devtalk discount! Just use the coupon code “devtalk.com” at checkout
Most Liked

mafinar
Sounds like a very difficult book to write

Ted
Eric currently offers a discount code for 50% off; it’s right at the top of PurelyFunctional.tv, his Clojure training site.

davearonson
After seeing the subtitle, it made a lot of sense. Almost every time I try to apply a functional approach, instead of keeping state in some kind of object, it seems so much simpler to code – and to test.
Popular Backend topics










Other popular topics










Latest in Learning Resources
Latest (all)
Categories:
Sub Categories:
Popular Portals
- /elixir
- /rust
- /wasm
- /ruby
- /erlang
- /phoenix
- /keyboards
- /rails
- /js
- /python
- /security
- /go
- /swift
- /vim
- /clojure
- /java
- /haskell
- /emacs
- /svelte
- /onivim
- /typescript
- /crystal
- /c-plus-plus
- /tailwind
- /kotlin
- /gleam
- /react
- /flutter
- /elm
- /ocaml
- /vscode
- /opensuse
- /ash
- /centos
- /php
- /deepseek
- /scala
- /zig
- /html
- /debian
- /nixos
- /lisp
- /agda
- /textmate
- /sublime-text
- /react-native
- /kubuntu
- /arch-linux
- /ubuntu
- /revery
- /manjaro
- /django
- /spring
- /diversity
- /nodejs
- /lua
- /c
- /slackware
- /julia
- /neovim