News Feed
Sections




News Archive
feed this:

Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Mathias Verraes:
DRY is about Knowledge
August 04, 2014 @ 10:51:50

In this new post to his site Mathias Verraes approaches the concept of the DRY principle (Don't Repeat Yourself) as being more about knowledge. He includes two "real world" examples where the business rules can change around you.

"Don't Repeat Yourself" was never about code. It's about knowledge. It's about cohesion. If two pieces of code represent the exact same knowledge, they will always change together. Having to change them both is risky: you might forget one of them. On the other hand, if two identical pieces of code represent different knowledge, they will change independently. De-duplicating them introduces risk, because changing the knowledge for one object, might accidentally change it for the other object.

In his examples, he shows how hard-coded rules (like "a product container can only contain 3 products") could just be around certain needs, not the entire range of requests. He covers some of the principles of Domain-Driven Design and how they apply here, pointing out that changing rules in one part of the application can have an effect on other parts depending on it.

0 comments voice your opinion now!
dry dontrepeatyourself principle knowledge domaindriven design business goal

Link: http://verraes.net/2014/08/dry-is-about-knowledge/

Brandon Savage:
Languages Don't Matter (Part Deux)
January 16, 2013 @ 11:54:29

In a follow-up to his previous article about why languages don't matter, Brandon Savage has a new post (part two) carrying on the theme but getting more into the thought patterns behind language selection and use.

Developers like to think that companies hire developers to write code. But companies do not hire developers to write code; they hire developers to solve problems. They hire developers with the expectation that the developer knows about, or can learn about, the problems of the company, and find a creative solution to those problems at minimal cost.

It is therefore up to the developer to choose what tools they will use to achieve the outcome. The customer doesn't much care what tools the developer uses; they only care that the outcome they desired is achieved.

He goes on to talk about preferences in the tools "used by craftsmen" and why they're less important than the result of the work they create. He notes that languages matter, but only in a certain context - as a piece of a puzzle, a part of a whole to reach an objective of functioning software.

0 comments voice your opinion now!
language opinion choice tool goal software development


Travis Swicegood's Blog:
My goals for the PHP standards group
June 04, 2009 @ 08:44:26

Travis Swicegood, a member of the Standards Group that has formed in the PHP community, has posted some of his own thoughts about the group and what kinds of goals he sees it having.

A few weeks ago at php|tek, I corralled developers from all of the major PHP frameworks into one of the conferences rooms. The idea was simple: in the PEAR Group we've been discussing our new PEAR2 Coding Standard and have come to some conclusions on how PHP 5.3 code should be handled moving forward. A standard is only a standard if people use it, though, and PEAR is not entirely representative of the community at large. That's where this group comes in.

He mentions resolving namespacing issues around naming structures, classes/interfaces/abstracts and for Exceptions. He also sums up his thoughts on the openness of the group well:

I'd love to see an officially sanctioned standard come out of our work. All of us are too busy, both with real jobs and our various projects, to fight the battles that come of trying to make this a completely open process where anyone with an email address can contribute. Sad as it may be, pear-dev has demonstrated that coding standards *must* go the way of sausages and laws lest they devolve into a constant "but I think is better, and this is why..." followed by pages of well meaning, but generally irrelevant content.
0 comments voice your opinion now!
goal group standards


PHPBuilder.com:
Beginning PHP One Goal at a Time
September 01, 2006 @ 03:46:29

Though it contains no code, this new article on PHPBuilder provides a good perspective for those looking to get into PHP and what to expect to find.

A couple of months ago, I knew almost nothing about PHP, only that is was a programming language that I needed to learn. Today, my whole site relies upon PHP and I have gained the confidence that almost anything is possible using PHP. I accomplished this achievement using methods that I will describe in this article.

The author talks about the methods followed to get into the language, including making smaller goals at first, just to get used to things. The manual is also suggested as a "best friend" for a developer and looking at other people's code can provide insight into your problems.

0 comments voice your opinion now!
beginning tutorial goal introduction beginning tutorial goal introduction



Community Events





Don't see your event here?
Let us know!


api unittest bugfix deployment package install community podcast release framework language series library interview zendserver symfony introduction opinion voicesoftheelephpant laravel

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework