Doug Hatcher

Doug Hatcher

Enterprise architecture and tech junkie

Note

I agree with the sentiment that it’s your course to set and the major consideration is your own personal sanity. I will say, however, that if your project is used by many projects then one consideration should be their adoption strategy. Maybe it makes sense to find some usage stats, or maybe a survey, and figure out what versions of PHP your users are currently using and expect to use throughout the course of your roadmap. You may find you need to support lower versions, or that there’s enough appetite to keep things current that you can work towards bleeding edge support.

More generally, most libraries will work to not introduce breaking API changes and will just peg their latest versions to newer technologies, with the expectations that people can use an older version that satisfies the php requirements.

www.reddit.com/r/PHP/com…

Note

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.

www.reddit.com/r/PHP/com…

Note

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.

while you’re doing this, sort out a proper gitflow based continuous integration for testing, and continuous delivery with deployment automation. Also put everything your doing in the readmes! Learn markdown.

Finally, Google scrum ceremonies and begin to follow them. Learn planning poker, rely on your team, and the three stand up questions. Do all this, and you will be ok.

www.reddit.com/r/PHP/com…

Note

Open Source is a standalone product with its own community and roadmap geared towards small to medium sized businesses. Adobe supports and helps fund Magento, and will continue to do so. There willl always be the two products. Adobe wants the enterprise market for Adobe Commerce and thinks an open source base helps add value by building a bigger community and giving brands a path in And out of the enterprise licensing tier. As far as I can tell, Adobe Commerce and Magento will continue to drift apart and I suspect that eventually Adobe Commerce will shed its legacy PHP core as Adobe moves on to out of process extensibility principles and solutions like Edge Delivery and App Builder.

www.reddit.com/r/Magento…