{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Vernon Richard Show","title":"New QA Job? How We'd Decide Where To Start","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/d36edd5e\"></iframe>","width":"100%","height":180,"duration":3270,"description":"A listener asks which domino to push first, and the chaps immediately disagree about where to start.\n\nShady has been a QA engineer for about five years and has recently joined a new organisation. Like most of us walking into somewhere new, he can see more things worth improving than he could ever get to at once, and no obvious order to do them in. So which one goes first? Vernon goes straight for wherever the pain is greatest. Richard says do it the other way round entirely, and has a spreadsheet ready to prove it. Between the two of them sits the part nobody warns you about when you take the job: the thing you were hired to fix is very often not the problem, your credibility to say so out loud has a half-life, and the clock started the moment you walked in. Also, a man who finds water leaks for a living turns out to be running a testing process most of us could learn something from.\n\nChapters\n00:00 - Intro\n01:16 - Welcome: Energy levels and an idea for a future episode\n03:07 - A question from the audience\n03:51 - Shady’s question: Which QA domino do you push first?\n04:48 - One line answers FTW!\n06:04 - Rich maps the terrain\n08:24 - Vern does the not so obvious obvious thing\n10:12 - What’s the underlying problem?\n12:19 - How to choose between a quick win and a long-term play?\n13:55 - Instead of creating a master plan, do this instead.\n15:47 - Work like a… Drug dealer?!\n17:38 - Pickles\n19:44 - Because reasons\n21:05 - Rob Meaney thinks we have our priorities backwards\n24:01 - The colleague who argued against more test coverage, and won\n26:16 - Can you even prove the flaky automation is the problem?\n28:54 - GitHub's availability has never been worse. Rich has a theory why\n29:54 - Is Shady looking at a testing problem or a quality problem?\n31:12 - What happens when you tell them their problem isn't the problem\n32:50 - Education over illusion, and why \"you're wrong\" never lands\n36:18 - Does it matter that you can't name the technique you just used?\n37:24 - The page...","thumbnail_url":"https://img.transistorcdn.com/UFGkkh_jsZubLbpE6txGLPU3-7iIlh6gJ0JsseFDEm0/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9iM2Zk/NGQ3NDk4NmVkNjA5/OGJmMzA0ODQxMWIy/N2ExOS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}