home.social

Search

549 results for “maaretp”

  1. Today is my final board meeting for - I have served my two years. I set out to figure out what does it mean to be a "board professional", and I am grateful for now having a good understanding of board-level decision making, differences of tax statuses and coordinating group of companies with different tax statuses as one closely aligned entities.

    It has been a significant source of reflection of the challenges a board has compared to people in the org itself, and not easy.

  2. Today is my final board meeting for #Tivia - I have served my two years. I set out to figure out what does it mean to be a "board professional", and I am grateful for now having a good understanding of board-level decision making, differences of tax statuses and coordinating group of companies with different tax statuses as one closely aligned entities.

    It has been a significant source of reflection of the challenges a board has compared to people in the org itself, and not easy.

  3. In recording of the Test Case Scenario podcast, Marcus Merrell reminded me of this keynote I did in 2018 on showing exploratory testing with a demo of writing code without centering the code or automation. This was early stages of really digging into #ContemporaryExploratoryTesting. Still relevant even though I stopped repeating this talk and wrote some hundred of more framings since. youtube.com/watch?v=Es4SfYog5V

  4. In March 2022, I talked at #TSQA with an experience report on the silly things we do with writing test case documentation. Since then, some folks think generating this wasteful documentation with #GenAI would be better, and it is not.
    My slides from the talk: drive.google.com/file/d/1_AWSL

  5. In March 2022, I talked at #TSQA with an experience report on the silly things we do with writing test case documentation. Since then, some folks think generating this wasteful documentation with #GenAI would be better, and it is not.
    My slides from the talk: drive.google.com/file/d/1_AWSL

  6. In March 2022, I talked at #TSQA with an experience report on the silly things we do with writing test case documentation. Since then, some folks think generating this wasteful documentation with #GenAI would be better, and it is not.
    My slides from the talk: drive.google.com/file/d/1_AWSL

  7. In March 2022, I talked at with an experience report on the silly things we do with writing test case documentation. Since then, some folks think generating this wasteful documentation with would be better, and it is not.
    My slides from the talk: drive.google.com/file/d/1_AWSL

  8. In March 2022, I talked at #TSQA with an experience report on the silly things we do with writing test case documentation. Since then, some folks think generating this wasteful documentation with #GenAI would be better, and it is not.
    My slides from the talk: drive.google.com/file/d/1_AWSL

  9. I work with a tester who has before only written system test automation code in Python, based on tasks including detailed scenarios. I moved her to a project with TypeScript (new language), solid developer testing (new mode of operating automation) and refused to give her a task but said to explore a little and then contribute.

    It's like I have now the tester I always wanted. Great work, and great example of #ContemporaryExploratoryTesting.

  10. We worked with @rinkkasatiainen for 9 months to grow #TechExcellence in the team, from within. To remember the time, I used gource and my cringy video editing skills to create a keepsake. This is what we look like working on our codebase. Movement is work.

  11. I was told I have 'great energy' when repeating instructions in an open space conference. I have a career (on testing) built on the idea that I treat repetition as opportunity for change with exploratory testing, and I am just delighted I get four opportunities to either succeed or fail with opening the space in this #SOSC23 event

  12. Test management in this continuous style is the work we do ensuring that the sum of all things testing leads to the results it should. It seems like a product owner not knowing testing can water it down. It seems like a functional test case or ad hoc tester can water it down. So I call for #ContemporaryExploratoryTesting and a map of things different people can do.

  13. Everyone is testing in production. At least I’m looking at the results. -Abby Bangser #observability #HUSTEF

  14. You want to prioritize tools that allow asking new questions. - Abby Bangser #HUSTEF

  15. In a few hours, it's shift of cities, from Helsinki, Finland to Budapest, Hungary. True my just in time planning habits, I now know I will open #HUSTEF with my keynote on impact on Wednesday, and can meet up with my local team member tomorrow. Yes, one of my team's developers is in Budapest.

    Excited to see so many people I have gotten to know over the years, and that this is the last one as I have already said no to 18 requests after this.

  16. Participated #OpenSourceCollective #OSC community call today, and learned a bit about #JHipster tagging issues they pay to fix. Loved the open finances data crunch to show how over four years one developer made 30k, about 10 developers made 10k and many developers made some paid contributions.

    Solving money community style.

  17. I love how small the world is. I met on a call today a brilliant colleague in Brazil, for purposes of tuning her conference presentation she will deliver in Sweden. #TechVoices may be small when it’s powered by me mentoring but it would need others to volunteer on the wider matchmaking. And it begs for a software solution. Meanwhile I am enough.

  18. A tale of three testers but entirely different frames of reference. #ContemporaryExploratoryTesting and we knew coverage, found bugs and hit schedules. #DomainSpecialistTesting and we covered only requirements, insufficient testing, fuzzy communication on status. #ProgrammerTesting got road blocked to fixing, leaving coverage low and missing bugs.

  19. People still seem to think that for geographically distributed teams, meeting face to face is the key to success. I am of opinion that working together, like actually working together #PairProgramming, #EnsembleProgramming and sharing work as real team is much more key than traveling to meet people.

    The perceived distance is almost as much of a choice as the physical distance. Show up for people, every day.

  20. Back when I was not manager, my solution to #ISTQB (which is BAD) was that I taught my colleagues. I allowed them to take certs if they felt the letters would help them in life.

    Now I don't have time to teach all of my colleagues as much on #testing as I'd like. So I set the ball rolling. People get to take #BBST.

    I have taken four different modules and failed on two. They were *that hard*. But even when failing, I learned so much that I will take them still and they will improve me.

  21. Thinking out loud as usual. If I say we have been failing at finding a #ContemporaryExploratoryTesting profile, I don't by all means think we have talked to every possible candidate. But I find it fascinating how people would think the ones they employ and hold on would be so much better than the excellent people on free market we have not yet found.

    I believe there are a lot of good people. But also a lot of mismatch correctable by training.

  22. We have been unsuccessful at recruiting a tester for a team building embedded devices. We've looked for seniors. We've looked for promising juniors. But the leap of faith on believing their background knowledge would help them succeed has been quite extensive.

    So today I am dreaming of a whole team of newbie testers to train. If only I had the time and the budget.

    #ContemporaryExploratoryTesting - resultful testing - is hard to find.

  23. Looks like we had 85 summer trainees this summer. From what I experience, the number is limited by mentors, and it makes me kind of happy to have a steady annual influx of people getting their experiences with #Vaisala. There is a need of constant training positions, not only summertimes, and every company should pitch in to training next generations of professionals doing the work.

  24. It's funny to think in terms of retiring from public speaking, but that is sort of what I am doing. I have already said MANY no's where I used to say yes on doing a talk, and will only be delivering the two I committed before my resolution.

    #HUSTEF hustef.hu is something I still look forward to. I am again traveling with @Mii so I plan on learning++ with the conversational ping pong her brilliant mind brings.

  25. Modeling #ContemporaryExploratoryTesting, bits worth remembering.

    Meeting another company's managers reminded me that we model what and where is #ExploratoryTesting very differently. Instead of drawing the box of exploratory testing that includes all worthwhile parts of test case -based testing, I split this to timeline of activities.

  26. I've been identifying with the #ContextDrivenTesting crowd professionally for decades while stepping away from the pair of individuals who make appearances of it being their thing. Seeing CDT described as
    - non-automated
    - whole-product
    - exploratory-focused
    helps me see difference that lead me to #ContemporaryExploratoryTesting that is:
    - automating
    - all levels leading up to whole products
    - exploratory-focused centring agency and learning

  27. Story of adding programmatic quality gates to pushing to master in an organization that was used to spending most of their time on unfinished work. Pushing though change makes a fun story but also the ripple effects are scary here. 50 people leaving in a transformation. #DevTalks

  28. If #ModelBasedTesting is of interest, you may want to look at #AltWalker. It is one entry point to open source tools in this space. altom.gitlab.io/altwalker/altw

  29. If #ModelBasedTesting is of interest, you may want to look at #AltWalker. It is one entry point to open source tools in this space. altom.gitlab.io/altwalker/altw