Skip to content
HomeVideosBooks
AllTopicsTrends
BlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K
    Cover of Crystal clear

    Crystal clear

    Alistair Cockburn · 2004

    Software EngineeringProgramming
    Open LibraryAmazon
    Stats for nerds
    1recommend
    3mentions
    3people
    2011–2022years
    33% recommend67% neutral

    Mentions per year

    2011201320152017201920212022

    What Hacker News says

    1. chopsueyarFeb 2011
      Alistair Cockburn wrote an awesome book for small teams based on the "Crystal Clear Method". It has some great info.

      http://www.amazon.com/exec/obidos/ASIN/0201699478/ref=ase_al...

      thread
    2. davidthewatsonNov 2022
      Eating print on camera certainly qualifies you as being on-par with Werner Herzog who ate his shoe on camera.

      The problem with classifying the need for lightweight methods as an "agile" problem is that agile has become the dogma that it set out to replace twenty years ago. Let that sink in. The word agile divides the room and that's part of the problem with cliched corporate speak.

      As a result, there is no more confusing argument in software process today than agile because we do not have consensus on its meaning. At best, defining agile is a choice paradox. This is a result of the spectrum from little a agile (actual agility) to Big A Agile (fake corporate agile) where the pointy haired boss tells you to select from a cargo cult of overly complex choices, all of which are bad. My experience has been that teams that wind up at real agile wind up there because they weren't worried about defining a cornucopia of cliched agile speak prior to moving forward and instead did a lean build-measure-learn cycle and just figured it out as a series of continuous improvement iterations whereas fake agile stems from trying to do what some other unicorn says works for them, failing, and never getting it right because there is no cycle of action learning and reflection. tldr; it doesn't actually matter what words you use to describe the gyrations, what matters is that the gyrations work for you and your team and produce the results the team desires.

      FWIW, most of what I've said is supported in the research and publishing of Alistair Cockburn who was there when it all began twenty years ago and wrote Crystal Clear. The other academic I'd reference who has the done the work and arrives at what I believe are the correct conclusions is Allen Holub.

      thread
    3. amigoingtodieOct 2017
      What about Alex Cockburn's Crystal Clear Methodology?
      thread

    Related

    Cover of Clean Code
    2008–2026

    Clean Code

    Robert C. Martin
    298 recommend · 951
    Cover of Code Complete
    2007–2026

    Code Complete

    Steve McConnell
    393 recommend · 894
    Cover of Programming Pearls
    2007–2026

    Programming Pearls

    Jon Bentley
    158 recommend · 315
    Cover of Designing Data-Intensive Applications
    2014–2026

    Designing Data-Intensive Applications

    Martin Kleppmann
    457 recommend · 846
    Cover of The clean coder
    2010–2025

    The clean coder

    Robert C. Martin
    53 recommend · 95
    Cover of Code
    2008–2026

    Code

    Charles Petzold
    243 recommend · 385
    Cover of The Elements of Computing Systems
    2008–2026

    The Elements of Computing Systems

    Noam Nisan
    204 recommend · 344
    The Book of Shaders
    2015–2026

    The Book of Shaders

    39 recommend · 59