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: 🤨
@email@example.com Almost like the kind of place you’d like to visit some time right? 😜
Always Be Shipping 🚢
This is why Shipping is so important to me
How to build a culture of frequent product releases? What is the difference between Agile and Shipping? What are the benefits for the product, the team, and the whole company? And what impact do product managers have on the company's shipping culture?www.mobilespoon.net
Pretty dang gorgeous day in Leiden. 😎
@firstname.lastname@example.org But imagine if the only term was 'Full-stack'? That's kind of what we're facing in front-end.
@email@example.com Ah ha! I was missing the prefix! 🤔 And no worries. We're all busy people. When I get some time I'll at least try to write up some documentation from what I've learned. :)