I spent the whole evening doing paper work and I don’t even feel bad. #adulting ✊

Replying to @schmichael

Well this sounds like a delightful place to work.

The CEO of @RevolutApp on Slack: “Why aren’t you working on weekends?”

🚮 pic.twitter.com/skGU8VZWF9

— Phillip Caudell (@phillipcaudell) February 28, 2019


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.


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.

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.

— Benedikt Meurer (@bmeurer) February 25, 2019