Remove Book Remove Software Review Remove Testing
article thumbnail

Book Review: A Philosophy of Software Design

Henrik Warne

I really liked A Philosophy of Software Design by John Ousterhout. The author is a professor of Computer Science at Stanford, but he has also spent 14 years developing commercial software. The book starts with a good chapter on complexity. The goal of software design is to reduce the complexity of the system. Complexity.

article thumbnail

Recruiting Software Developers – Coding Tests

Henrik Warne

In all cases, one or more coding tests were included. I have also been on the interviewing side, evaluating a coding test. Are coding tests needed? When I started out as a software developer, nobody did coding tests as far as I know. Problems With Coding Tests.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Effective Software Testing – A Developer’s Guide

Henrik Warne

I recently finished Effective Software Testing – A Developer’s Guide by Maurício Aniche , and I really liked it. I have been coding for a long time and I think I have been writing pretty good tests for the features I have implemented. Even so, I found this book quite valuable. Most Interesting Chapters.

article thumbnail

Why Testing is No Longer Sufficient for Today’s Software Delivery Pipelines

OverOps

The move to innovate at speed and scale is stressing software quality and exposing the limitations of testing. Don’t get me wrong – testing in all its forms is inseparable from the software delivery supply chain. Testing is no longer enough. The Red Queen Hypothesis (and What it Means for Testing).

article thumbnail

The Real Reasons for Doing Test-Driven Development ??

Xebia

Why do people apply TDD? Here’s a secret: it’s not for the tests. Learn about the actual goal and values hidden under the surface of Test-Driven Development. What Are the Real Reasons for Doing TDD? Test-Driven Development (TDD) is a controversial topic amongst developers. Feedback on what?

article thumbnail

On Code Reviews

Henrik Warne

There seems to be an established truth in programming that code reviews find a lot of bugs. An example is chapter 18 (Modern Code Review ) in the book Making Software. This is however not my experience – I rarely find outright bugs when reviewing changes. Why code review?

article thumbnail

Bliki: TestDrivenDevelopment

Martin Fowler

Test-Driven Development (TDD) is a technique for building software that guides software development by writing tests. In essence we follow three simple steps repeatedly: Write a test for the next bit of functionality you want to add. Write the functional code until the test passes.