Well, yesterday my coworker had the issue that CentOS 7 was in a reboot loop after installing upgrades, which was a systemd issue to start with, And the logging of systemd didn't really help to debug it. coworker googled some recipe which consisted of a bunch of sysctls which neither of us understood. Fixed the issue (for now). Feels like Windows...
And this is exactly what I predicted: Systemd will have weird issues, and since no one understands its complexity, no one will be able to fix it. If you're lucky, you'll be able to google the solution. Reinstall will be the standard Linux fix soon.
Notice how simplicity is design goal number 1.
If you really believe this you should take less.
If you intend to remain (a paid) Linux sysadmin in the future now where all major distro are starting to convert to systemd, you should really study systemd's journal.
And this is why every sysadmin hates your cabal: It feels like the evil empire taking over. "Don't resist, and it will hurt less."
But we will resist. Go to hell.