“First Attempt In Learning”
summary
A tester reframes failure as First Attempt In Learning, studies cognition and metacognition, and moves from terrified test-case writer to curious engineer by deliberately writing bad tests, learning one programming concept a day, and building an automation framework from scratch that measurably improved team processes. Strategy includes write one line a day, pair with peers, and seek a mentor who believes in you; outcome: reduced fear, faster skill growth, practical artifacts that worked.
AI-written summary · about
related talks
22mChoosing Failure
01h 03mRewiring your brain with test driven thinking in C++
05mFostering Personal Growth Through Failure and Experimentation
42mTester’s Mindset: Rethinking Software Testing Through Mentorship
15mThe Tester I Was and the Tester I Could Be
21mEmbracing Failure
40mFailure for Fun and Profit!
25mThe Pursuit of Failure