1243 1369 1780 1856 1723 1436 1539 1348 1544 1061 1918 1969 1414 1259 1123 1374 1835 1162 1838 1645 1846 1027 1736 1989 1397 1891 1707 1003 1002 1832 1096 1285 1917 1788 1174 1664 1678 1048 1962 1365 1414 1742 1190 1697 1539 1072 1125 1759 1668 1761 1802 1681 1391 1577 1955 1270 1957 1154 1451 1158 1016 1903 1721 1306 1329 1199 1145 1130 1109 1407 1346 1883 1064 1265 1765 1511 1228 1894 1060 1605 1797 1817 1362 1371 1481 1009 1081 1731 1970 1543 1437 1767 1595 1431 1869 1022 1905 1936 1540 Who uses PHP anyway? | PHPnews.io


Who uses PHP anyway?

Written by Colin DeCarlo / Original link on Sep. 9, 2017

Each Thursday at my office we hold a one hour ‘tech talk’ after lunch to discuss something technical of interest. These tech talks are pretty informal, it’s really just a bunch of us sitting around a projector talking shop with one person facilitating the conversation. I get a lot out of them and it’s one of the reasons I really value working at Vehikl.

This week we chose Object Calisthenics as our source material and we stepped through the list of heuristics discussing why the application of these rules tend to produce cleaner more maintainable code. Afterwards, one of our junior developers sent me a message in Slack with a screenshot from the post we were working through.

Read through the whole article this time on Object Calisthenics, and saw this… How do you feel when people say this about PHP? Is it because they’re not developing web applications? Just curious, and if you have nothing to say that’s okay too

It really kinda sucks that given the value the post delivers to its readers, this is the one thing that made enough of an impact that it caused the junior dev to ask me about it.

Here’s my reply.

People shitting on PHP isn’t going to go away, it’s a symptom of a few things.

PHP has a ridiculously flat learning curve so just about anyone can write code using it, this means a lot of amateurs and ‘get it done’ developers will choose php but won’t really ever level up their skills when it comes to software development.

PHP is ridiculously easy to deploy software with. This means that all those amateurs writing less than professional code can get their apps out into the real world. There are a lot of nasty people on the internet and these types of amateur applications are ripe for malicious attacks. This tends to give PHP a bad rap when it comes to building secure and robust applications.

Since PHP is easy to write and easy to deploy, a lot of people are trying to do that but they need help. They post to stack overflow or other message boards and other amateurs help them out with solutions that they’ve made themselves which is also amateur. So the shitty code propagates quickly and lots and lots of terrible examples are posted out there for everyone to see.

People are insecure assholes looking to make themselves feel better by shitting on people they don’t know because that’s easy and seemingly without repercussions. These are generally the same people who troll the internet wasting time and taking up space instead of building useful tools and generally being productive. Note that these trolls are shitting on people who actually are building useful tools and being productive, kinda ironic (if I know what irony means).

So how do I feel when people say shitty things about PHP? I can’t say that it doesn’t bother me because it does; it doesn’t make me angry though, it just makes me kinda sad. It makes me sad because they’re taking time out of their day to point out “if you’re doing X then you’re an idiot” and that isn’t helpful in anyway. In this particular instance, I don’t think that the author was trying to be malicious, it looks like the statement was made in jest, like they’re in on the joke that people shitting on PHP is a waste of time.

The key take away though is try not to identify yourself as any kind of X developer, PHP developer, Laravel developer, Symfony developer, JavaScript developer, Vue, React, Python whatever. All that does is create tribalism and pulls people further apart which is the opposite of what we should be striving towards. The product of software development is the same no matter what tools are used to make it, many of the core ideas and philosophies are applicable to all sorts of languages, so sharing this information across disciplines works to benefit the industry as a whole. If you silo yourself, you’re doing yourself a disservice and limiting your opportunities for growth.

Further, learning multiple different programming languages only makes you a better developer. While the core ideas and philosophies may be the same, the ways in which they are applied tend be slightly different because different languages have different language constructs. This is why developers will ask “whats the idiomatic way to do X in Y?”. Learning new languages will expose you to these “new” ways of accomplishing common tasks. You can take these experiences back to other languages and see how well they apply. It’s a win win.

calevans colindecarlo

« Lazy creative - A week of symfony #558 (4-10 September 2017) »