Slideshare slides: Pay No Attention To The Project Manager Behind The Curtain
Presentation by Joshua Warren and David Deppner at Meet Magento New York 2016.
This presentation discusses the early days of Magento 2 in the context of a real project, focusing on Merchant/Development Agency relation...
Presented by David Deppner at MagentoLive UK, London, June 20, 2016
This presentation offers a business perspective on managing your Magento 2 upgrade project, and when to get started (spoiler alert: start now!). I speak from a merchant point of view to illustrate why you may want to move to Magen...
I recently got started with some work integrating some older systems with Magento 2 using their new REST API. Right at the top of the Getting Started with Magento 2 APIs Introduction there's a list of features, including this one:
- The framework supports field filtering of web api responses to conserve mobile bandwidth.
That sounds nice. Let's get some of those responses down to just the fields we need, and speed up the data transfer just a bit!
Ecommerce merchants are usually very quiet about their servers getting hacked. Obviously, they face some serious legal liabilities in situations like this, and the potential for lost sales if their customers lose faith in them. This may be good for business on the one hand, but it’s really bad for business on the other. Sharing security information with people who need it helps us all. We just faced a hack that didn't impact our business in any way, so I want to share it to help other people. I hope it's useful to other merchants.
I’m working on our Magento 2 upgrade right now, two months before its release. Why am I so bullish, when so many other merchants and agencies are taking a “wait and see” approach? Risk and return. It’s that simple.
Anyone who’s lived through as many painful upgrades as I have is nervous about change. When your business depends on an operating system or software platform, you never rush to upgrade. The initial version will be buggy. Once you upgrade, it’s hard to roll back. You don’t know what the new version is really like before it’s released. So you wait until the release. Then you check it out. And you wait. You wait for all the idiots who rush in to find the bugs. You wait for the company to issue patches. Then you start to plan an upgrade. You roll out slowly. No rush. Why break what’s working?