PHP Architect · Vol 21, Issue 4 · April 2022
by Edward Barnard
When the new requirement arrives, does this mean we cram it in the best place, making our software more difficult to work with, or might we have ways to make the result cleaner than before we started? We’ll take advantage of Martin Fowler’s concept of Preparatory Refactoring.
The full article is in PHP Architect Vol 21, Issue 4. Subscribe to read it and every new issue.
About the author
Ed Barnard had a front-row seat when the Morris Worm took down the Internet, November 1988. He was teaching CRAY-1 supercomputer operating system internals to analysts as they were being directly hit by the Worm. It was a busy week! Ed continues to indulge his interests in computer security and teaching software concepts to others.
Collaborating with industry leaders to bring you the best PHP resources and expertise
Interested in partnering? Get in touch →
