I usually say something like "Conflict is a sign that people care about things. If nobody cared, there would be no conflict. Caring is good, so it is better to have conflict, then to have apathy." Unsure if this is the exact same pitch or you mean something else.

* Better test accounts (Read 'working' for 'better')
* Buggy data relationship removed
* Constants updated
* Goat Sacrificed on the Altar of the Sales Driven Roadmap
* Tickets for week old bugs
* Updated on-call hand off document

I have (and love) the top left bedspread, got mine at three80atlantic in Brooklyn, where they stock 11.11 and other brands with an interest in indigo & texture like INDI+ASH.

Did you look at hackathons and creative coding sessions with time limits as possible material? Did a Creative Coding at Recurse recently, where my goal was to write a bunch of test cases understanding Things Programmers Get Wrong About Time. It was educational in terms of speed VS understanding.

...and when my team meets my lower expectations instead, well, that's why we continue to have these contrasting views.

Someone who only talked about how we should push for the ideal situation would lose my confidence quickly. Someone meeting with the other stakeholders the same day to tell them they need to go further than I asked? That's a confidence boost and a lesson for me and a benefit to the whole team.

The other person doing formal methods at Recurse found it without me pointing it out, and used it as far as I know.

Very beautifully translated. Have a diagram in honor of my failed attempts. Tomorrow, I'm finishing the Core section of the book and then I'm going to try to Do Something.

Sorry, it's the future lock, not the past lock. And also something something conveying the brackets. Not simple!

TLA+ redefining my mental definition of 'fluency' in programming languages over here as I take three+ layers of mental translation to get anywhere.