Other Edited Contributions

From Programmer 97-things

Revision as of 10:17, 17 February 2010 by Kevlin (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search
  1. Abstract Data Types by Aslam Khan
  2. Acknowledge (and Learn from) Failures by Steve Berczuk
  3. Anomalies Should not Be Ignored by Keith Gardner
  4. Avoid Programmer Churn and Bottlenecks by Jonathan Danylko
  5. Balance Duplication, Disruption, and Paralysis by Johannes Brodwall
  6. Be Stupid and Lazy by Mario Fusco
  7. Become Effective with Reuse by Vijay Narayanan
  8. Better Efficiency with Mini-Activities, Multi-Processing, and Interrupted Flow by Siv Fjellkårstad
  9. Code Is Hard to Read by Dave Anderson
  10. Consider the Hardware by Jason P Sage
  11. Continuous Refactoring by Michael Hunger
  12. Continuously Align Software to Be Reusable by Vijay Narayanan
  13. Data Type Tips by Jason P Sage
  14. Declarative over Imperative by Christian Horsdal
  15. Decouple that UI by George Brooke
  16. Display Courage, Commitment, and Humility by Ed Sykes
  17. Dive into Programming by Wojciech Rynczuk
  18. Don't Be a One Trick Pony by Rajith Attapattu
  19. Don't Be too Sophisticated by Ralph Winzinger
  20. Don't Reinvent the Wheel by Kai Tödter
  21. Don't Use too Much Magic by Mario Fusco
  22. Done Means Value by Raphael Marvie
  23. Execution Speed versus Maintenance Effort by Paul Colin Gloster
  24. Expect the Unexpected by Pete Goodliffe
  25. First Write, Second Copy, Third Refactor by Mario Fusco
  26. From Requirements to Tables to Code and Tests by George Brooke
  27. How to Access Patterns by Klaus Marquardt
  28. Implicit Dependencies Are also Dependencies by Klaus Marquardt
  29. Improved Testability Leads to Better Design by George Brooke
  30. In the End, It's All Communication by Thomas Lundström
  31. Integrate Early and Often by Gerard Meszaros
  32. Interfaces Should Reveal Intention by Einar Landre
  33. Isolate to Eliminate by Stuart Herbert
  34. Keep Your Architect Busy by Klaus Marquardt
  35. Know When to Fail by Geir Hedemark
  36. Know Your Language by Bob Archer
  37. Learn the Platform by Vatsal Avasthi
  38. Learn to Use a Real Editor by Diomidis Spinellis
  39. Leave It in a Better State by Patrick Kua
  40. Methods Matter by Matthias Merdes
  41. The Programmer's New Clothes by Ryan Brush
  42. Programmers Are Mini-Project Managers by Jonathan Danylko
  43. Programmers Who Write Tests Get More Time to Program by Johannes Brodwall
  44. Push Your Limits by Karoline Klever
  45. QA Team Member as an Equal by Ravindar Gujral
  46. Reap What You Sow by Seb Rose
  47. Respect the Software Release Process by Pete Goodliffe
  48. Restrict Mutability of State by Kevlin Henney
  49. Reuse Implies Coupling by Klaus Marquardt
  50. Scoping Methods by Michael Hunger
  51. Simple Is not Simplistic by Giovanni Asproni
  52. Small! by Uncle Bob
  53. Soft Skills Matter by Bruce Rennie
  54. Speed Kills by Uncle Bob
  55. Structure over Function by Peter Sommerlad
  56. Talk about the Trade-offs by Michael Harmer
  57. There Is Always Something More to Learn by Klaus Marquardt
  58. There Is No Right or Wrong by Mike Nereson
  59. There Is No Such Thing as Self-Documenting Code by Carroll Robinson
  60. The Three Laws of Test-Driven Development by Uncle Bob
  61. Understand Principles behind Practices by Steve Berczuk
  62. Use Aggregate Objects to Reduce Coupling by Einar Landre
  63. Use the Same Tools in a Team by Kai Tödter
  64. Using Design Patterns to Build Reusable Software by Vijay Narayanan
  65. Who Will Test the Tests Themselves? by Filip van Laenen
  66. Work with a Star and Get Rid of the Truck Factor by Cecilia Sjölin and Ida Hveding Huse
  67. Write a Test that Prints PASSED by Kevin Kilzer
  68. Write Code for Humans not Machines by Mario Fusco
Personal tools