yak butter recipe

When your IDE trial runs out don't buy the license. It will timeout after 30 minutes. Built in Pomodoro timer! Not so great for pairing remotely maybe.

Interfaces facilitate visibility. Software is the only engineering practice that doesn't allow runtime visibility to end-user. If this were true for construction, it would mean your builder would have to live with you for you to even guess what the problem is. https://vimeo.com/221049715 https://github.com/stripe/veneur

Read more at:  https://www.cardratings.com/creditcardblog/whats-the-point-of-having-a-credit-card.html Copyright © CardRatings.com 1. Earn credit card rewards and perks Every month, seems like a joke this is just a way for marketers to get ahold of you Don't need rewards for tracking my behavior. Need living wage and fair prices.  2. Avoid wiping out your bank account if an emergency happens Life is an emergency Should we charge RHApr when someone is in need? Vulture lately? 3. Minimize risk and reduce payment hassles  Debit cards or other e-payment do this without exorbitant fees like RHApr 4. Make budgeting easier  No No one writes checks anymore Debit cards and other forms of e-payment solve most of these 5. Build credit why? So you can have more credit. Circular. Stupid. Read more at:  https://www.cardratings.com/creditcardblog/whats-the-point-of-having-a-credit-card.html Copyright © CardRatings.com

https://kafka.apache.org/intro#kafka_mq and more generally https://kafka.apache.org/intro

Why functional over OO? https://medium.com/@cscalfani/goodbye-object-oriented-programming-a59cda4c0e53 Inheritance Banana Monkey Jungle The diamond relationship Fragile parent class Categorical (Taxonomy) v.  Containment (or Exclusive Ownership) Hierarchies Encapsulation Object passed by reference to an Object Constructor is not safe Deep cloning MC Hammer v.   Immutability Global Scope Polymorphism https://www.cs.utexas.edu/~mitra/csSummer2013/cs312/lectures/interfaces.html Design by Behavior not Data

functional decomposition or domain-driven design well-defined interfaces  explicitly published interface  single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services

There’s a lot of talk about transformation and some metrics around what we are lacking and need to do better. Do we also know what we do well and the good things about our work processes and environment that we want to keep? I’m concerned that if we don’t diagram this as a spectrum we risk running over those good things that we do in the course of transforming. Running agile retrospectives at team levels could provide us with this feedback DAKI – drop, add, keep, improve | Fun Retrospectives www.funretrospectives.com/daki-drop-add-keep-improve/ 1.         2.         DAKI is a great data gathering to foster the thinking around practices and the value the team get from it. It helps team members to understand each other ... KALM – Keep, Add, More, Less | Fun Retrospectives www.funretrospectives.com/kalm-keep-add-more-less/ 1.         2.       ...