People Hate Change, But It Is For The Best

It’s not “change” in the how, it’s the change in the principle of design I have an issue with. No more clean code. Now we have stuff all over the place in the database, and it’s not just content. Now we have design elements mixed in with content. That is not best practice, best design principle. Fine change things but keep the principle of simple 1st. Content separate from design code. Might as well go back to table design.

Visual Composer already offered the option of adding elements. I love change. This change happens to be legitimately bad.

That’s what’s wrong with software development these days, and hardware for that matter, forced adoption and change, whether necessary or not. Too many solutions to problems that DON’T really exist. The state of the code aside, if it was left as a plug-in, at least for the next 18 months or so, while it matures and gets to work properly, there would be NO real problem! From a professional standpoint, it’s almost unbelievable that WordPress felt it’s fine to force this on users, breaking so many templates and developed workflows. We already have page/visual builders, like Elementor, that are a hundred times better than Gutenberg, so quite off target I would say as an attempt to modernise and I’m sure there are other areas that should have had more priority – but everyone seems intent on dumbing down their products these days. Once you’ve experienced enough ‘change’ in a career, you soon recognise how much was ill-thought through and has wasted so much of your own time!