How do you manage to work less than 8 hours despite full-time job?

On average I work between 4.5-5.25 hours per day.

I divide my working time in 45 min. sessions with 10 min. breaks in between. To be honest I don’t always take the breaks, which is wrong and is something I need to improve. During a break I stand up, do a chore at home or go to the balcony.

In the course of each 45 min. session I do only work with little to no interruptions. No casual Internet browsing, no mails and I try to avoid chats. On average I tend to do 6 to 7 session chunks per day which is more than enough to implement features, fix bugs and write documentation.

Distractions. Avoid the ones under your control (reading news, procrastination) and embrace the ones out of your control. When you get a sudden phone call, instead of going directly back to coding, you could read/write mail or answer some work chats. Such activities also count as part of my sessions.

No one is there to supervise me, so I need to be _honest_ about the time I dedicate to work in each session. In the end, I exercise self-control to the best of my abilities. I could also do 3 work sessions a day and still get paid, but I don’t believe this is in my favor. Doing more is OK, but I hit a cognitive limit sooner or later, so I only push myself when it’s really needed.

When I need to learn new stuff, I do it mostly in the mornings. Memory works best after the brain had some sleep.

When people claim they work „less then 8 hours“, they typically found a perfect spot for them where their work is engaging, but also comfortable. They are able to do the work, get challenged enough but are not over-their-head.

I had jobs where I worked 10 hours a day, often on my own will since I wanted to figure something out. Most often than not, I was skills missing for the position I had so I did more work.

I had jobs where I worked 15-20 hours a week, and was praised and earned a lot of money.

So if you are good at something, like really good, and you join a company lacking these skills, than you probably don‘t have to work as hard since you already make a difference just by being there.

You choose your company and the amount you want to work as a developer these times. It‘s up to you. Some people however overwork themselves with 60+ hours and earn less than people who work 20 in a different industry but better pay.

I am currently in a position where I grow a family, and I found a well paying hjob where some weeks I work 50 hours, but most weeks I work 30. I get enough done to be a good performer. And that‘s enough for me at the moment.

Which means, my skills perfectly fit the position I am in, and for once I don‘t try to overdo it but just do a decent enough job to get a bit of praise. I use the down time to relax, watch movies, play with my kids etc.

Some of these things are only possible in certain position,but rough ideas: 1) reduce number of meetings to minimum.

2) in the meetings, know why you are there and try to stick to the agenda.

3) sort out things you need to do by priorities ( low, medium, here and now).

4) Check if your to do list is balanced: e.g. not all tasks are 'here and now'. If it's not balanced,raise it with management or try figure out yourself why that's the case.

5) Turn off distractions: email, text, chat,etc. Leave 1 channel ( phone?) open for emergencies.

6) Inform others where you are and what you do. E.g. : 'I'm in a zone between 9am-11am, don't bother contacting.

7) Learn to be OK if you don't do everything you were supposed to. You aren't in a hospital, nobody's going to dye.

8) Aim to complete 3-5 things in any given day. No point to commit to 20 if it's all going to be half baked.

9) Learn stuff early in the day- much easier than towards the end of it.

10) Take short brakes no matter what: even 5 min walk down the corridor is useful.

Before covid, my work takes on average about 7-8 hr a day. Now, without the social aspect, I can easily do 5-6 hr a day, but there are days I work 10-12 hr because I was in a flow to solve the problem. From my experience, how much you work is largely depending on:

1. company culture. My friends who work on trading desk as tech person were doing long hours before pandemic, now, they are doing crazy long hours. Managements don't trust their people, lack boundary, etc.. I no longer work for those companies and I'm much healthier because of that.

2. Your skill vs expectation of your job. If you can easily qualify for the job in both hard and soft skills, your hours will be easier. If you are behind on the job in those skills, then you'll have to work harder.

3. And lastly, the skills of your team(s). I work with a lot of teams with junior-mid level developers, so I spend a lot of time trying to get them to understand what we are doing. Whereas seniors, we just get it done, but there are some seniors that are more obstacles than juniors.

Software is near impossible to estimate. Things that can be done in 1 day can sometimes take 2 weeks. And something that seems like it should take weeks can take hours.

Then you factor in the huge difference in approaches, skill, efficiency, and productivity between employees. If you are experienced, you skip the hours of googling, reading SO, etc.

You are probably pushing way harder than you need to be.

If I feel like I made good progress, I take the rest of the day off. If something should take a week and I finish it in 2 days - I take the week off.

It is worth questioning how you define "work". I may only sit in my chair coding for a couple hours a day. (And a couple more on meetings and documentation.) But I'm thinking about the problems while I am doing chores, going for a walk, etc. Then when I do sit down to code, it comes to fruition quickly. If I were to spend 8 hours in a chair staring at the screen, I'd "work" more, but I'd accomplish less.

This is why I am such a proponent of remote work, at least for coders - it allows us to spend more time doing what is truly the core of our job: thinking, and less time just sitting in a chair typing out those thoughts into the proper syntax.

I don’t really get in a flow state any more unless I turn off all email and chat. In those cases it can last up to 4 hours.

That happens maybe 20% of all days though, and people don’t really enjoy it, so it’s mostly something I do for my own sanity.

The rest of my day is spent showing up in meetings and trying to prevent people from shooting themselves in the foot, which involves a lot of back and forth.

When in the office, I think I regularly made 9 hour days, but at home they’re at most 7.5 hours, mostly due the constraints imposed by having to pick up my son from daycare.

I once spent a week power washing and staining my deck. I’d only look at the most crucial work stuff and ignore the rest. When that happens, you go through a realization how much of our work actually matters and what appears to matter at the time, but really isn’t as important. In fact some of it just needlessly creates stress and work for others.

I recommend doing something like this, it can be a nice reset button...

In the course of say a quarter or two I work on average 5-7 hours a day. Some weeks there is more work to be done than others depending on the phase of the project at hand. I tend to not start too many things at the same time (start working on a bug, documentation, new feature etc), basically limiting the amount of WIP. Projects still get delivered on time or with slight delays that is not detrimental to the success of the project or the morale of the team, while still learning a ton. so going “the extra mile” anything beyond that is asking for trouble (stress that would eventually lead to burnouts). Im lucky that my direct manager and peers are more or less the same way too. The older i get the more interests i have in things outside of my profession so i try to make the time for it.

I hammer maybe 1-2 days a week (3 max). Then I either cruise control and completely chill the other days.

If stuff really needs to get done though, I'll hammer.

The solution is simple - just switch teams to one where people are allowed to slack off. It's basically a norm in a big bank I work for - the management is mostly non-technical and clueless, there's little time pressure so devs are not really pushed hard (or at all) to deliver.

On my side most of the time is wasted on uncertainty of tasks and some tasks are absolutely boring so I push them back.

Hope I can learn from some of the answers here.