Programming

293 Items

Sort by Date | Title

How to Build a Strong Virtual Team: By Karen N. Johnson; May 11, 2010; Karen N. Johnson provides valuable advice for establishing and maintaining virtual relationships with team members. Using senses other than just your sight, paying attention to subtle clues, and putting in a little extra effort to be available when needed can help you to build a strong team that works together even when they're physically separated.

Improve Your Testing and Your Testers with Paired Testing: By Karen N. Johnson; Apr 27, 2010; Have you ever had testers on your team whose knowledge and skill sets were complementary, and wondered how you could encourage them to exchange and collaborate so that they could both increase their skills? Author Karen Johnson shows a different approach to testing and some of the advantages of pairing testers.

The Design of Design: Exemplars in Design: By Frederick P. Brooks; Apr 19, 2010; Few designs are all-new. Usually, even novel designs derive from earlier artifacts intended for similar purposes and built with similar technology. What then is the proper role of exemplars, precedents, in design? How should the designer study and use them? Should each design domain develop an accessible cumulative store of exemplars? Frederick P. Brooks considers these questions in this excerpt from his book, The Design of Design.

Software [In]security: The Smart (Electric) Grid and Dumb Cybersecurity: By Gary McGraw; Mar 26, 2010; Security expert Gary McGraw explains why the rush to upgrade our power grid may lead to security vulnerabilities in critical infrastructure.

Agile Product Management with Scrum: Understanding the Product Owner Role: By Roman Pichler; Mar 24, 2010; A new product is launched with great expectations—and bombs. What went wrong? There was no single person responsible for leading the effort to create a winning product—a product owner. This chapter explores the role of the product owner. It explains the role's authority and responsibility as well as how the role should be applied.

Software [In]security: What Works in Software Security: By Gary McGraw, Brian Chess, Sammy Migues; Feb 26, 2010; 15 of the 110 activities in the BSIMM are very commonly observed. Gary McGraw, Brian Chess, and Sammy Migues list and explain these activities.

Software [In]security: Cargo Cult Computer Security: By Gary McGraw; Jan 28, 2010; Gary McGraw argues that the time is right to turn to real science to combat the "Cargo Cult" mentality of the software security field.

What Programmers Have to Know About Testing: By Janet Gregory; Jan 11, 2010; Janet Gregory offers some good advice to developers: Even when you know that a dedicated test team will be testing your software, there are some things that your programming team shouldn't leave for the testers to find.

Being Methodical About Test Design: By James A. Whittaker; Dec 29, 2009; James Whittaker suggests that developers and testers treat the software as a system and consider specific system attributes and properties as a way to design test cases. As he explains, applying these ideas at Google has resulted in both more effective manual testing and a new way to design test automation.

Software [In]security: You Really Need a Software Security Group: By Gary McGraw; Dec 21, 2009; Gary McGraw explains why having a software security group is necessary for a software security initiative.

Succeeding with Agile Software Development Using Scrum: Team Structure: By Mike Cohn; Dec 1, 2009; In this chapter Mike Cohn looks at the importance of two critical factors to be considered when deciding how to structure Scrum teams: keeping teams small and orienting each team around the delivery of end-to-end user-visible functionality

Software [In]security: BSIMM Europe: By Gary McGraw, David Harper, Matias Madou, Florence Mottay; Nov 10, 2009; Security expert Gary McGraw and team introduce BSIMM Europe and compare some of its initial results to the original BSIMM data.

On Iteration: By Andrei Alexandrescu; Nov 9, 2009; Andrei Alexandrescu provides a fresh perspective on iteration and proposes a new approach to iteration that builds on the strengths of abstractions defined by other languages and libraries. The proposed framework is sensible and expressive, yet one that is simple and obvious in hindsight.

Software [In]security: Startup Lessons: By Gary McGraw; Oct 22, 2009; Gary McGraw discusses the seven lessons he's learned through his startup years at Cigital.

Test-Driven Development with Objects: By Steve Freeman, Nat Pryce; Oct 22, 2009; The authors of Growing Object-Oriented Software, Guided by Tests discuss test-driven development with objects.

The Case for Manual Software Testing: By James A. Whittaker; Oct 15, 2009; James A. Whittaker explains why the world of manual exploratory testing is one of the most challenging and satisfying jobs in the IT industry.

Kicking the Code Monkey: Migrating Your Ancient Code for Fun and Profit: By Phillip Culliton; Sep 25, 2009; Phillip Culliton gropes through the darkness of prehensile programming to find and deliver a sound thrashing to the code monkey (that's you) who needs to migrate old code to a new language - but hasn't done it yet.

Software [In]security: BSIMM Begin: By Gary McGraw, Sammy Migues; Sep 24, 2009; Gary McGraw introduces BSIMM Begin, a Web-based study focused on 40 of the 110 activities covered in the full Building Security In Maturity Model.

Robert C. Martin's Clean Code Tip #12: Eliminate Boolean Arguments: By Robert C. Martin; Aug 25, 2009; We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this twelfth tip in the series, the crew learns that Boolean arguments loudly declare that the function does more than one thing. They are confusing and should be eliminated.

Software [In]security: Attack Categories and History Prediction: By Gary McGraw; Aug 25, 2009; Software security expert Gary McGraw describes how to divide attacks into four categories — and predict the attacks of tomorrow.