Programming

293 Items

Sort by Date | Title

Move Semantics in C++11, Part 1: A New Way of Thinking About Objects: By Danny Kalev; Jul 2, 2012; Not every resource transfer is a copy operation. In many programming tasks, the resource only moves from one object to another, emptying the source object in the process. The semantics and formal properties of these 'move semantics' are a new C++11 paradigm to make code more efficient and simulate real-world situations more accurately, as Danny Kalev explains in this two-part series.

Testing the Big Picture on Agile Teams: By Janet Gregory, Lisa Crispin; May 23, 2012; One of the biggest problems on many agile teams is forgetting the real business value of the feature they are developing. Even with all the testing done for each story, the team may deliver a feature that has outstanding issues, or does not meet the customer’s expectations. This article covers how to balance the fast feedback of working in small increments and iterations with ensuring that the overall feature delivers adequate business value.

Seven Ways to Find Software Defects Before They Hit Production: By Matthew Heusser; May 11, 2012; If you've ever been surprised by a bug that seemed obvious in hindsight, you may be curious where test ideas originate and how to generate more of them. Matt Heusser walks through a half-dozen ideas to kickstart (or reinvigorate!) your software testing.

Introduction to Google Software Testing: By James A. Whittaker; Apr 5, 2012; James A. Whittaker, the former Test Director for Chrome and Chrome OS, discusses his book, How Google Tests Software, what it means to be a Google tester and how Google testers approach the problems of scale, complexity and mass usage.

Three Things I Learned about Testing at Google that Might Surprise You: By James A. Whittaker; Mar 20, 2012; Over the course of his time at Google, James A. Whittaker learned a few valuable lessons about software testing, which he shares here.

Source Code Is Dead! Long Live Source Code!: By Dhanji R. Prasanna; Mar 19, 2012; Dhanji R. Prasanna illuminates the unseen (and often unconsidered) costs to a company of keeping its source code proprietary and closed, rather than sharing it as open source with the world.

Software [In]security: vBSIMM Take Two (BSIMM for Vendors Revised): By Gary McGraw, Sammy Migues; Jan 26, 2012; Gary McGraw and Sammy Migues introduce a revised, compact version of the BSIMM for vendors called vBSIMM, which can be thought of as a foundational security control for vendor management of third-party software providers.

Analysis for Continuous Delivery: Five Core Practices: By Jez Humble; Jan 25, 2012; Jez Humble, coauthor of Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation, urges teams to move away from the all-or-nothing design of traditional software delivery approaches. Following the practices outlined here, you can deliver single-feature or small-story batches that dramatically decrease the time needed to build a new product or new release, testing and moving forward on successful features and redesigning or dropping features that fail (or that users show they don't really want).

Exploring the Mythical Weekend Coding Project: By Dhanji R. Prasanna; Jan 24, 2012; Did you ever spend a weekend working through some kooky idea for coding an app you'd had in mind for years? Like many of us, Dhanji R. Prasanna has carried concepts around in his mental pockets, and one day he decided to go ahead and try it. The goal was a working app in two days. Would he succeed or fail miserably? Some things he learned were to be expected, but others he could never have predicted.

Software [In]security: BSIMM versus SAFECode and Other Kaiju Cinema: By Gary McGraw, Sammy Migues; Dec 26, 2011; Gary McGraw and Sammy Migues clarify the intended use of the Building Security In Maturity Model (BSIMM) and compare it to the SAFECode Practices methodology.

An Academy for Software Craftsmen? An Interview with Founder Ken Auer: By Matthew Heusser, Ken Auer; Dec 20, 2011; For all the talk of craftsmanship and apprentices, there is only one commercial school in the world offering a journeyman rating: The RoleModel Software Craftsmanship Academy in Holly Springs, North Carolina. We interviewed Ken Auer to find out where the idea came from, how the program works, and why it's necessary today.

Software [In]security: Third-Party Software and Security: By Gary McGraw, Brian Chess, Sammy Migues; Nov 30, 2011; How do you gauge the security of third-party code? A recent security conference examined that question, and Gary McGraw presents the findings in this article.

Software Systems Architecture: Viewpoints and Views: By Nick Rozanski, Eóin Woods; Nov 10, 2011; Capturing the essence and the detail of the whole architecture in a single model is just not possible for anything other than simple systems. By far the best way of managing this complexity is to produce a number of different representations of all or part of the architecture, each of which focuses on certain aspects of the system, showing how it addresses some of the stakeholder concerns.

Software [In]security: Software Security Training: By Gary McGraw, Sammy Migues; Oct 31, 2011; Gary McGraw and Sammy Migues describe how training has changed, provide data showing it's importance, and explain why it's important to pick the right training for your organization's needs.

Want to Prove Agile Works? Practice Continuous Delivery!: By Aaron Erickson; Oct 31, 2011; Aaron Erickson, author of The Nomadic Developer, explains why Agile development teams must deliver and keep delivering on a regular schedule. The surest proof of your team's practicing Agile methodology correctly is that you continue delivering working product.

Software [In]security: BSIMM3: By Gary McGraw, Brian Chess, Sammy Migues; Sep 27, 2011; BSIMM3 is the third iteration of the Building Security In Maturity Model (BSIMM) project, a tool used as a measuring stick for software security initiatives in the corporate world. Gary McGraw describes the BSIMM3 along with Brian Chess and Sammy Migues.

Software [In]security: Balancing All the Breaking with some Building: By Gary McGraw; Aug 30, 2011; Security expert Gary McGraw argues that the software security industry is favoring offense at the expense of defense, and that more proactive defense is needed.

Essential Skills for the Agile Developer: Avoid Over- and Under-Design: By Alan Shalloway, Scott Bain, Amir Kolsky, Ken Pugh; Aug 29, 2011; How do you avoid over- or under-designing your code? As Ward Cunningham once said, "Take as much time as you need to make your code quality as high as it can be, but don't spend a second adding functionality that you don't need now!" This chapter covers this "mantra for development: write high-quality code, but don't write extra code.

Ten Years Of Agile: An Interview with Robert C. "Uncle Bob" Martin: By InformIT Editorial Team, Robert C. Martin; Aug 3, 2011; InformIT interviews Uncle Bob Martin, one of the original Agile Manifesto signatories, on the ten-year anniversary of its creation.

Putting the "Journey" in Journeyman Software Developer: An Interview with Corey Haines: By Matthew Heusser, Corey Haines; Jul 25, 2011; When it comes to putting the craft back into programming, a handful of names might come to mind, and Corey Haines is one of them. Matthew Heusser talked with Corey about software craft, his journeyman project, and that great big project he is working on next.