1,417 Matching Annotations
  1. Nov 2016
  2. Oct 2016
  3. Apr 2016
    1. My friends here who started a micro-brewery tell stories that when they were starting, the other micro-breweries in the region did not seem them as a threat/competition, and in fact, offered advice, equipment, supplies. The people who do this stuff see it as a net gain for everyone if someone can help raise the regional interest in craft beer; if everyone grows more customers, everyone wins. It’s not a tech startup mentality.

      Craft beer is a fascinating world, partly because of this approach to sharing. Much of the so-called “Craft Beer Revolution” happened through homebrewers who were sharing tips and recipes online (not to mention ingredients and samples offline). The idea, in many an indie/craft scene, is that the out-group is the Mainstream. Very similar story among owners of Third Wave cafés. Of course, there are differences. But still… When you have a “common enemy” (Anheuser-Busch, Starbucks, McGraw-Hill…), it’s much easier to grow together.

  4. Feb 2016
    1. In my professional career I’ve noticed that doing “The Right Thing” is not always the best path. That phenomenon is called The Rise of “Worse is Better” and it can be observed in many things including C, Unix, Windows, JavaScript… Seems like New Jersey approach wins out more than it looses in a real world. (Be a virus, spread and than the pressure will rise to better the game).
  5. Jan 2016
  6. Dec 2015
  7. Nov 2015
  8. Sep 2015
  9. www.gutenberg.org www.gutenberg.org
    2
  10. Mar 2015
    1. an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

      an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.