Here's the main RSS feed from phpdeveloper.org:
|Stefan Koopmanschap: To Exception or not to Exception on 21 April 2017||
In the latest post to his site Stefan Koopmanschap offers some advice on and when to avoid them (the result of a recent Twitter discussion).
I recently found myself in a discussion on whether or not exceptions could be used to control program flow in software (specifically in PHP applications). That triggered me to post a tweet:
He goes on to define the term "program flow" and how that relates to the idea of using exceptions to control it. He then talks about naming things, the "intent" of your code and how the right names can make your code clearer and easier to maintain.
|NetTuts.com: How to Create a Laravel Helper on 21 April 2017||
On the NetTuts.com site there's a new tutorial from author Sajal Soni showing you how to , a set of helper functions that can be used through out the entire application.
Laravel includes a variety of global "helper" PHP functions. Many of these functions are used by the framework itself; however, you are free to use them in your own applications if you find them convenient. So, basically, helpers in Laravel are built-in utility functions that you can call from anywhere within your application. If they hadn't been provided by the core framework, you might have ended up developing your own helper classes.
They start by talking about some of the current helpers and the functionality they relate to (arrays, paths, strings, etc). It then goes into the creation of the custom helper including the skeleton of the code layout, where to place them and how to load them into the application via a service provider.
|QaFoo Blog: How You Can Successfully Ship New Code in a Legacy Codebase on 21 April 2017||
On the QaFoo blog there's a new post sharing some ideas on how you can and ship it successfully without too much interruption to the current code.
Usually the problems software needs to solve get more complex over time. As the software itself needs to model this increased complexity it is often necessary to replace entire subsystems with more efficient or flexible solutions. Instead of starting from scratch whenever this happens (often!), a better solution is to refactor the existing code and therefore reducing the risk of losing existing business rules and knowledge.
They then give a few examples of methods that can be use to get the new code in:
The final point is broken down into the process they recommend including the refactor of the current code, starting in on the new implementation and deleting the old code.
|Site News: Popular Posts for This Week (04.21.2017) on 21 April 2017||
Popular posts from PHPDeveloper.org for the past week:
|SitePoint PHP Blog: Getting to Know and Love Xdebug on 20 April 2017||
On the SitePoint PHP blog editor Bruno Skvorc has posted a tutorial , the powerful debugging tool for PHP applications.
It’s been 15 years since Xdebug first came out. We think this is the perfect opportunity to re-introduce it to the world, and explain how and why it does what it does. Xdebug is a PHP extension (meaning it needs to be compiled and installed into a PHP installation) which provides the developer with some features for debugging.
It starts off by explaining some of the functionality that Xdebug brings to your debugging practices and the features that can help make it flow a little easier. It talks about how it differs from some of the IDE debugging tools and services like . Next up is the example putting it to use and what the resulting errors look like. The post then gets into the integration of Vagrant with PhpStorm, using the profiler and how to force the rendering in Laravel output (it normally overrides the exception output with its own formatting).
Also from phpdeveloper.org, here are some Security links:No channel data