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

Reddit.com:
What constitutes the "PHP community"?
July 18, 2014 @ 12:09:37

There's a good conversation happening over on Reddit today about what constitutes the "PHP community" and how it can be defined. JordanLeDoux wonders if those who just write PHP are included in that group as well.

One conversation was with a dev who hates PHP because (mostly) they work with code that was written by some non-PHP dev who was asked to write it. The other was with /u/krakjoe from the PHP internals team, where I was commenting on a sentiment that sometimes finds its way into the internals mailing list: if you want a real programming language, then go use one. In both cases, I made the assertion that most people who utilize PHP or edit a script aren't actually part of the PHP community. [...] How can someone that is functionally isolated from any other person working in PHP be part of the PHP community?

Responses to the post are, for the most part, encouraging suggesting that

  • There's not a single "PHP community" but many smaller ones
  • sub-communitiies can revolve around technology or a product
  • The different definitions of community
  • The broad range of skills that "PHP developers" are known to have

Check out the full post for more opinions and share your own!

0 comments voice your opinion now!
community opinion developer

Link: http://www.reddit.com/r/PHP/comments/2ayxkg/what_constitutes_the_php_community/

Dominic Tancredi:
PHP is a dying language - A Rebuttal
June 24, 2014 @ 09:47:14

In a recent post to his site Dominic Tancredi has posted some of his own opinions about the PHP language, a rebuttal to all of those who say that PHP is dying.

A junior programmer with a master's asked me, "Is PHP a dying language being taken over by trending technologies like Ruby on Rails?" Here are my thoughts. Order. It all comes down to order. Order is what defines us, clarifies ideas. Order allows us to get to market quicker, safer, and less defects. Order is a pristine engine that is maintainable, scalable and extendable.

He talks about the evolution of web development language over the years: how Ruby on Rails was the "next big thing" for a while and how PHP, despite starting from a small community grew into something a bit haphazard and crazy. Out of that craziness, though, came what he calls the "PHP Renaissance", a time when PHP is gaining order, standards are being defined and good practices are winning over the old ways. He mentions some adoption numbers and reinforces a suggestion from Phil Sturgeon that we all need to act more like a community and less like a tribe (or a set of tribes, centered around tools or techniques).

0 comments voice your opinion now!
dying language rebuttal opinion community

Link: http://dominic-tancredi.com/posts/php-is-a-dying-language-a-rebuttal

Reddit.com:
PHP devs -What are your 'must have' tools and apps?
June 23, 2014 @ 12:54:45

If you're a PHP developer and are looking for some new tools to "up your game" and improve your development life, check out this new post to /r/php on Reddit.com. Developers of all kinds have shared tools they've found useful in their own development (and maybe you can too).

In other words, what tools make your development life easier and why? Can be anything from database design to FTP clients to workflow planners. Which tools can you just not live without?

Among the many tools on the list are things like:

  • PHP CodeSniffer
  • PHPUnit
  • IDEs like PHPStorm, Netbeans and editors like Sublime Text
  • Git
  • Composer
  • Vagrant/VirtualBox
  • Xdebug
  • Redis
  • Behat

Check out the full post for the complete (and growing) list.

0 comments voice your opinion now!
musthave tools applications opinion reddit

Link: http://www.reddit.com/r/PHP/comments/28r11n/php_devs_what_are_your_must_have_tools_and_apps/

Codeacy Blog:
Your Greatest Code Quality Threats and How to Solve Them
June 23, 2014 @ 09:22:42

On the Codacy blog there's a recent post that looks at some of the biggest threats to code quality (six of them) and some brief advice on how you can prevent them. Code quality goes beyond just style guides and common coding practices too.

In the process of building Codacy, I've learned that software companies in different life stages have different needs in terms of code quality. Early startups have, for example, very different needs in comparison to digital agencies and freelancers. There is however a common ground that links them all together: code quality is not being taken seriously enough, regardless of the stage. If this resonates with you, take action today. Continuous improvement is the central piece of software engineering craft.

Among the six things in their list are suggestions like:

  • Using continuous integration
  • Living with broken windows
  • Heterogeneity (code styles)
  • Not using static code analysis

They also link to some tools that can help fix some of these suggestions including JSHint, some PHP static analysis tools and CSSLint for CSS.

0 comments voice your opinion now!
code quality threat suggestion opinion tools solve

Link: http://blog.codacy.com/2014/06/19/your-greatest-code-quality-threats-and-how-to-solve-them/

Reddit.com:
What exactly is 'model' in MVC?
June 20, 2014 @ 11:25:48

If you're relatively new to the world of the MVC (Model-View-Controller) design pattern and its use, you may be trying to figure out exactly what each piece is. One of the more difficult relationships is between models and controllers, more specifically what each are supposed to contain. In this discussion over on Reddit several people weigh in on their opinions and own suggestions about what models should be.

Sometimes I feel I should avoid session in model ... but sometimes I feel using session in controller is putting business logic in controller which is bad ... sometimes I feel I should avoid $_POST and $_GET in model ... but sometimes I feel receiving data in controller and then send all of them to model is an unnecessary move ... sometimes I feel one model should represent almost everything about one certain table ... sometimes I feel it's almost god pattern if that table is the core of your application, but separate the model into many model is confusing too since they are using the same table. I wanna be a Model Master who can explain 'Model' very well. Who can help me plz.

Comments on the post explain models in several different ways including:

  • Thinking of it as a representation of "domain" functionality
  • Models as a 1-to-1 relationship with database tables
  • The differences between them and collections
  • Links to some helpful libraries like Eloquent and Doctrine
0 comments voice your opinion now!
model mvc modelviewcontroller opinion definition

Link: http://www.reddit.com/r/PHP/comments/28luto/what_exactly_is_model_in_mvc/

Grant Lovell:
Why PHP doesn't suck anymore
June 17, 2014 @ 09:04:07

In a recent post Grant Lovell shares some of the reasons why he thinks PHP doesn't suck anymore based on his presentation from the Waterloo-Wellinton Webmakers.

Chances are if you have been in web development for any amount of time you have done some work with PHP and maybe it was a great experience like it was for me, or perhaps it was hours and hours of digging through WordPress code to figure out why a plugin wasn't working. [...] A friend from U of W was giving me a hand setting up the catalog and introduced me to PHP. He was able to build the whole catalog, at least a basic first version, in one afternoon. You can imagine I was pretty excited about something that I thought was going to be weeks of cutting and pasting being done in a few short lines of PHP code. From then I was hooked.

He looks at a brief history of PHP, from its beginnings as a set of simple scripts by Rasmus Lerdorf out to the current push and support of the language by big companies like Facebook. Despite all of this, he points out that PHP "went wrong" somewhere along the way thanks to things like bad tutorials and practices. He talks about the GoPHP5 initiative and some of the signs of improvement in PHP: frameworks, Composer, the FIG and the "PHP renaissance." He looks into the future and sees only improvement thanks to better tutorial content (on various sites) and the increased amount of cooperation between developers wanting to make the language better.

0 comments voice your opinion now!
opinion suck language history improvement future

Link: http://transmission.vehikl.com/why-php-doesnt-suck-anymore/

Mathias Verraes:
When to Use Static Methods
June 16, 2014 @ 10:20:52

Mathias Verraes has followed up his previous post about named constructors in PHP with a bit more clarification about when to use static methods (as he did in his "multiple constructor" examples previously).

Some of the reactions to my last blog post on Named Constructors in PHP, originate from the notion that static methods are inherently bad and should never be used. This is rather overgeneralized. Static methods are nothing more than namespaced global functions. Namespacing, I think we can all agree on, is great. As for global functions: We use those all the time. The native functions in PHP form our basic building blocks.

He talks about the main problem with their use, the shared global state, and compares it to a more stateful service. His solution is to either move to a normal object state (that allows for internal tracking) or think more about abstractions and how they relate.

0 comments voice your opinion now!
static methods opinion object stateless abstraction

Link: http://verraes.net/2014/06/when-to-use-static-methods-in-php/

Snipe.net:
Why You Should Stop Stalling and Start Presenting
June 13, 2014 @ 11:47:01

In her latest post Snipe does her best to motivate those out there that have thought about speaking or presenting at a technology conference but are "stalling" and finding excuses not to. The post pulls from some of her own past experiences as a speaker in various communities, PHP and otherwise.

My last post generated a bit of buzz when it was posted to HackerNews recently, so I figured I'd take this opportunity to reiterate something I've been saying on Twitter for a while now. If you have never presented a conference before, make this the year you change that.

She breaks the rest of the post up into different reasons to stop making excuses and just do it:

  • It is an incredible experience that makes you better at other things
  • You will meet great people and learn about their experiences
  • Even if you suck the first time, it really is okay, even if it doesn't feel like it at the time
  • It's great for your career
  • If you are part of an underrepresented minority, your peers need to see you on that stage
  • Your audience is actually far more forgiving than you imagine
  • You're smarter than you think. Things that are obvious to you are not obvious to everyone else
  • It feels really fucking awesome talking about stuff you care about

She also shares a few panic-aversion tactics she's worked up over the years including starting small, working with "power poses" and a reminder to use the "presenter view" feature in your presentation software of choice.

0 comments voice your opinion now!
presentation conference speaking experience opinion recommendation

Link: http://www.snipe.net/2014/06/why-you-should-stop-stalling-and-start-presenting/

PHPClasses.org:
7 Reasons Why TDD Failed to become Mainstream
June 11, 2014 @ 09:44:39

In the latest PHPClasses.org post Manuel Lemos suggests severn reasons why TDD failed to become mainstream in most development communities. This is related to comments from an leader in another community about his perspective on the "TDD movement".

Recently the creator of Ruby On Rails declared that TDD (Test Driven Development) is dead. Despite he used to be a supporter of TDD as the right way to do software development, he finally decided to announce that he really does not agree that TDD is really the right way. Read this article to learn more about what happened and what does this mean for developers that support TDD or not.

He starts with a brief look at what TDD (test-driven development) is and a link to a ThoughtWorks video of DHH talking about his new stance. Among his reasons are things like:

  • TDD is Expensive
  • You Will Change Your Projects and Old Tests Become Waste
  • Extensive Testing is Boring
  • Many TDD Preachers Do Not Use it Most of the Time But Do Not Admit it

Manuel shares some of his own opinions on the matter, though, pointing out that he doesn't think TDD is dead. He suggests that it helps to "make you rethink" when developing and that your (and your development group's) practices shouldn't be influenced by outside opinions - use what works.

0 comments voice your opinion now!
tdd fail mainstream opinion dhh video introduction

Link: http://www.phpclasses.org/blog/post/237-7-Reasons-Why-TDD-Failed-to-become-Mainstream.html

Dawn Casey:
Things Developers Say
June 05, 2014 @ 09:13:45

In this new post from Dawn Casey (wife of the infamous Keith Casey) she talks about some of her "growing pains" around becoming a new developer and the learning process. She's come up against some interesting problems in the course of her learning, both good and frustrating.

In the course of my learning development (seven months at this point) I've heard quite a few things from other veteran developers, all of whom were trying to be helpful. Or I'd ask a question and get one of these things in response because it makes sense to *them*…they don't realize I have no point of reference. [...] I'm frustrated because they can't explain whatever it is I don't understand..mostly because I don't understand exactly what it is I'm not understanding.

Her frustration comes not only from not being able to ask the right questions, but also from being a "blind deaf alien" thrown into the world of development. She point out an issue common to those trying to get into programming: the wealth of information one needs to know before getting started. She also mentions another common problem, particularly for new developers (or those looking to improve one certain skill): the sometimes unhelpful nature of other, more experienced developers. While some are happy to help and guide you through the learning process, there's others that will just toss you a tutorial link and call it a day.

Here's the gist of what I'm saying: There is so much back-knowledge needed to be a web developer today that many are derailed for months trying to learn everything they need to know before they can learn anything at all. PLEASE REMEMBER THIS!!
0 comments voice your opinion now!
developer beginner experience opinion help learning

Link: http://sdawncasey.wordpress.com/2014/06/04/things-developers-say/


Community Events





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


interview install series code testing developer threedevsandamaybe framework release podcast language laravel introduction refactor configure opinion wordpress unittest list community

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