One-click experts: When basic knowledge is missing

This morning I opened my email client and found a newsletter from a web designer. I usually enjoy reading her tips - she often shares interesting insights from her day-to-day work. But this newsletter made me smile and shake my head at the same time.

She happily reported on her change of hoster. The reason? The automatic WordPress installation was no longer working properly. Instead of solving the problem, she switched providers. With practical affiliate links, of course - to both the old and the new host. Better safe than sorry, right?

I had to think back to my early days. There were no one-click installations back then. You upload the files, create a database, adjust the configuration - done. Today, that seems to be rocket science for some colleagues.

But it's like driving a car: You don't need to know how an engine works, but refueling and checking the oil level are part of it. Anyone who sells WordPress projects should be able to install the system without a click wizard.

What happens if real problems occur later? Database errors, plugin conflicts, faulty updates - should the hoster then also be changed? Or is the problem passed on to the next service provider?

I am not only observing this development with WordPress. In the TYPO3 world, I also encounter "experts" who can configure extensions perfectly, but who have to make individual adjustments. That's perfectly fine - as long as you're honest about it.

It becomes problematic when basic knowledge is missing, which is part of the tools of the trade. If you call yourself a professional, you should know the basics of your system. Anything else is like a chef who can only heat up ready meals.

Of course there are specializations. Not every designer has to be a developer. But there's a huge difference between "I'm not a programmer" and "I can't install my CMS".

Maybe I'm old-fashioned, but I think that anyone who advises clients and implements their projects bears responsibility. This responsibility starts with a solid basic knowledge of your own tool.

Sending out the newsletter publicly was brave, by the way. I value transparency - even if it sometimes unintentionally reveals more than planned.

How do you see it? What basic knowledge do you think web professionals should have? Share your experiences in the comments!