Group items matching

in title, tags, annotations or url

2. Use Many Tables With PHP and MYSQL for Scalability – Matt Mullenweg

3. Never, ever trust your users – Dave Child

4. Invest in PHP Caching – Ben Balbo

5. Speed up PHP Development with an IDE, Templates and Snippets – Chad Kieffer

6. Make Better Use of PHP’s Filter Functions – Joey Sochacki

7. Use a PHP Framework – Josh Sharp

8. Don’t use a PHP Framework – Rasmus Lerdorf

9. Use Batch Processing – Jack D. Herrington

10. Turn on Error Reporting Immediately – David Cummings

Third, you make a little change to your functional code

Next, you run the tests

In the optional fifth step, you refactor your code to remove any duplication.

two simple rules. First, you should write new business code only when an automated test has failed. Second, you should eliminate any duplication that you find.

Your designs must consist of highly cohesive

You write your own tests because you can’t wait

the running code providing feedback between decisions

Test-Driven Development (Addison-Wesley 2003)

a Smalltalk system with a completely test-driven approach that took four years and 40 person-years of effort

there’s far more to testing than unit tests, so you’ll still need other testing techniques such as functional testing, user acceptance testing, system integration testing and so on.

you have a clear measure of success

most programmers don’t read the written documentation for a system; instead, they prefer to dig right into the code.

Your acceptance tests define exactly what your stakeholders expect of your system; therefore, they truly do determine a good portion of your requirements.

Bob Martin says it best: “The act of writing a unit test is more an act of design than of verification. It’s also more an act of documentation than of verification.

Side by Side: Comparing TDD and AMDD TDD shortens the programming feedback loop; AMDD abridges the modeling feedback loop. TDD provides detailed specification (tests), while AMDD provides traditional specifications (agile documents). TDD promotes the development of high-quality code; AMDD encourages high-quality communication between your stakeholders and other developers. TDD provides concrete evidence that your software works, whereas AMDD supports your entire team, including stakeholders, in working toward a common understanding. TDD provides finely grained, concrete feedback in minutes. However, concrete feedback requires developers to follow the practice Prove It With Code, and they may become dependent on non-AM techniques; AMDD lets you get verbal feedback in minutes. TDD ensures that your design is clean by focusing on creation of callable and testable operations; AMDD lets you think through larger design and architectural issues before you code. TDD isn’t visually oriented; AMDD is. Both techniques are new and therefore may be threatening to traditional developers. Both techniques support evolutionary development. —S. W. Ambler

Valid URL

Cleaning values

Why not use a CAPTCHA?

Security Gurus?

we now have PHP developers going around developing inferior software

We have developers obsessed with micro-optimizations and zombie followers of design patterns when the truth of the matter is that had they just been introduced the language properly in the first place many of these concepts would become like second nature

senior members of the PHP community need to, for the sake of our beloved language, shift some of the focus of our discussions and our articles back to PHP. Just pure PHP.

I hate PHP frameworks. They do absolutely nothing to aid in the learning of the language and, at the rate that they are going, we’ll soon find that PHP frameworks abstract away PHP itself.