A run through of the Return Void Type, why it can be useful and why some of the points against are not so strong to me.
Dear PHP Community: These are the folks behind The League of Extraordinary Packages, who you should know, but maybe do not.
If you have documentation for any sort of HTTP-based API, from a micro-service to a non-trivial RESTful API, if it has existed for more than a week it has got some mistakes in it. Documentation degrades over time. This article aims to help you ensure that your API documentation keeps entirely in line with the implementation, utilizing two tools: API Blueprint and Dredd.
Some people like to take a quick walk down memory lane in January, and post their highlights of the previous year.
The answer to "What is the State of Markdown?" is "Yes, it's a f**king state."
A while ago Treehouse got in touch with me, and asked me if I would be interested in working with them on a video course. They wanted more PHP-related content, and they had heard I knew a thing or two about that.
A few months ago I wrote a bit of an emotional article about my visa status, and how I was in a bit of a pickle. A few people since have wanted an update, so here it is.
When is it a good idea to commit your composer.lock file, and when should you leave it out?
I've been talking recently about what The League of Extraordinary Packages is up to in regards to components, and made a plea to avoid "Not Invented Here" syndrome to help the community focus on quality instead of quantity. Today I noticed a new pet-peeve.
In the last article I said I wanted to write about when its a good idea to release a component. A lot of this comes down to: is there one out there that does what I want, and if so, can I use it? Should I release a PR or make my own? Why should I maybe avoid writing something that already exists?