💯❗️
The more programming tools you use, and the more indirection you add to the system, the more difficult it gets to maintain. Then you look for more tools to manage the complexity, and add more indirection to try to manage it, and you end up with runaway inflammation.
— Gary Bernhardt (@garybernhardt) February 27, 2019
Even after using vim for 4 years this happens more often than I care to admit. 
A llama named Caesar the No Drama Llama boarded a tram in Portland with his handler Larry McCool to go to Wizard Con. This appears to be a factual statement.
This exiting vim joke goes to 11: https://twitter.com/marionpdaly/status/1100067792550735874?s=21
Say hi to the newest QA engineer at @YoungCapital_NL@twitter.com. 💁♀️ 
This has definitely been my experience. I think DRY is a useful tool but taken to an extreme makes things worse. Definitely use DRY to clean up repeated values into constants. But complex abstractions tend to be wrong the first time.
Wrong abstractions hurt code readability and maintainability a lot more than some duplicated code.
— Benedikt Meurer (@bmeurer) February 25, 2019
This is especially true for test code. Having lots of helpers in there whose behavior is controlled by a zoo if parameters is a clear warning sign. It'll be hard to change later.
I think I need to get a plant so I can name it.
I woke up and named all of my plants. How is your day going?
— Tina Roth Eisenberg (@swissmiss) February 24, 2019
Wife reading an animal picture book to the 1 y/o.
Wife: Tiger. Roar!
1 y/o: ...
Wife: Fish. Glug glug, glug glug.
1 y/o: ...
Wife: Giraffe... 🤔 I’m a giraffe!!
1 y/o: 🤨
@hamiltonmath@twitter.com Almost like the kind of place you’d like to visit some time right? 😜
Always Be Shipping 🚢
http://www.mobilespoon.net/2019/01/product-shipping-why-i-love-shipping-so.html
