Process

Better Software Magazine Articles

Tinkerable Software

In what ways should software be like a house? In a recent issue of STQE magazine, Technical Editor Brian Marick’s musings about the concept of “tinkerable software” generated some interesting discussion about the very nature of software design. This week’s column runs a portion of that piece so that our Sticky-minded readers can sink their thoughts into the concept.

Brian Marick's picture Brian Marick
Introducing Test-First Development

Testers are often frustrated to receive a product for testing that is riddled with bugs. They want to know why some of the bugs couldn't have been caught during development. If only some tests could be run before the code was handed off! Jason Bedunah learned the benefits of test-first development first hand. Here, he introduces a framework for testing and coding that he found to be very helpful, and he gives some pointers on getting developers on board with test-first development.

Jason L. Bedunah's picture Jason L. Bedunah
Faults of Omission

Brian Marick is obsessed with faults of omission in software code, and he thinks you should be too. In this Bug Report, Marick describes coding omissions, design omissions, and requirements omissions, and offers some ways to prevent (or at least test) them.

Brian Marick's picture Brian Marick
A Look at Cost Xpert

John Magill found Marotz's Cost Xpert 2.0 to meet his requirements, offer some important relevant program factors, and permit him to change or adjust the factors to establish an estimating window or boundaries, all at a competitive price.

John Magill's picture John Magill
A Look at e-Test Suite 301 by RSW

RSW Software’s e-Test Suite contains four main components. The reusable scripts recorded with RSW e-Tester (the functional testing tool) feed RSW e-Load (the performance and stress-testing tool). For reporting and analysis purposes, results gathered during performance testing feed to RSW e-Reporter. The final tool, RSW e-Monitor, is responsible for monitoring the status of Websites by sending periodic page requests and validating them against previously recorded results.

Christopher Nolan's picture Christopher Nolan
My Summer as a Hacker

Pete TerMaat shares some valuable lessons learned from a summer with "hacking legend" Richard Stallman. He learned that attitude, passion for one's work, was most important. Reviews, coding standards, porting guidelines, bug hunting advice, and other measures can fall flat without a passion for clean code, for "getting things right."

Pete TerMaat's picture Pete TerMaat
A Study in Failures

Examples of mistakes, manifestations, and problems help us understand all parts of the software. Brian Marick suggests Web resources that examine software failures.

Brian Marick's picture Brian Marick
Learning to Love Unit Testing

Unit testing can become a developer's best friend. Find out how and why from two programmers who now rely on this practice to improve development.

Andy Hunt's picture Andy Hunt Dave Thomas
The Two Bugs

Brian Marick applies the philosophical concept of "ready-to-hand" to software programming and describes two bugs that illustrate problems caused by mismatched reuse of ideas.

Brian Marick's picture Brian Marick
Book Review: Adaptive Software Development

Johanna Rothman recommends the book Adaptive Software Development by James Highsmith. She says, "Highsmith shows the reader how to recognize when development practices need to change and how to acquire the skills to adapt. For a fresh approach to software development, be sure to check it out."

Johanna Rothman's picture Johanna Rothman

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.