It’s hard to articulate just exactly why people should avoid Amasty but DRM is a pretty hard line you should never cross in a PHP project. It’s just not necessary, and it speaks volumes to their intent as Adobe and the broader community would come to their defense if their good work was actually stolen by other vendors.
www.reddit.com/r/Magento…
Doug Hatcher
Enterprise architecture and tech junkie
2024
I’m partial to devcontainers, personally.
www.reddit.com/r/PHP/com…
Honestly, just do your best and learn to be a good teammate. Languages come and go, and with ChatGPT you’ve got a buddy ever ready to answer questions. My advice is use it, don’t rely on its code but use it to grok and understand. The rest is being useful. Ask the dumb questions, because you’re not the only person wondering. Give practical commitment dates, over communicate and help those around you.
How big is the codebase? Obviously you’re facing a rewrite, but I would start by reviewing the logs and codebase, think deeply about how it should work, and isolate the current solution and mitigate the problems while you start building the correct solution.
You need to begin by getting your arms around the biggest problems and begin to address them this week. Start by installing new relic, tackle problems with zeal, and do it first on a staging environment with plenty of testing so you’re not introducing more problems.
From Setup to Success: How to leverage payments to enhance the Adobe Commerce journey
Blue Acorn iCi’s Doug Hatcher teams up with Adobe’s Nitu Walker to guide you through setting up and onboarding Payment Services on Adobe Commerce. They’ll cover practical use cases and highlight the out-of-the-box features that can elevate your experience.