Why should developers ship features a bit slower as they take time to write tests? It’s simple. Tested code is good code. Start viewing testing practices as an investment instead of an expense to your business.
If you were running a retail store circa 2010, chances are you had an experience like many others at the time. The Web offered a new opportunity to expand your physical store, and Magento was the best solution for the job. So you found your platform, built your strategy, asked one of your trusted employees […]
We spend a considerable amount of time optimizing our infrastructure to make your Magento 2 store faster. After years of research and development, we’ve pulled together the ultimate 8-step Magento 2 performance checklist.
If you’ve never heard of auto scaling before you can think about it like an HOV lane on the highway. When Nexcess Auto Scaling is enabled, if our servers detect a surge of traffic, we’ll automatically open up an ‘HOV lane’ to manage the expanding traffic.
While you can find lots of content about unit testing PHP applications, there aren’t many people talking about unit testing specifically for WordPress. There is precious little written about where to start for developers that are ready to increase their code quality and want to learn how to add tests to their work.
Automating your WordPress deployment, and taking the time to get it right, means you never accidentally overwrite the wrong files, put the wrong files in the wrong directory, or make any other of the many mistakes I’ve made moving files around in the 12 years I’ve been building sites. A day or two of time spent configuring deployment for your first time is worth saving that pain.
Magecart attacks against Magento 1 stores won’t stop. The best kind of protection against external attacks is a mix of server side protection in the form of a WAF plus modules and patches to keep your store protected.