Worked for a large corporation that is now widely considered a very scummy printer manufacturer. For whatever reason there was an issue no-one could figure out

Worked for a large corporation that is now widely considered a very scummy printer manufacturer. For whatever reason there was an issue no-one could figure out where if either of two networked computers, attached to printers, couldn't communicate (e.g. ping each other) then the printing from the local machine itself would stop working. I wrote a small Erlang application which would monitor an Erlang pid on the other computer and restart the network interface in case it ever lost contact, which generally made things work again. Obviously many ways to solve (such as figuring out why it behaved like that in the first place!!) but I was learning Erlang at the time and it seemed a neat way to do it.