5 ms·

> Running old code for an old service that no one remembers or use any longer... which is why every two years, I switch the servers completely to fresh new mac

> Running old code for an old service that no one remembers or use any longer... which is why every two years, I switch the servers completely to fresh new machines, installing everything anew. Let those old things that we installed for who-knows-why die off.

patates 6y ago
People (well, me too) these days script that too, so the good thing is you don't forget a service or configuration, the bad thing is you never forget a service or configuration.
Cthulhu_ 6y ago
This is I think a problem in pretty much all of IT; people install a system and forget about it. What 'people' (sysadmins?) SHOULD do is create a maintenance schedule / contract at the same time, and make sure that it is transferred to the next guy in case of moving on in a job / position. Doing what I can, I make a point of having a calendar reminder to update my software's dependencies every month. Doing it frequently reduces the amount of work needed and keeps things up to date.
- bayindirh 6y ago
  This is why I document everything during installation, and automate security updates if the system doesn't have any special needs requiring package freeze. Moreover, we template system installation further, so I can install the same server with the same config, with the latest packages with just three commands.
- _trampeltier 6y ago
  Welcome in the real world. It's almost the same like in traditional maintenance, were you have to change filters in HVAC or change mechanical parts all x hours of running and so on. Funny it's also an Cobol thread on the first page of HN. That code does run for years and years .. and I read here make everything new every 2 years. Big projects are not even done in 2 years .. I'm work in industry automation and I'm more and more happy, if a new thing has no computer at all. So much work, so short life.
- earthboundkid 6y ago
  It's a big problem for large corporate sites with lots of sub-brands. A million little sites get launched and then no one ever cleans them up. It would be fine except that they're ticking time bombs of WP ownage etc. It's my firm belief that any site which isn't an on-going concern should be changed to a static site in a cloud bucket just to defuse all these time bombs.

patates 6y ago

People (well, me too) these days script that too, so the good thing is you don't forget a service or configuration, the bad thing is you never forget a service or configuration.

Cthulhu_ 6y ago

This is I think a problem in pretty much all of IT; people install a system and forget about it. What 'people' (sysadmins?) SHOULD do is create a maintenance schedule / contract at the same time, and make sure that it is transferred to the next guy in case of moving on in a job / position. Doing what I can, I make a point of having a calendar reminder to update my software's dependencies every month. Doing it frequently reduces the amount of work needed and keeps things up to date.

bayindirh 6y ago
This is why I document everything during installation, and automate security updates if the system doesn't have any special needs requiring package freeze. Moreover, we template system installation further, so I can install the same server with the same config, with the latest packages with just three commands.
_trampeltier 6y ago
Welcome in the real world. It's almost the same like in traditional maintenance, were you have to change filters in HVAC or change mechanical parts all x hours of running and so on. Funny it's also an Cobol thread on the first page of HN. That code does run for years and years .. and I read here make everything new every 2 years. Big projects are not even done in 2 years .. I'm work in industry automation and I'm more and more happy, if a new thing has no computer at all. So much work, so short life.
earthboundkid 6y ago
It's a big problem for large corporate sites with lots of sub-brands. A million little sites get launched and then no one ever cleans them up. It would be fine except that they're ticking time bombs of WP ownage etc. It's my firm belief that any site which isn't an on-going concern should be changed to a static site in a cloud bucket just to defuse all these time bombs.