147
Whats a good lesson you learned on the job? (piefed.social)
submitted 4 months ago* by to c/asklemmy@lemmy.world
144 comments fedilink hide all child comments
 

For me:

Sometimes it doesn't matter how hard you work, your going to get laid off either way.
Just showing up can sometimes make the difference.
Your not paid to be a software developer. Your being paid to be a problem solver.

you are viewing a single comment's thread
view the rest of the comments
[–] 39 points 4 months ago (3 children)

Validate your backups regularly.

Also, make backups.

  • permalink
  • fedilink
  • source
  • hideshow 6 child comments
    •
  • [–] [S] 18 points 4 months ago (1 child)

    Taking a day to actually test backups by doing a cold reset can save a business, thats for sure.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 12 points 4 months ago (1 child)

    The horror of being a senior admin is realizing that the whole thing could live or die based solely on your actions and decisions. And that you will be blamed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 4 months ago (1 child)

    This is where you bring Chaos Monkey in and see where your weak points are.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 4 months ago (1 child)

    Years after the fact I could make the lead developer’s eye twitch just by mentioning the guy who was supposed to maintain the backups but we discovered after the fire that he actually hadn’t been doing it. That guy was fired, but it didn’t bring back the lost code.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •