Видео

I only develop apps as an Indie. I'm ruined as an employee for large businesses. Unemployable at this point. I like brewing my fussy coffee, coding in my pajamas at 2AM or 2PM or on a Sunday. To your point, "no right way", long as it ships =)

Excellent video, Thank you Elizabeth. Just subscribed!

"Unquestioned deference is as toxic to a partnership as disloyalty" Holy shit you put into clear terms something I've been thinking about but never really defined.

Great vid, love it - subscribed. Yet I feel one thing is missing at 10:15 ... Trust! Mutual trust, but especially top-down trust, that everyone is trying their best to achieve those four values.

Thanks for the upload! Great points and perspective, well explained. I'm curious about your thoughts on how a company should handle promotions, and allow leaders to emerge and rotate. Sorry for the bad english

"The four ingredients that are absolutely essential" 10:14 1. "Culture that values and rewards collaboration, experimentation, and learning" - a.k.a. People should be encouraged to follow general heuristics that correlate with better individual rationality. 2. "Clear definition of what good looks like, or what's important for the context" - a.k.a. a well-defined reward function to be used by individuals to judge whether they are doing well or not (or whether others are doing well or not) 3. "Some way of giving everyone visibility into the current reality so that they can see the delta between the status quo and the ideal" - Figure out how to improve people's rationality of the project and the goal so they have a better model of the whole process to make improvements with 4. "Making time for teams to reflect and adapt... that is, hold restrospectives." - Provide opportunities for synchronization between different people's models of the process, the reward function (goal) specification, and rational consideration of what could be improved for the future. "Everything else is an implementation detail" Tbh, I think most of the principles above could also be implementation details, or at least they are derived principles. In my mind the most important thing is "being rational", and by that I mean you should embody just two principles: *Epistemic rationality*: systemically refining your internal model of the world around you to better predict it, a.k.a. "being accurate" *Instrumental rationality*: Using that model to achieve your values by figuring out what action to perform at any given moment that would maximize your prediction for your value(s) to be achieved (whatever those values may be). Everything else is a heuristic (a practice / thought pattern that is useful in a large number of cases)

Elizabeth, have you ever worked with foreigners? Hugs from Brazil.

All my pain in the first minute of this video! Thank you, Elisabeth!

Excellent example, thanks for sharing.

Elizabeth, thanks so much for creating and posting. I gotta say, "be kind" saved me this week. On Monday, I was fuming about a thing a person had done, then told myself to be kind, followed my advice, and turned the situation around so that it was the high point of my week.

That was excellent, a touching impactful, valuable lesson, Thank you Elisabeth!

Awesome examples, and what a story! Brava! And exactly on point for what a good leader must do and how they should behave.

Thank you Elisabeth, hugs from Brazil. Muito obrigado.

Love this so much!

Very nice! Your callout that "Working with fresh information is always better and more efficient" is absolutely golden. There's a masterclass contained in that one sentence. Also, the dog, cats, and expressions in the animation are wonderful. So real, and super charming.

Thanks for sharing this video with us Elisabeth - it makes the dangers of ill-considered schedules very clear. But the other thing that it makes very clear, and something that I like to adhere to, and provide slack time for during iterations in order to accommodate my view - bugs take priority over new features... always. They have too, otherwise as you have noted in your video, the code-base can, and does, become unstable as time goes by, and the cost of fixing issues increases exponentially the longer fixing is delayed, as you also noted. Great video, thanks once again. 👍🙂

Great visualization!

This presentation was awesome! Thanks for sharing 😀 I have been watching it before my internship starts next week. Great video that takes up key points of Exploratory testing

Dear Élisabeth, your présentation reminds me of the book from Eliahu Goldratt on Critical Chain. Good présentation, thank you

I'm glad I got recommended this. I wasn't aware you even had a channel, saw your name and remembered that you were one of the OG's along with Bach and Bolton.

So great! It stopped just short of the scenario I thought it was headed for: The T-shaped folks, by virtue of sometimes working on stuff they know less about, slowly accrete more expertise in those weak areas over time. In other words the simulation doesn't account for learning and skills transfer. Once that's in place then I'd like to see a simulation of what happens when you keep changing the makeup of the team and losing people who have special knowledge specific to that team/product.

great simulation, also great to speak from both sides of the debate

Hey Elisabeth! Excellent video. You captured my attention and held it throughout. I've never considered building simulations with software to investigate outcomes under different contexts. Very cool! I particularly love the conclusion/definition of a team at the end <3

This is great Elisabeth, I think the point is well shown. The one thing I don't see is the complexity of development level as well. Juniors vs Seniors and all the mentoring that can happen. I completely agree with the Generalists approach but mentoring and teaching need to be incorporated as well and have no idea how this would be incorporated.

What a great video and explanation! Good job! ❤

Very interesting simulation and visualisation, Liz. Thank you for sharing this. I was wondering what happens if bugs show up during the release/iteration? How would it impact the teams? The reason I want to focus on bugs as compared to new work, is generally with bugs, you might want the same developer to pick up the bug who worked on the feature that introduced the bug.

This is fantastic. Great way to visualize teams.

Hi Elisabeth, I don't know if you remember me from Julio de Lima's mentorship to students from Brazil in the end of last year, I asked you about your favorites heuristics 😃

how can I give two thumbs up - one for the book and one for this video!! Thank you!

Thank you for lecture

Thank you, this is great!

This is a great presentation - not only can you learn a lot about exploratory testing but also how to present useful content!

This video is a perfect resource for helping folks understand the difference and importance of Explore vs Check as a mindset. Lately it seems I keep hearing about "breaking code" is what testers do... Sigh.... I am definitely sharing this! Thanks for bringing this view to our profession.

Thanks for the video 🙏. On my next video coming tomorrow I recommend your book as well. It’s one of the best books on the market

Awesome video! Thanks!

Elizabeth, thank you very much! Before your video I didn't realize how your book (approach, explanation) is important for my current work of a digital product & business building. The Book I already aquired some time ago, now its definitely falling from the shelf to my hands 😃 Hope to see more of your videos!

I've been in testing for almost 15 years now, and Elisabeth you have been a constant in my career! I'm so grateful for this resource! Not just for newbies but for me too!

Wow Awesome Test Design techniques explained. Those practical examples of bugs were really good to explain the importance of exploration. In modern software and the days to come, exploration would be the best way to find bugs. As checking would mostly be automated. Please do make more videos :) specially on test design techniques

Thank you for sharing it ! Looking forward for more content from you :)

This just made my day. Learned so much. Hope this reaches to everyone.

Totally forgot that you wanted to record that video, what a nice surprise in the new year! Love it!

I love the book and always recommend it to those joining the testing trade. Thank you for this intro / recap.

I have learned a lot from your book. Please keep sharing these videos

Thanks for sharing. Really helpful.

Shared this with my organization, thank you for posting it! Very helpful with a great combination of theory and practical examples.

I really can't believe I am the 8th follower of a legend in Software Testing. 😊Your contribution to software testing is invaluable. Thank you for sharing this wonderful video.