Any asshole can build an org where the smartest, most experienced engineers in the world can get shit done.

A truly great engineering org is one where normal, workaday software engineers, with decent skills and ordinary experience, can move fast, ship code, and move the business forward day by day.

On ideas that drive testing, shapes of context is quite a powerful one. This weeks shapes for me are:
1. Remote testing, local ownership.
2. Platform testing. Testing pyramid would be irrelevant.
3. Build and document with automation. Close collaboration in teams owning quality.

Another idea that drives how I now frame testing is scaling. It came along with being able to run thousands of tests a day, sourced from tens of teams in internal open source style. People can't hold the knowledge. People can complete circles but holding it, we need a system to do that for us.

Earlier this week, I was reminded of thinking of test strategy 10 years ago, with an experience report at a peer conference. Then I coined four ideas:
Knowing product. Delivering professionally. Actionable information first. Releasing in production when done.
The last included building capability.

While I would frame the ideas driving test automation with capturing things into pipelines, I also would frame it with the idea that *anything else in testing could happen while working towards automation*.

Ideas of new capabilities are driven by changes in the world. Accessibility this year, driven by the changes in EU legislation, as well as Finnish interpretations of already existing legislation. AI and the need to intertwine it. OSS composition analysis and risks in ownership.

Another idea that drives testing is that *professional testers as proxy for real users are poor substitute*. This increases the aspects of "social" in testing. You must meet real users. You must facilitate conversations for whole teams for real users. And you must go to logs with data of real users.

Essentially, with the parts that focus on testing of applications, our ideas that drive testing are founded on the idea that work needs to continue when we are no longer around. Organizational resiliency requires all of us to care to leave things behind. This is why we *capture things in pipelines.*

We may say "shift left" and "shift right", but in fact we are in the process of completing a circle, but with a social transformation: *testing is too important to be left just for testers, but also too important to be left without testers*.

The first idea that drives testing is *testing is bigger than testing of apps*. You know, the fact that I am a tester yet I test ideas, organizations and sometimes people's patience. A common way of describing this is to point at every stage of DevOps cycle and say "you test here".