I have done this before, but arranged my days off to be alternating Mondays and Fridays so that every two weeks I'd get a four day weekend. My bosses were very generous with my schedule. :-)

Honestly this seems like the ideal scenario. Full pay, likely no argument from superiors about the amount of work you'd accomplish, and the ability to take long weekend trips without wasting a day or two of PTO.

I only see a few possible downsides:

- Someone expecting you to be in the office and you're not, particularly if they're not familiar with your schedule.

- For developers the same issues with 60+ work weeks often come up in hours 7-10 of a single working day. Off-campus lunch for a full hour (or more) would probably be important, which pushes your full day to 11+ hours.

- Using 10 hours of PTO when you take a day off, but I guess that's what you get for getting the 4-day weekends :)

This is the schedule my father has, working as a mechanic in a power plant. It's pretty solid.

The only (kind of ironic) downside is that holiday weeks are kind of sucky. The holiday day only pays 8 hours, so he ends up having to still work four eight hour days those weeks.

Working 3 10-hour days during a week and 6 5-hour days during a week seems equally doable, but I think I would get more complex, brainy problems solved with the latter, and more simpleminded grunt work done with the former.

I do this every once in a while, and my most productive hours tend to be... the two hours left in my day after everybody else has gone home. The office is silent and there are no distractions or emails. I can just get "in the zone". Maybe I should start doing this more often...

Anecdotal evidence, I used to to that as a CSR at PayPal years ago. After a "normal" day of height hours of calls or emails you had two more hours of emails.

My brain was fried and I was glad when the policy was canceled.

I loved the extra day though (which was Monday or Wednesday) and as a software engineer I would love to pull it off, to rest or work on my own thing, but I would gladly take a pay cut than work 10 hours a day constantly.

>Anecdotal evidence, I used to to that as a CSR

What does CSR stand for?

It likely stands for Customer Service Representative.

Yes. Maybe it's not as well known as an acronym in English as I thought.

I think I conflated your current role as a software engineer with your previous job as a CSR. Besides poor reading comprehension on my part I think assuming a position like CSR is hourly and (typically?) only salaried employees answer emails after they go home contributed to that. Sorry.

How is that working less?

It's not working less, some of us need 100% of our pay to get by and can't afford a 20% cut for less work (the stress of having less money > the stress caused by working more)