 | News Feed |
Sections
|
Piotr Pasich:
ClassManager - You shall not pass
by Chris Cornutt January 30, 2015 @ 11:42:55
Piotr Pasich has shared some thoughts on naming in his latest post to his site today. In it he talks about one of the "hardest things in computer science" (naming things) and makes some recommendations to help you make naming in your code more effective.
Precise names for classes is notoriously difficult. Done right, it makes code more self-documenting and provides a vocabulary for reasoning about code at a higher level of abstraction. There are a couple simple tips&tricks to make the names more readable: do not abbreviate, do not add any extra informations (underscore, type), avoid single letter prefixes, etc etc.
But what if you already know and use those rules and you still want to improve naming in your code? I assume that you care, you're not selfish and you think about elses when you write the code. You ask one of the most important question to yourself, during architecture implementation - how the fellow sitting next to will behave while reading the code.
He's broken up the remainder of the post into different sections, each with a high level recommendation and some follow up description:
- Ask somebody else
- Does it have a single responsibility you can name?
- Simple Superclass Name
- Qualified Subclass Name
- Adding 'Interface' word
He ends with a few names to avoid (like *Manager, *Helper or *Handler) to help prevent ambiguity. He reinforces providing meaning in your naming and making it easier for others to understand what's going on.
voice your opinion now!
classmanager naming opinion recommendation avoid meaning
Michael Kimsal:
Purpose of Benchmarking Framework Speed
by Chris Cornutt January 30, 2015 @ 09:53:57
In his new post Michael Kimsal shares some of his thoughts about framework benchmarking especially in the context of speed.
I've followed the techempower benchmarks, and every now and then I check out benchmarks of various projects (usually PHP) to see what the relative state of things are. Inevitably, someone points out that "these aren't testing anything 'real world' - they're useless!". Usually it's from someone who's favorite framework has 'lost'. I used to think along the same lines; namely that "hello world" benchmarks don't measure anything useful. I don't hold quite the same position anymore, and I'll explain why.
He goes on to talk about the purpose of using a framework and what kind of functionality they should provide. The usefulness of a framework is measured in what tools it provides and how easy it makes them to use. Benchmarks are only about speed, performance and overhead.
What those benchmark results are telling you is "this is about the fastest this framework's request cycle can be invoked while doing essentially nothing". [...] These benchmarks are largely about establishing that baseline expectation of performance. I'd say that they're not always necessarily presented that way, but this is largely the fault of the readers.
He refutes some of the common arguments about increasing performance of an application using a framework (like "just throw hardware at it"). He points out that, even with other improvements, it may come to a point where your framework of choice has become too slow and you need to move on. Think about maintainability too, though, and what you're switching from or to when considering making a move.
voice your opinion now!
benchmark framework speed purpose opinion feature maintainability scalability
Community News:
Packagist Latest Releases for 01.30.2015
by Chris Cornutt January 30, 2015 @ 08:08:07
Recent releases from the Packagist:
Three Devs & A Maybe Podcast:
Episode #56 The SOLID Podcast
by Chris Cornutt January 29, 2015 @ 12:20:03
In the latest show from the Three Devs & A Maybe podcast hosts Michael Budd, Fraser Hart, Lewis Cains and Edd Mann talk about a wide range of topics with a focus on the SOLID development principles.
This week we have a three developer podcast with discussion on a host of topics. We kick off with how Fraser has enjoyed building his first bonus slot game, written entirely in JavaScript and HTML5. Preprocessors are a huge part of the JavaScript ecosystem at this time, with so many to choose from we discuss a couple of the more popular ones. This leads on to Photoshop discussion, ReactJS, the cool features present in ES6 and how you can use them today with transpilers. Following this we move on to the SOLID principles, the overuse of inheritance, technical debt and the concept of Over-DRY vs. Software Value. This then takes us on to a strange 'rubber duck' example Edd conjured up to help try and explain the Liskov substitution and Interface segregation principles. Finally, we discuss Edd's media server setup and how he has got it to a staged that he is finally happy with it.
Other topics include things like:
You can listen to the latest show either through the in-page audio player or by downloading the mp3 of the episode. Also, be sure to subscribe to their feed of you enjoy the show!
voice your opinion now!
threedevsandamaybe podcast ep56 solid development principles
Community News:
Announcing the Pacific Northwest PHP Conference (Seattle, WA)
by Chris Cornutt January 29, 2015 @ 11:53:08
The Seattle PHP User Group has decided to follow along with the example set by many other PHP user groups in the past several years. They have officially announced the Pacific Northwest PHP Conference and a Kickstarter campaign to help raise the funding to help make it a reality.
The Seattle PHP User Group (SeaPHP) has been around for over 10 years. We love PHP, and we want to build up our local PHP community even further by hosting a PHP developer conference here in Seattle-the technology hub of the Pacific Northwest and cloud computing capital of the world. We invite PHP developers everywhere, and of all skill levels, to come learn, network, and hack together with us in the Emerald City at the first Pacific Northwest PHP Conference (PNWPHP).
The goal of the campaign is to raise some of the initial funding needed to generate more interest for the event, presell tickets and even attract sponsors. The conference itself is planned for September 11th and 12th of 2015 there in Seattle, Washington at the Impact Hub coworking space. If you'd like more information about the conference and updates as they come along, be sure to subscribe to their mailing list and consider helping the PHP conference community grow and contribute today!
voice your opinion now!
kickstarter campaign pacific northwest conference pnwphp15 contribute
Matthew Weier O'Phinney:
PSR-7 By Example
by Chris Cornutt January 29, 2015 @ 09:13:20
As a part of his involvement in the PHP-FIG standards group, Matthew Weier O'Phinney has been contributing to the PSR-7 proposal. This proposal defines a standardized structure for HTTP message handling. In his latest post he gets into a bit more detail on what this means for the PHP developer and how it might be implemented.
PSR-7 is shaping up nicely. I pushed some updates earlier this week, and we tagged 0.6.0 of the http-message package last week for implementors and potential users to start coding against. I'm still hearing some grumbles both of "simplify!" and "not far enough!" so I'm writing this posts to demonstrate usage of the currently published interfaces, and to illustrate both the ease of use and the completeness and robustness they offer.
He starts with a base definition of what the proposal, well, proposes around HTTP messaging, both the incoming and outgoing. He describes the basic structure of an HTTP message and what each part represents. He talks about message headers, bodies and how the current library could return that content. He then looks at requests vs responses, server-side requests and some various uses cases and more practical examples:
- HTTP Clients
- Middleware
- Frameworks
With the PSR-7 standard in place, all of these different tools could have interchangeable interfaces for HTTP request/responses, easily swappable with any other implementation.
voice your opinion now!
psr7 http message request response summary tool framework middleware client
|
Community Events
Don't see your event here?
Let us know!
|
