This is a question that frequently arises. Someone will ask me “Oh, you [work with/prefer/love] Laravel?” and my answer to that is a simple yes. What baffles me is the very frequent follow up question to that, which is “Well, what about Symfony?”. Every time I get this question, I’m stricken by it because I have never understood the question. It seems like there is a battle, Laravel vs Symfony.
I recently stumbled upon an interesting problem when trying to retrieve the raw POST body in Laravel. This happened when I was sending POST/PUT requests from AngularJS to a REST API that was built with Laravel. I did a lot of trial and error before I figured out the problem.
If you happen to be using PHP Mess Detector (which you should for any larger project) you have probably stumbled upon these two, but do you really know what they stand for? NPath complexity and cyclomatic complexity sounds really scary, but they are fancy words for quite simple concepts. So let’s go through them and also find out why they’re important for maintainable and testable code. Both of these concepts are used in static code analysis and are measurements of how complex a function is.
To me it’s essential as a developer to read books, and not just looking things up on the internet. The depth of a book can not be compared to almost anything you find on the web. Keeping your knowledge fresh is important and I tend to try to read my books as often as I feel like it and have the time. What you learn by reading a book once is nothing compared to reading it perhaps two or more times. I’ll share with you a selection of books I have, mostly in my Kindle or Leanpub library, which I’ve found to help me a lot. Some of the books are not PHP specific, but are for developers in general or about software development as a concept. Some of the books are a lot about code while others are more about getting you to think about what you’re doing and how you can improve it.