Hannes Van De Vreken has a new post on the madewithlove blog on why you should avoid over-abstracting:
Some time ago I started working on an existing project, so I read the documentation before diving in. At the top of the contributing.md file there was this sentence: “Abstract when possible”. Quickly I learned the project contained more abstract classes than a normal project. This leads to too highly coupled, and often unchangeable code.
This post is dedicated on explaining why “abstract when possible” isn’t good advice. Not only in PHP, but in all programming languages.
Filed in: Laravel Tutorials
Join the weekly newsletter and never miss out on new tips, tutorials, and more.
- Senior Software Engineer - LAMP/PHP/MySQL/Laravel
Los Angeles / Remote
- Senior PHP/Laravel Developer: Your Dream Work Environment
iPhone Photography School
- In-house Laravel Developer.
Gold Coast / Australia
- Laravel Developer
Oak Brook, IL
- Senior Backend Engineer
Santa Monica only
- Senior Laravel Developer
- Senior Software Developer
South Jordan, UT
LaraJobs + Linode = Side Gig Heaven
Hey there! Over the last few months, LaraJobs has really blown up! We’re seeing more great job posts than ever. To ce…
PSequel – PostgreSQL GUI tool for Mac OS X
For all the Postgres fans, here is a nice looking tool for Mac OS X: Designed for Yosemite. Written in Swift. PSequel…