Martin Fowler published an article on his website describing the different workflows that could be used when refactoring and explaining the reasons for combining them.
The goal of a software project is to deliver value to stakeholders and Behaviour-Driven Development, (BDD), is designed for that, Viktor Farcic, a software developer working on transitions from waterfall to agile processes, states in the first of four blog posts describing his view on BDD.
Mobile Backend as a Service provider AnyPresence continues to hone their chops. Launching the fifth update to their self-titled platform geared for the enterprise. Co-founder Rich Mendis provides some insights for InfoQ readers…
The Behaviour Driven Development, BDD, tool Cucumber is popular in Ruby’s TDD community. It offers a way to write tests that anybody can understand, but is any of the benefits of Cucumber really that beneficial, Kevin Liddle asks in a case against Cucumber. Jon Frisby and Matt Polito has each written a response somewhat arguing against Kevin’s ideas, both seeing benefits in using Cucumber.
Agile has helped us move away from creating upfront requirements but we still have a huge amount of waste with lots of discovery and misunderstandings late in sprints. BDD is meant to decrease this by improving the communication between people working in the problem and solution domains, Matt Wynne states in a recent overview of Behaviour-Driven Development.
Start using Behaviour-Driven Development (BDD) when designing an application and focus on the domain instead of the database, Julie Lerman, a Microsoft MVP since 2003, suggests. BDD lets developers focus on user stories and behaviour in the business domain when building up logic and tests. New to BDD, Julie has implemented a working example using Visual Studio, C# and SpecFlow.
The project for Cucumber, a Behaviour Driven Development, BDD, tool, has recently increased the team and intensive work last months has brought open bugs down substantially, Aslak Hellesøy revealed when talking about the Cucumber ecosystem during a Cucumber conference day last week.
The community research we published on .NET tools and practices had more than 650 votes leading to some interesting results. We attempt to draw insights.
InfoQ's research initiative continues with an 8th question: "What are the most widely used .NET practices and tools?". This is a new service we hope will provide you with up-to-date & bias-free community-based insight into trends & behaviors that affect enterprise software development. Unlike traditional vendor/analyst-based research, our research is based on answers provided by YOU.
Wikispeed founder Joe Justice gave a talk in Wellington, New Zealand, this week in which he spoke about the Wikispeed mission of "Rapidly Solving Problems for Social Good", starting by using agile techniques to build a 100MPG vehicle with the intent of creating a new approach to motor-vehicle manufacturing, using open-source and crowd-source approaches building on agile values and principles.
Recently Cap Gemini's Steve Jones has written an article on how he believes that thinking about solutions to problems is less important these days than jumping on the latest hype bandwagon. Although he uses REST and Big Data as examples, he believes it goes beyond any single technology and that eventually IT will no longer belong to IT people.
Mighty-Moose, a continuous build and test-runner for .NET, now comes free of charge.
Dan North has recently discussed the impact of opportunity costs in his article "The Art of Misdirection." Opportunity Cost is about choosing an obvious solution for a particular problem context, although sometimes an alternative option may be the better choice. Software engineers, in particular, are subject to such opportunity costs as they are constantly facing decisions in their daily work.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.