There are plenty of developers who work 7+ hours a work day, plus a little more at nights or on weekends during crunch times. I'm one of these people and every place I've worked has had these people. It's not like all of our work requires intense concentration - sometimes it's just typing or testing.
Sure, there are people who put in very little "real work" by their own admission, and think they are doing just fine. But that's not a luxury afforded to the entire industry
That's normal across all industries. If there are people who are actually productive for 7 hours per day, they are extreme outliers.
I used to think that I worked 8-10 hours per day. That was until I measured my actual productivity.
I worked as a translator once. When I timed myself, I found that I can translate about 2,000 words in 1 hour. But in a day, I struggle to do more than 5,000 words, no matter how hard I push myself- even though that's just 2.5 hours of work! And if I do 5,000 words every day, I burn out within a week.
I think it’s important to realise that there’s that limit to productivity, so don’t force it if it’s not working. take a break, come back tomorrow, you may find that you’re far more productive even though you’re spending less time “bums on seats”. Somewhat employer dependent
I do pretty grueling manual labor at night. The shift is 8, I think about 4 hours is reasonable (under 55), we do about 5. We have to carefully hide the other 3 hours. The shift starts with 20-40 min of planning and organizing which is maybe 4 minutes of work, we glue 10 min in front and behind the lunch break, we rest out of sight, we "finish" early.
I often joke that a marathon is only 2 hours if you run really slowly. The culture is to expect us to do 5 marathons in 8 hours, every day! uhh.. i mean every night! Which is every bit as hilarious as it sounds.
I calculate for the MBA types that if they cut the shifts in half and raise the pay by 50% people will be well over 25% more productive. Sleeping at night is not overrated. Both the pay raise and the reduced work day are of course culturally unthinkable. Their eyes just glaze over. I further joke that they don't have to understand. They can just join us and run these 25 marathons for a week. Only one week?
When coding I prefer either ONE hour/day or 14 days straight 14 to 18 hours/day. That way everything fits in my head and I feel very productive. The endorphin milestones fly by. It's lovely. After that I don't want to see any code for two months. I don't want to even try to explain this to any employer. I probably wouldn't even want to understand it if I was hiring.
Philip limited mine workers work days to seven hours! That was 430 years ago.
</rant>
It says something about society that asks people to work well beyond their retirement age.
I hope you are only looking because it gives you purpose rather than doing it because it’s necessary (ie, medical bills, rent). If it’s the latter, very dystopian and on par for this neoliberal economic hellhole we live in.
Personally, if I get to that age. I am cashing in my chips. No way I am working for soulless corporations, whether that’s part time or full time.
I would much rather “retire” and work on my own open source projects or contribute to FOSS projects I like. Worst case scenario, I become a wood worker ;)
I work because I like it. I like being around smart people doing smart things. But in a couple of years, I will stop working and just spend time lifting weights, practicing bjj and painting.
I dont think that's what's going on here. If you click on OP's profile you'll see that he's written a bunch of books. He also mentions Common Lisp and Racket, not exactly go to languages for soul-less corporations. My take is he's doing it for the love of the craft.
I aspire to do this too when I'm at that age. I've been through a few career iterations with the only constant being is that I love to make things.
I envisage myself coding for another 45 years (I'm in my 50s now), but I worry about my ability to concentrate on a single task for long spells, think creatively yet realistically enough to find solutions; to learn the latest fads and tools, and maintain my enthusiasm to keep up with the latest fads and tools. Will my hands get too unsteady to type, my eyes too weak to focus; how long will I be able to sit (or stand) up and work in a session. No-one knows I'm a dog, but they will if I have to turn on the camera or go to the office, so, will I necessarily be transitioned to more results-driven work assignments via tasking sites?
(I guess these are the typical prejudices that a hiring team will make when considering an older candidate.)
Prepare me. Share your wisdom. What challenges has aging presented to your ability to code?
One thing that I do is that I keep writing code in my favorite languages Common Lisp, Haskell, Racket, and Python (Python only for deep learning). I also still write.