This looked a lot easier when I wasn't looking.
— The Director (@QAHatesYou) June 28, 2016
"Some people, when confronted with a problem, think "I know, I'll use regular expressions."
Now they have two problems." – Jamie Zawinski
— Programming Wisdom (@CodeWisdom) June 28, 2016
In sports you don't get what you wish for, you get what you work for.
— Sports Quotes (@Sports_Greats) June 22, 2016
You do big things by doing lots of little things.
— Daily Zen (@dailyzen) June 21, 2016
Hackers don't break software, they simply demonstrate that it was already broken.
— Holly-Grace.jpg.exe (@HollyGraceful) June 19, 2016
You know, I wish I thought of all the scenarios that find bugs first and then all the ones that do not later, too.
— The Director (@QAHatesYou) June 15, 2016
— Alan Richardson (@eviltester) June 13, 2016
”There is no such thing as a failed experiment, only experiments with unexpected outcomes.“ ~ R. Buckminster Fuller
— Bob Marshall (@flowchainsensei) June 2, 2016
Used this in a conversation on automation. About what you should automate and what you shouldn't … pic.twitter.com/kLf8cMz9zZ
— Mike Talks (@TestSheepNZ) May 30, 2016
[User requests feature already in product]
Junior dev: "lol dumb user"
Staff dev: "Closed – fixed"
Senior dev: <opens usability bug>
— Vicky Harp (@vickyharp) May 27, 2016
Chaos monkey for backlogs: remove things randomly, and if no one notices, problem solved!
— Chris Ford (@ctford) May 27, 2016
The one habit I've seen sabotage more people than any other is the habit of making assumptions instead of asking questions.
— Alex Hillman (@alexhillman) May 21, 2016
Things are mostly fine pic.twitter.com/hVzuMRiIfx
— The Practical Dev (@ThePracticalDev) May 21, 2016
— Ioana Serban (@ioanasaysgo) May 19, 2016
Flaky tests train you to ignore failing tests THEREFORE it’s better to delete them if you’re not going to fix
— Jason Yip (@jchyip) May 13, 2016
— James Thomas (@qahiccupps) May 11, 2016
So what Marvel character best represents testing and/or QA? #importantquestions
— Kate Falanga (@Squidish_QA) May 9, 2016
Picard management tip: Have an opinion on one side of an issue. Stay out of the neutral zone.
— Picard Tips (@PicardTips) May 5, 2016
"If at first you don’t succeed, call it version 1.0." – Unknown
— Programming Wisdom (@CodeWisdom) May 3, 2016
Two week sprints that are really accelerated waterfall cycles are cute. And by cute, I mean #&%#^!!
— The Director (@QAHatesYou) May 2, 2016
Exercise idea: To understand how it feels to switch in and out of building mindset, try solving two different logic puzzles simultaneously.
— James Marcus Bach (@jamesmarcusbach) April 23, 2016
"Let's schedule a meeting to talk about code quality" "Great!"
"Let's schedule an hour to work on code quality" "We don't have time"
— Llewellyn Falco (@LlewellynFalco) April 14, 2016
Some people have pictures of their children on their phone. I have screenshots of defects.
— The Director (@QAHatesYou) April 11, 2016
If it ain't broke, break it.
— Bob Marshall (@flowchainsensei) April 11, 2016
Many Agile projects are now, steadily and iteratively, producing crap code.
— Kevin O'Shaughnessy (@OshaughnessyKev) April 8, 2016
Picard management tip: Know your audience. Display strength to Klingons, logic to Vulcans, and opportunity to Ferengi.
— Picard Tips (@PicardTips) April 8, 2016
As an author of the Agile Manifesto
I want that stupid story format to go away
So that people can get to the essence of user stories.
— Ron Jeffries (@RonJeffries) April 7, 2016