Aleš Roubíček

“Change is not necessarily slow. A team eager or desperate for improvement can progress quickly. It doesn't need to wait long to assimilate one change before moving on to the next practice. If you change too fast, though, you risk slipping back into old practices and values. When this happens, take time to regroup. Remind yourself of the values you want to hold. Review your practices and remind yourself why you chose them. New habits take time to solidify.”
― Kent Beck, Extreme Programming Explained: Embrace Change

“If I have the same logic in two places, I work with the design to understand how I can have only one copy. Designs without duplication tend to be easy to change.”
― Kent Beck, Extreme Programming Explained: Embrace Change

“That means that a go block compares very favorably to an Elxir process—a very impressive result given that Clojure runs on the JVM, whereas Elixir runs on the Erlang virtual machine, which was built with efficient concurrency in mind.”
― Anonymous

“As with threads and locks, actors provide no direct support for parallelism. Parallel solutions need to be built from concurrent building blocks, raising the specter of non-determinism. And because actors do not share state, and can only communicate through message passing, they are not a suitable choice if you need fine-grained parallelism.”
― Anonymous