For those of us who have chosen to work in the tech world change is constantly with us: it may well be daunting sometimes, but then again - without it we would sometimes even be out of a job. But the same change that sometimes has us uneasy as to having learn something all the time can also be our friend, it can be what makes a developers life easier and more productive. And it can have the same effect in the sysadmin-area.
Just ten years ago the way we worked in the php-world was quite different from today: servers for production or development use where manuelly provisioned by as sysadmin who thus was also desponsible for - manually - creating the same setup on a number of servers and to do that with consistency. Developers would then push their code onto the server via FTP and use something like phpMyAdmin to set up the Database. At least that was the way it worked most of the time. Don't get me wrong, I'm running this very site on a server I also use for shared hosting purposes, and in that field - like quite a bunch of others - a lot of this is still valid. But nonetheless: Things have changed, even if you are like me - quite weary of always running after the newest trend that is.
Working with more and more complex projects does ever more show the boundries of something like FTP deploys, after all who likes to search for that one missing file that somehow didn't make onto the server, allthewhile knowing there are a lot of users getting a code 500 while that file needs to go up there. But even besides such things as different ways to deploy things onto servers, tools like (link: https://www.bugsnag.com/ text: Bugsnagg) or (link: https://www.honeybadger.io/ text: Honeybadger) enable us to actually know that these errors to occur. That is also new - unless you where into building elaborate things out of log-analytics yourself before.
So I guess what all my rambling comes down to is that these are in fact exciting times.