16 Matching Annotations
  1. Last 7 days
    1. Mark: Yeah. And I actually think the Agile revolution in software development is software development catching up to the fact that it’s a writer-ly art. Writers don’t know where they’re going or how they’re going to express it when they start out. Neither, it turns out, does software developers. They can pretend by writing it the first time in a spec language and then coding it and then, checking the specification, then finding out that they’ve written the wrong thing and writing a new specification. That was when I was getting started, the right way to write software.

      Agile software development is akin to the design of the writing process.

  2. May 2022
    1. Any software developer will recognize it, The Eureka Moment. This is when you suddenly see how to solve a particular problem. We have them in all shapes and sizes and at the strangest moments. How does that work in SCRUM and DevOps teams?

      The Eureka Moment in Agile Teams

      Any software developer will recognize it, The Eureka Moment. This is when you suddenly see how to solve a particular problem. We have them in all shapes and sizes and at the strangest moments. How does that work in SCRUM and DevOps teams?

  3. Mar 2022
    1. agile development that has rapidly spread from manufacturers in Japan to startups in Silicon Valley. It's a system of group dynamics in which workers are organized into small teams, hold daily progress sessions and weekly reviews

      +1

  4. Feb 2022
    1. Google killed SG&E about one year after Stadia launched, before the studio had released a game or done any public work. In a blog post announcing Stadia's pivot to a "platform technology," Stadia VP Phil Harrison explained the decision to shutter SG&E, saying, "Creating best-in-class games from the ground up takes many years and significant investment, and the cost is going up exponentially."

      I suspect Google wanted faster, more measurable results than is possible with game development. There's a reason why tech companies are vastly more profitable than game companies.

      I don't particularly see the shame in changing a strategy that isn't working. As an early user of Stadia I do see the lost potential though, maybe that's where this is coming from.

  5. May 2021
    1. Agile as a methodology is designed to be adaptive to multiple conditions and drivers to enhance the speed of delivery, but it is most successful when the organisation adopting it understands its own in-built cadence, i.e. its specific rhythm of project delivery.
  6. Mar 2021
    1. The number one problem that I see developers have when practicing test-first development that impedes them from refactoring their code is that they over-specify behavior in their tests. This leads developers to write more tests than are needed, which can become a burden when refactoring code.
  7. Feb 2021
    1. Programming to interfaces is at the core of flexible structure.
    2. Rather than implement features you might need, you implement only the features you definitely need, but in a way that accommodates change. If you don't have this flexibility, parallel development simply isn't possible.
    3. At the core of parallel development, however, is the notion of flexibility. You have to write your code in such a way that you can incorporate newly discovered requirements into the existing code as painlessly as possible.
    4. many successful projects have proven that you can develop high-quality code more rapidly (and cost effectively) this way than with the traditional pipelined approach
  8. Nov 2019
  9. Sep 2019
    1. The Agile Software Development Process – How We Do It

      To get your tech startup going you have to deal with a lot of challenges, and come through it unscathed. Otherwise, the failure to deal with those challenges may directly lead to mistakes and problems during the actual software development process- hampering your chances of scaling your development process.

  10. May 2017
    1. Every time a customer service assistant shrugs and says “computer says no” or an organization acts in crazy, inflexible ways, odds-are there’s a database underneath which has a limited, rigid view of reality and it’s simply too expensive to fix the software to make the organization more intelligent. We live in these boxes, as pervasive as oxygen, and as inflexible as punched cards.

      Isn't it interesting how the rigidity of institutionalised "old economy"-businesses and their management structure as well as their work ethics is, in a way, mimicked by their IT-architecture? Efficiency over effectiveness, stability over flexibility, repetition over creative destruction and innovation. And then came Agile...

  11. Jun 2016