Pet Peeves, Part 1:
- not writing any log messages
- almost as bad: writing log messages without timestamps
- a server application that picks a different TCP port every time I restart the application, and my 30+ users all had to update their client software configuration with the new port (reboot would start at the same initial port, so I rebooted it a lot)

The last two happened to me years ago when testing network management software from Alcatel called OmniVista. (I had feedback.)

Pet Peeves, Part 2 (aka today):
- changing interface names after I got new server up-and-running, and tested it with a reboot to be sure

Is this because I ran updates and rebooted again?

Thank you, remote console. Eff you, whatever mechanism changed interface names from em[1-4] to eno[1-4].

THIS IS A SERVER! Server network configuration SHOULD NOT CHANGE after I configure, test, reboot, and test again. Not application TCP ports, and not interface names.

That is all.

@nethope good ole systemd fucking shit up again