Oh Dear is the all-in-one monitoring tool for your entire website. We monitor uptime, SSL certificates, broken links, scheduled tasks and more. You'll get a notifications for us when something's wrong. All that paired with a developer friendly API and kick-ass documentation. O, and you'll also be able to create a public status page under a minute. Start monitoring using our free trial now.

What about "final" and "private"?

Link – Jun 5th 2015

There was much discussion on Twitter about the concepts of using “final” and “private” in objects, and what exactly the best practices are. The conversation seemed to boil down to three distinct questions:

Should an object be open for extension, and expose its internals for that purpose?

Does exposure of those internals create a de facto contract with children for their behavior?

Should software only be used as intended by its designers, or should it be modified, extended and changed by the end user to fit certain, specific goals?

http://www.brandonsavage.net/what-about-final-and-private/

Stay up to date with all things Laravel, PHP, and JavaScript.

You can follow me on these platforms:

On all these platforms, regularly share programming tips, and what I myself have learned in ongoing projects.

Every month I send out a newsletter containing lots of interesting stuff for the modern PHP developer.

Expect quick tips & tricks, interesting tutorials, opinions and packages. Because I work with Laravel every day there is an emphasis on that framework.

Rest assured that I will only use your email address to send you the newsletter and will not use it for any other purposes.

Comments #

What are your thoughts on "What about "final" and "private"?"?

Comments powered by Laravel Comments

Want to join the conversation? Log in or create an account to post a comment.