BT

InfoQ Homepage Software Craftsmanship Content on InfoQ

  • Readable Code - Why, How and When You Should Write It

    Most people would say they want readable code, and may even prefer readability over functionality. But when it comes down to asking people to define readability, opinions will start to diverge. At Explore DDD 2018 , Laura Savino covered why we want readable code, what it really means to be readable, and when readability absolutely must take priority over other considerations.

  • Focusing on Business Outcomes at Barclays: Overcoming the "Urgency Paradox"

    Jonathan Smart, head of working ways, and Morag McCall, PMO at Barclays, spoke last month at the DevOps Enterprise Summit in London about re-thinking the entire flow of work, from initial idea triage until releasing to production. This means introducing agility into how the application and services portfolio is managed, as well as changing the role of the PMO and finance departments.

  • Getting More Work Done in Fewer Working Hours

    When Jason Lengstorf’s body was actively falling apart due of the way he was working, he decided to limit his computer usage and create pockets of high-focus effort. Working fewer hours prevents you from becoming overtired or unfocused. We need to treat downtime with the same level of care as we treat our uptime, using breaks to make creative connections, recharge, and to remember why we work.

  • Sustainable Software with Agile

    Sustainable software enables you to deliver changes to the customer more quickly with a lower likelihood of bugs, decrease of the total cost of ownership of applications, and increase business agility. It’s possible to verify the sustainability of software using a combination of automated analysis of source code, expert review of technical artifacts, and comparison with benchmark data.

  • Software Engineering for Creativity, Collaboration, and Inventiveness

    A software engineering discipline must be iterative, based on feedback, incremental, experimental, and empirical. Craftsmanship is not sufficient; engineering is an amplifier, it enhances creativity, collaboration, and inventiveness. Continuous delivery is grounded in engineering principles.

  • Oath for Programmers

    Our society demands a commitment to professional behavior; we need an oath for programmers as lives and fortunes depend upon the proper construction and execution of software, argues Robert Martin. According to him, this will have to be enforced by membership in an professional association.

  • Tackling Technical Debt at Meetup

    Continuous product health can be realized by regularly prioritizing the highest impact technical debt items and knocking those off systemically. You need to continuously iterate how you're tackling technical debt to drive more and more impactful results. Going for maximum impact items first and communicating the impact of paying down technical debt is what Yvette Pasqua, CTO of Meetup, recommends.

  • Adopting Agile and DevOps at Wyndham Vacation Rentals UK

    Embedding agile and DevOps had a positive impact on the role of QA at Wyndham; focusing effort in the earlier lifecycle stages has led to smoother releases with fewer bugs and post-production issues. Business colleagues and customers are more involved throughout the delivery cycle, making testing a shared responsibility .

  • Managing Crowdsourced Testing

    Crowdsourced testing is a unique way of involving the crowd- meaning the real users/testers- into software testing under real world conditions. It helped Swisscom to find defects very early in the development process and increase the quality of products.

  • Putting Quality Back in Agile with Lean

    The agile manifesto and lean practices are very complementary; lean can be a useful addition to a very strong agile process to increase quality. Interviewing real clients or client proxies to deeply understand their pain points and visualizing the process by diving into the handovers between departments helps to uncover problems faster and fix those problems more efficiently for a lower price.

  • Evan Leybourn of IBM on the Theory of Agile Constraints

    Evan Leybourn is talking at the upcoming Agile Indonesia conference. He spoke to InfoQ about his Theory of Agile Constraints, defining value in an initiative, agile budgeting and #NoProjects.

  • How Testers Can Become More Technical

    Testers who are able to successfully apply technical techniques of the testing craft during testing are more valuable; they increase both the quality and productivity of their teams. To become more technical, testers can learn something about code, and they should know how to manipulate and parse text files and how to use the most important analysis tools for their application platform.

  • Bridging the Gap between Legacy Systems and Modern Techniques

    Aging platforms that are managed with manual, time consuming processes can be costly. Teams can make a business case to management based on hours lost by repetitive work or re-work caused by human error for introducing modern techniques like automation tools and containers. The result is a predictable and repeatable process with minimal human interaction to deploy more often and more confidently.

  • Refocusing e-Commerce with Lean

    Auchan:Direct, the online grocery delivery service of Auchan France, decided to apply lean to develop a new e-Commerce website. Their CEO was the first customer and they used continuous and fast feedback from their clients on the new experience to improve website quality using continuous delivery.

  • Scaling Lean Startup: Principles over Process

    Large organizations want to be like lean start-ups but they need to rethink how they hire, incentivize and manage their staff to become an agile organization. Organizations should reward teams for making low-risk decisions based on what they can learn quickly and build in the value of learning in addition to delivery.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.