10 Matching Annotations
  1. Jan 2023
    1. I've seen a bunch of people sharing this and repeating the conclusion: that the success is because the CEO loves books t/f you need passionate leaders and... while I think that's true, I don't think that's the conclusion to draw here. The winning strategy wasn't love, it was delegation and local, on the ground, knowledge.

      This win comes from a leader who acknowledges people in the stores know their communities and can see and react faster to sales trends in store... <br /> —Aram Zucker-Scharff (@Chronotope@indieweb.social) https://indieweb.social/@Chronotope/109597430733908319 Dec 29, 2022, 06:27 · Mastodon for Android

      Also heavily at play here in their decentralization of control is regression toward the mean (Galton, 1886) by spreading out buying decisions over a more diverse group which is more likely to reflect the buying population than one or two corporate buyers whose individual bad decisions can destroy a company.

      How is one to balance these sorts of decisions at the center of a company? What role do examples of tastemakers and creatives have in spaces like fashion for this? How about the control exerted by Steve Jobs at Apple in shaping the purchasing decisions of the users vis-a-vis auteur theory? (Or more broadly, how does one retain the idea of a central vision or voice with the creative or business inputs of dozens, hundreds, or thousands of others?)

      How can you balance the regression to the mean with potentially cutting edge internal ideas which may give the company a more competitive edge versus the mean?

  2. Jun 2021
  3. Mar 2021
    1. Why separate out red tests from green tests? Because my green tests serve a fundamentally different purpose. They are there to act as a living specification, validating that the behaviors work as expected. Regardless of whether they are implemented in a unit testing framework or an acceptance testing framework, they are in essence acceptance tests because they’re based upon validating behaviors or acceptance criteria rather than implementation details.
    1. Sometimes a change impact analysis is performed to determine an appropriate subset of tests

      Hey, I do that sometimes so I can run a smaller/faster subset of tests. Didn't know it had a fancy name though.

    2. non-regression testing

      That would probably be a better name because you're actually testing/verifying that there hasn't been any regression.

      You're testing for the absence of regression. But I guess testing for one also tests for the other, so it probably doesn't matter. (If something is not true you know it is false, etc.)

    3. Regression testing (rarely non-regression testing[1]) is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change.[2] If not, that would be called a regression.
  4. Sep 2020
  5. Aug 2020
  6. May 2020
  7. Nov 2015