How often is a ban on any changes practiced on Fridays?

Anton Belichkov2012-07-06 10:45:26

Time Management

Anton Belichkov, 2012-07-06 10:45:26

And in your,% habrauser%, department (office, in short, at work), they also don’t contribute anything to production on Fridays?

Answer the question

In order to leave comments, you need to log in

13 answer(s)

Nikolai Turnaviotov, 2012-07-06
@za90

Everywhere where I worked as an administrator there was an informal ban on any configuration changes other than emergency ones, and Friday - routine, documentation and other trifles

Ivan, 2012-07-06
@iSage

Well, those who have a desire to come to work on the weekend - contribute.
Minor and tested edits are also made. Something big - usually not.

Stdit, 2012-07-06
@Stdit

Yes, except in exceptional cases. And after 15:00 too.

Perkov, 2012-07-06
@Perkov

In some Finnish institutions - the ban begins approximately 1 month before the submission of the annual report.

xldsakamrhahn, 2012-07-07
@xldsakamrhahn

It is forbidden to make changes on the product on Friday and on the last 2 days of the month.
I think this is correct, since the projects are financial.
For non-financial projects, there is a ban only on Friday.

Nikolai Turnaviotov, 2012-07-06
@foxmuldercp

A friend worked in a company, so they had a very strict policy of updating machines through vusas - with a gradual deployment of updates both on the station and on the server - all critical ones were always installed on 2 nodes from the cluster, and if there were no problems, then the servers were updated over the weekend with reboot.
But they have at least 4 virtual machines for each service on different nodes and half of them are in another DC.
At one time, they survived a blackout in Moscow.

kartoha, 2012-07-06
@kartoha

It happens that the owner wants to, but we are against ... As it was already said above, we do not want to spend the weekend on "debriefing".

cat_crash, 2012-07-06
@cat_crash

The workflow 7 days a week is the main staff of freelancers, so on Friday, as well as on Monday, there are a lot of commits, pulls for production

Vladimir Chernyshev, 2012-07-06
@VolCh

Worked where Friday was the recommended day for releases. Target audience - corporate users.

oia, 2012-07-06
@oia

we have long adopted the practice of not touching important processes on Friday, but there is one thing that TOP employees or founders of the company have on Friday after 15 00, when IT has already decided to drink beer or cognac, problems arise and we need to look for employees who can go and morally help the poor fellows for now at this point employees with a spoiled mood solve the problem remotely.

freeek, 2012-07-06
@freeek

They do not contribute, although it is on Friday that the feedback is the most active.

vatuma, 2012-07-10
@vatuma

Personally, I'm a little surprised that many (judging by the comments) are forbidden to make changes on Friday. And how then to cope with unforeseen situations? Well, they rolled, for example, some unfortunate change on Monday morning - and the company stopped. While specialists are figuring it out, the company stands still, losing money. How can a leader do this? Well, that is, of course, breaking something non-critical is not scary, but what if it is a corporate/banking system?
We have all any important changes rolling in just on Friday evening - 8 o'clock in the evening. The next 2 days (Sat, Sun) are for restoring system performance :)
For the most significant changes, longer weekends are chosen - for example, New Year's or May holidays.

hildisvini, 2014-01-23
@hildisvini

No big deployments on Fridays after 12:00, on other days - after 16:00.
This is not an official ban, just an internal rule. Inexperienced client-side managers demanding to roll out an update to production on a Friday afternoon are scared of going over budget.