For further actions, you may consider blocking this person and/or reporting abuse
For further actions, you may consider blocking this person and/or reporting abuse
Nandini S Hinduja -
Jon Snow -
uliyahoo -
Random -
Once suspended, zajkowskimarcin will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, zajkowskimarcin will be able to comment and publish posts again.
Once unpublished, all posts by zajkowskimarcin will become hidden and only accessible to themselves.
If zajkowskimarcin is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Marcin Zajkowski.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag zajkowskimarcin:
Unflagging zajkowskimarcin will restore default visibility to their posts.
Top comments (15)
I pushed an infinite loop into our deployment process which took down the site and got us rate limited and suspended by Heroku. It also caused elevated failure rates on their whole service enough that status.heroku.com had a yellow message about the situation.
Two things, both on a large Wordpress installation:
Once removed a Tomcat server while trying to remove symlink. Fortunately was a internal server for CI that was being implemented.
And other time deleted a production database. Fortunately there was a morning backup and lost 3 articles
First webmaster gig and first formal job. Learning FTP accidentally deleted a whole Wordpress site. Almost got fired on my first day.
Sounds like their screw-up to me! First day on the job and they have you "learning" FTP on the server with important sites on it?
Accident waiting to happen.
Yeah the company management and infrastructure were missing hahahaha
Hope the company had the proper source control etc. and it was just a matter of redeploy? Or not...? :)
No it didn't. Infrastructure was not a word in that company hahaha. I got lucky because there was another copy of it in an old HDD
Oh man, so it was fun! ;)
One of my calculations worked backwards. The internal testing was manually triggering the fake passage of time by increasing the number of days, and it worked perfectly. As soon as it went to live I realised it was supposed to be x - y, not y - x and the whole thing ran backwards. read: it didn't work.
🙈
I used Python once. :-(
Oh no! How dare you?! ;)
sudo rm -r -f /*