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

“What data did you notice about the week, what stood out for you? What were your emotional reactions to the week? What made you happy? Where were you challenged? Where were you frustrated? What were your insights? What did you learn? What one or two things will you do based on this week?”
― 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

“In his book Tapworthy, author Josh Clark focused on three critical mobile behaviors: micro-tasking, “I’m local,” and “I’m bored.” These align pretty well with Google’s breakdown of mobile users into three behavioral groups: urgent now, repetitive now, and bored now.”
― Anonymous