You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Why early-in-career?
I accidentally rm -rf'd the @euskalencounter postgresql DB once, by exiting one ssh level too many from a testing VM out into the prod host.
Thankfully there were hourly backups (which I'd set up), so I took the chance to upgrade postgresql :-)https://twitter.com/delroth_/status/1256041866354712577 …
After that I stuck a big 
emoji into the zsh prompt of prod hosts.
The only data lost was a user that had registered themselves in the time between the backup and the accident. We have structured logs which include everything but the password, so I manually re-created them.
Then we asked our admin/support person to email them informing them that they need to reset their password.
i still love having delayed db slave(s) as recovery mechanisms. not only covers sysadmin errors but also user/moderator incidents where soft delete might not be a thing. also in a similar way i colour code shell tabs according to their danger level
We actually have a standby slave now (was set up after the incident too), but it's not delayed.
On my personal systems I at one time did something similar, where each machine had the hostname in a different color specific to that machine. As machines have been retired, reformatted, drives replaced etc. those $PS1's have been lost, however.
I had my account on my workstations blue, my account on other systems yellow, and root was always red. I should go back to that. Also, prompts should always have username and host name. Ideally they should have path too.
Nice recovery and response to try to avoid it in the future.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
