It was ok, just the power cord and a fee RJ45 torn. No serious damage besides downtime.
Build yourself a home lab and learn how systems work. Figure out what is really running your code. Learn how to resource optimize.
Don't end up only being able to work on webapps and small datasets that fit comfortably in the cloud.
5 years ago I left a company running loads of enterprise software and web applications for other companies in a couple of data centers. We had well over 10.000 physical machines. When I left, about 90% of the workloads were virtualized. Running on bare metal is the exception today.
Sure, its cool to have hot-swap HDDs, hot-swap PSUs, redundant network cards and a remote management board but none of that is rocket science. You can learn it in a week if needed.
Networking is a much deeper topic yet almost nobody would recommend you to set up a couple of switches and hardware firewalls in your home network. Today you expect that the hardware just works. In the real world it is extremely complicated to correctly design and run networks, but you aren't going to experience any of these problems in a home lab.
At the end of the day, you need the guy who makes it "just work". That is a valuable skill as well.
Also knowing how your application works when you just yank the power cord on half your VMs teaches you a ton.