Hacker News Reader

Similar thing - half of the year now with no meeting Fridays & 4hrs Fridays.

This gets extended month to month based on performance, so it could stop, but if they stop it I will really try to find a job where they do a similar thing.

No meetings on Friday means that in four hours you can do as much as with normal Friday but with meetings (given the meetings produce 0 value, which is not the case of course, but also sometimes the meetings could have been an email, a tweet, or a joke).

No code changes from Nov to Jan seems crazy to me. But if it works good for you guys.

This was standard protocol in my org at Microsoft as well. The time was suppose to be spend reviewing tech debt/the years oncall issues and come up with plans for them.

That is the time of year when the vast majority of our business occurs. The systems must be as bug free as possible, so no changes are allowed unless a bug pops up that is mission critical. If that were to happen it would involve huge meetings with tons of conversations and dozens of eyes looking at it, even if it is a simple change on one line of code.

This is pretty standard for organizations that see a large portion of their revenue during those months. This is especially important for ecommerce-like shopping around the US holidays, for instance. Black Friday, Cyber Monday and every intervening day between Thanksgiving and Christmas and the New Year's holidays.

No daily/sprint code changes, release management, emergency approvals and the like. It works pretty well, no major outages and the site kept taking orders.

Source: worked on high-traffic e-commerce infrastructure around US Black Fridays/Cyber Monday shopping days.

No code changes pushed to production is what I've experienced in such places as a risk mitigation strategy, not that everyone is sitting around twiddling thumbs. Every hour of downtime between Black Friday and Christmas will cost a lot of revenue, and sometimes the company will be working with a skeleton crew for a huge chunk of that time,which makes fixes take longer as a bonus. So why risk it?

I have the opposite experience at my company. We are given half days on summer Fridays. However, because the workload and client communications were not reduced, 80% of weeks the junior team members would take off, and myself and other senior members would not only have to unofficially work the full Friday, but also take on the work of the rest of the team.

No code change at all or nothing pushed to production environment ?

Nothing pushed to prod, but for all practical purposes all code changes stop. We use the holiday season to learn stuff, write documentation, brainstorm, clean stuff up, etc.

Any chance you’re hiring?

My department is not.

That just sounds like your company has too many employees. But also if they haven't discovered this themselves, good on them for paying for extra, unneeded jobs.

Well, the company does have tens of thousands of employees. I'm not sure how anyone would determine if there are too many. Of course some of the salaried employees are the lifeguards at the pool, the rock climbing wall people, etc. You would probably consider those to be extra, unneeded jobs.

More employees is irrelevant. I determined you have too many simply based on the information you gave.

That's not a bad thing, it's probably a good thing. But they're definitely unneeded.

>Of course some of the salaried employees are the lifeguards at the pool, the rock climbing wall people, etc.

???