News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Kevin Schroeder's Blog:
What programming rules should you ALWAYS follow?
November 09, 2011 @ 09:20:37

In a quick new post today Kevin Schroeder asks his readers for feedback on what programming rules you should always follow in your development practices.

Earlier today, more for my own interest, I asked the question on Twitter "What programming rules should you ALWAYS follow, regardless of the scenario you're working in?" In other words, are there programming rules that you ALWAYS should follow. It doesn't matter if it's a script to copy a bunch of files for a one time migration or if you're building the next Facebook (DON'T try to build the next Facebook. You will fail miserably. Build something else). In other words, what was the purist of programming rules.

Responses he received ranged from the simple to slightly more complex including:

  • Always comment your code
  • Test your code
  • Use source control
  • "Think. Think again. Then write code"
  • Use a good debugger to help track down problems
  • Make effective use of logging/output
0 comments voice your opinion now!
programming rules opinion recommendation twitter


blog comments powered by Disqus

Similar Posts

PHP Magazine: PHP Frameworks Trends

Stuart Herbert's Blog: Introducing ContractLib (Programming Contracts)

NetTuts.com: Aspect-Oriented Programming in PHP with Go!

Lee Davis: Is a HTTP DELETE request idempotent?

Matthew Weier O'Phinney: On Microframeworks


Community Events

Don't see your event here?
Let us know!


symfony2 application configure php7 conference release laravel api language interview framework opinion podcast community series library part2 performance example introduction

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework