Other Edited Contributions
From Programmer 97-things
- Abstract Data Types by Aslam Khan
- Acknowledge (and Learn from) Failures by Steve Berczuk
- Anomalies Should not Be Ignored by Keith Gardner
- Avoid Programmer Churn and Bottlenecks by Jonathan Danylko
- Balance Duplication, Disruption, and Paralysis by Johannes Brodwall
- Be Stupid and Lazy by Mario Fusco
- Become Effective with Reuse by Vijay Narayanan
- Better Efficiency with Mini-Activities, Multi-Processing, and Interrupted Flow by Siv Fjellkårstad
- Code Is Hard to Read by Dave Anderson
- Consider the Hardware by Jason P Sage
- Continuous Refactoring by Michael Hunger
- Continuously Align Software to Be Reusable by Vijay Narayanan
- Data Type Tips by Jason P Sage
- Declarative over Imperative by Christian Horsdal
- Decouple that UI by George Brooke
- Display Courage, Commitment, and Humility by Ed Sykes
- Dive into Programming by Wojciech Rynczuk
- Don't Be a One Trick Pony by Rajith Attapattu
- Don't Be too Sophisticated by Ralph Winzinger
- Don't Reinvent the Wheel by Kai Tödter
- Don't Use too Much Magic by Mario Fusco
- Done Means Value by Raphael Marvie
- Execution Speed versus Maintenance Effort by Paul Colin Gloster
- Expect the Unexpected by Pete Goodliffe
- First Write, Second Copy, Third Refactor by Mario Fusco
- From Requirements to Tables to Code and Tests by George Brooke
- How to Access Patterns by Klaus Marquardt
- Implicit Dependencies Are also Dependencies by Klaus Marquardt
- Improved Testability Leads to Better Design by George Brooke
- In the End, It's All Communication by Thomas Lundström
- Integrate Early and Often by Gerard Meszaros
- Interfaces Should Reveal Intention by Einar Landre
- Isolate to Eliminate by Stuart Herbert
- Keep Your Architect Busy by Klaus Marquardt
- Know When to Fail by Geir Hedemark
- Know Your Language by Bob Archer
- Learn the Platform by Vatsal Avasthi
- Learn to Use a Real Editor by Diomidis Spinellis
- Leave It in a Better State by Patrick Kua
- Methods Matter by Matthias Merdes
- The Programmer's New Clothes by Ryan Brush
- Programmers Are Mini-Project Managers by Jonathan Danylko
- Programmers Who Write Tests Get More Time to Program by Johannes Brodwall
- Push Your Limits by Karoline Klever
- QA Team Member as an Equal by Ravindar Gujral
- Reap What You Sow by Seb Rose
- Respect the Software Release Process by Pete Goodliffe
- Restrict Mutability of State by Kevlin Henney
- Reuse Implies Coupling by Klaus Marquardt
- Scoping Methods by Michael Hunger
- Simple Is not Simplistic by Giovanni Asproni
- Small! by Uncle Bob
- Soft Skills Matter by Bruce Rennie
- Speed Kills by Uncle Bob
- Structure over Function by Peter Sommerlad
- Talk about the Trade-offs by Michael Harmer
- There Is Always Something More to Learn by Klaus Marquardt
- There Is No Right or Wrong by Mike Nereson
- There Is No Such Thing as Self-Documenting Code by Carroll Robinson
- The Three Laws of Test-Driven Development by Uncle Bob
- Understand Principles behind Practices by Steve Berczuk
- Use Aggregate Objects to Reduce Coupling by Einar Landre
- Use the Same Tools in a Team by Kai Tödter
- Using Design Patterns to Build Reusable Software by Vijay Narayanan
- Who Will Test the Tests Themselves? by Filip van Laenen
- Work with a Star and Get Rid of the Truck Factor by Cecilia Sjölin and Ida Hveding Huse
- Write a Test that Prints PASSED by Kevin Kilzer
- Write Code for Humans not Machines by Mario Fusco
