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

VitalFlux.com:
Top 10 PHP Code Review Tips
September 10, 2014 @ 11:15:31

On the VitalFlux site there's a recent post sharing a few tips (a Top 10 list) of things to think about when doing code reviews.

This article represents top 10 areas to consider while you are taking up the task to do the code review of a PHP project. The other day, I had a discussion with one of the PHP senior developers who asked me about where to start on the task related with reviewing a PHP web application and, we brainstormed and came up with the list. Interestingly, apart from few, most of them can be pretty much applied to applications written with other programming languages as well.

Their top ten list of things to look for during code reviews extend beyond just the syntax of the code and good coding practices. They also suggest things like:

  • Adherence to Business Functionality
  • Object-Oriented Principles
  • Security
  • Integration Patterns/Protocols

Code reviews, if done effectively and efficiently, can be a major benefit for producing quality code that not only adheres to standards but also follows good practices and principles (like SOLID).

0 comments voice your opinion now!
code review tips top10 list syntax bestpractice business

Link: http://vitalflux.com/top-10-php-code-review-tips/

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/

php[architect]:
July 2014 Issue Released - Navigating the Business
July 22, 2014 @ 10:52:17

The July 2014 edition of php[architect] has officially been published - "Navigating the Business". Articles in this edition include:

  • "Resume 101" by Jordan Tway
  • "Startups and PHP" by Benjamin Greenaway
  • "Hexagonal Architecture with PHP" by Carlos Buenosvinos
  • "The Confident Coder: Sanity Check: Insane Value!" by Aaron Saray

All of the usual columns are also included as well as an "Archie's Adventures" section about the travels of the php[architect] orange elePHPant. You can pick up a (digital) copy of this month's issue directly from the site or get a year's subscription to get more great content delivered each month.

0 comments voice your opinion now!
phparchitect july2014 issue release navigating business magazine

Link: http://www.phparch.com/magazine/2014-2/july/

PHPMaster.com:
6 Extra Skills Every PHP Developer Should Have
April 09, 2012 @ 08:22:01

On PHPMaster.com today there's a new article with six things that they (well, Daniela Baker) thinks every independent PHP developer should know and have in their arsenal.

PHP development is hot right now, but there are also lots of people in PHP development. If you want to make it as an independent PHP developer you've got to know more than just PHP. Here are six other essential skills you need to succeed as a PHP developer.

Her list of six is made up of:

  • JavaScript, HTML, and CSS
  • Knowing What You Don't Know
  • Business Communication
  • Business Finance
  • Project Management
  • Networking

Really, independent or not, these types of skills/knowledge can help any developer out there to see the bigger picture outside of just their code, out to what the business is doing.

0 comments voice your opinion now!
skills opinion developer technical business knowledge


ThinkPHP Blog:
Benchmarking & optimizing real-world scenarios in a business context
June 18, 2010 @ 09:14:35

On the ThinkPHP blog today there's a new article looking at some of the best practices they seen when it comes to profiling and benchmarking your PHP-based applications.

Over the years, PHP has evolved from a script language to a programming language used in big applications with high-level architectures. As the most popular language for web applications, PHP is very fast, robust and stable by default. Coming from tiny scripts, PHP is used in large-scale web applications nowadays. In terms of business context, we need to focus on these three key factors: Scalability, Responsiveness and Resource misusage. All three factors have a high impact on hardware costs, customer loyalty and - indirectly - sales.

They mention a few ways that you can use to optimize your application's code including evaluating resource limitations, Firebug caching results and finding bottlenecks with something like XDebug.

0 comments voice your opinion now!
profiling benchmarking optimizing business


ThinkPHP Blog:
Study about relevance of business goals in PHP software architecture
May 28, 2010 @ 09:12:45

On the ThinkPHP blog there's a quick note about a study they've done on the relevance of business goals in the architecture of PHP applications.

PHP software developers and system integrators actually play an important role in running the world's largest web infrastructures. From Facebook, Gruner & Jahr, Kabel Deutschland and Lufthansa to a diversity of corporations, they all trust PHP and the respective systems built with it. It is not questionable that these systems provide a solid software architecture. The point of interest is how these architectures are aligned to the fast pace of changing business goals, which categories of business goals are considered during architecture creation and which means are utilised in projects.

The study (a 24-page study, in English) looks at some of the current strategies businesses are using in their application development, how to consider the right business goals and putting an emphasis on quality and capability of your organization. The study is free, but you'll need to register to get a copy emailed to you.

0 comments voice your opinion now!
study software architecture business goals


php|architect:
5 meta-skills for the PHP developer
February 23, 2010 @ 14:13:38

In a recent post to the php|architect site Marco Tabini has a suggestion of five meta-skills he thinks every PHP developer should learn.

But being a PHP developer is much more than writing PHP code. In fact, good PHP skills would be something that I would take for granted that every PHP developer should have'"and, if enough employers are as crazy as I am, there's a chance that I'm not the only one who wants to look beyond mere PHP to decide who is good and who is exceptional.

His list five of meta-skills for the PHP developer covers a wide range of things, not just involving the technology of web development:

  • HTML, CSS and JavaScript
  • Understanding business
  • Coming to grips with reality
  • Using the phone
  • Being humble
1 comment voice your opinion now!
opinion skill technology business phone humility


O'Reilly Radar:
What Facebook's HipHop means for developers and businesses
February 05, 2010 @ 13:17:16

In a recent interview posted on the O'Reilly Radar site, Msc Slocum talks with Kevin Tatroe about what Facebook's HipHop means for business.

Facebook's PHP overhaul, HipHop, reportedly cut CPU usage on the company's servers by around 50 percent. You don't have to be a programmer to understand that kind of result. [...] asked Kevin Tatroe, co-author of O'Reilly's Programming PHP, to weigh in on HipHop's functionality and its broader applications.

Mac starts with some basic questions - how will it help developers, how will it help businesses - and then asks for some clarification as to what the project really is and how difficult Kevin thinks it will be for companies to adopt.

0 comments voice your opinion now!
facebook hiphop business developer interview kevintatroe


Brandon Savage's Blog:
Peer Review Improving The Business Logic
September 08, 2009 @ 10:04:07

Brandon Savage has posted the fifth part of his "Peer Review" series where he's taken a sample application and worked it over - refactoring, updated to meeting coding standards and abstracting out interfaces to simplify the code. In this latest article he looks at a method to improve the business logic behind the scenes.

So far, we've done quite a bit of work on our Twitter class, making it better. There's still work to be done, though, especially improving the logic. The Twitter class we have now has a number of logical flaws in it that we need to address. Additionally, there are some logical flaws that we started with that I want to highlight, even though we've already fixed them. Let's get started with those.

He looks at a few things like setting the host name as a property, using the return of the HTTP request and handling exceptions (like when Twitter's down). The resulting code is included.

0 comments voice your opinion now!
peer review business logic


Jim Plush's Blog:
Rethinking the Zend Models
July 15, 2009 @ 12:35:16

Jim Plush has taken a look at his models in the Zend Framework and has rethought them a bit to work with a bit more complex process than the usual simple sort of Zend Framework application.

The current active record/table gateway patterns just aren't going to cut it for the complex business logic that's approaching. I'm starting to lean towards the domain model approach which would increase the initial complexity of the design but allow for the flexibility for future changes and features. The issue is with where to put your business logic?

He diagrams out his potential solution and includes two bits of code showing how it would work in practice. He's soliciting opinions as to the validity of this approach too, wondering if its the best way to go for more complex application structures requiring these sorts of business requirements.

0 comments voice your opinion now!
logic business complex model zendframework



Community Events





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


zendserver tips install library community update laravel release framework api introduction list series symfony interview podcast opinion deployment language package

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