ModernizingPHP's profile picture. Ridding the world of spaghetti PHP code one application at a time.  Posts by @SarahSavagePHP. Find me at https://phpc.social/@modernizingphp

Modernizing PHP

@ModernizingPHP

Ridding the world of spaghetti PHP code one application at a time. Posts by @SarahSavagePHP. Find me at https://phpc.social/@modernizingphp

Modernizing PHP أعاد

It's hard to believe I'm back here, but there's too many important conversations to have and too many things going on to miss out. Planning to post about #WordPress, #php, and community.


Work continues on the mirror for #WP .org. We’ve created a Slack channel and a subreddit. Check out Reddit.com/r/aspirepress to follow along. This will be my last update from this account; all others will come from @AspirePressOrg Please follow that account #Wordpress #wpdrama


I wrote something updating the world on the WP .org "single-point-of-failure" repo replacement effort: reddit.com/r/Wordpress/co… #wordpress #wp #wpengine


Modernizing PHP أعاد

Many people were waiting for WP Engine to say our side. Here is the 12-part complaint. Judge for yourself.

Matt Mullenweg and Automattic’s self-proclaimed scorched earth campaign against WP Engine has harmed not just our company, but the entire WordPress ecosystem. The symbiotic relationship between WordPress, its community and the businesses that invest millions to support WordPress…



There is a proposal on Reddit for the #wordpress community to provide a mirror of the asset repos and give back to the Foundation as well. It’s here: reddit.com/r/Wordpress/s/… The proposal needs @photomatt to bless it, since it requires some use of the original repo.


The worst time to discover your application is horribly out of date is when it breaks and your clients flee to competitors.


You cannot rewrite a piece of software and add new features at the same time. You CAN refactor a piece of software and add new features at the same time. This is why refactoring beats rewriting almost every time.


Each week I share a short, immediately actionable tip for improving your applications. Get your copy by signing up today buff.ly/3nH3WEQ


Whether you use the newest features or not, being on the latest version of your language is crucial to ensuring your software is secure.


The beauty of CI/CD is that you're always ready to ship. The beauty of having a solid test suite is that you always know if shipping will break anything.


Tomorrow, and every Thursday, I share a short (100 words) tip on modernizing applications. Want it? Sign up here: buff.ly/3nH3WEQ


Show me a developer that's afraid to deploy on Friday's and I'll show you the deficiency in test coverage.


Developing good software is important. Developing good software that meets the needs of the business is more important.


Established companies should employ a Chief Quality Officer. Their purview should be user-facing bugs and performance issues caused by low quality code. Their focus should be getting quality improvements into software that directly impact user experience.


Modernizing PHP applications is about more than the code. It’s about practices, too, like testing, TDD, CI/CD, and more.


Why do I push good code so hard? After all, isn’t working code the main goal? It is. But working code has limits if it’s designed badly. Good code is easier to maintain - something you’ll do a lot of - and gives you more flexibility in the future.


You can write great code in any framework. You can write terrible code in any framework. The quality of your code has more to do with your emphasis on quality than the framework.


Loading...

Something went wrong.


Something went wrong.