Bezos has given interviews about his habits. He works maybe 10-20 hours a week.
Billing 40 hours every week to run scripts that generate a Github repo structure in minutes has been profitable for me though. Not going to knock Musk and Bezos optimizing for themselves by gaming others agency.
Also the ultimate test is whether after confessing to your real contribution, people are ok. I don’t think any amazon employee was annoyed after hearing this so called interview, whereas is your company knew what you were charging them for, they would fire you.
He’s not a genius just well networked.
Idle idolatry of normal human beings with no effort to verify their real outputs creates an unfalsifiable truth Bezos is a lynchpin to reality.
Ooo oo I heard it through the grapevine, Bezos is not what you might call “divine”…
The rich did not invent science, engineering, and economic activity. Human behavior gives rise to those things organically. The rich are merely playing information awareness constraint games; a man named Farmer is a farmer, an engineer is an engineer, and there’s no reason to allow them agency to learn other things.
His value is rooted in traditions of political correctness to buy into that narrative, not immutable laws of nature.
It's not entirely rags to rich because gramps indeed did well for himself and had a nice big ranch out in the middle of Nowhere, Texas. But it's pretty close to it, and overall a pretty cool story.
That alone is a testament to how the country has changed. How many McDonalds burger flippers have that social network now?
His childhood and his family greatly benefited from pre-Reagan social programs.
How sad if the mega-mega-billionaires were mega-mega-millionaires. The rich of their childhood got through high taxes ok.
If such taxation is immoral, let’s discuss then the advantages immoral taxation in the past provided them and accept them as less uniquely gifted and successful on their own then.
If my boss is happy to pay this amount for my level of work output, why should it matter whether I'm spending 40 hours or 4 doing it? In fact, to suggest otherwise is downright Marxist, asserting that the value of my labor is the time I spent doing it, rather than the value someone else is willing to pay.
Do you subscribe to the labor theory of value for goods, or just people?
White collar work, is of course, way worse. There is a lot of slack time in between tasks and meetings and so on.
So during those 40 hours, let's say a person delivers 100 work units. If we were to say, from now on you only have to work 32 hours, some people will still deliver 100 work units, but many will deliver an approximation to 80 work units. Many people will automatically adjust. People have a "pace of work" that is like breathing.
Perhaps in manual labor, but I don't think this applies to white collar work. The limiting factor in output for this line of work seems to be intellectual exhaustion/burnout, not pacing.
Personally I assign development to more of a "creative" role than a lot of people tend to. Your productivity can often depend on your inspiration, moreso the more senior/architectural your role is.
I've certainly had moments where I accomplished more at one 3am moment of clarity than an entire week before - and I think most experienced developers can say the same.
My “work hours” in my pay slip say 75.8 for every 2 weeks. I work maybe 50 hours in a busy week. It is irrelevant to my organization. So we are already there in terms of intellectual white collar work.
If the company cared only about getting certain amount of work done in the time they paid for, they would hire an external. And continuing the analogy, it's usually more expensive in the long run to rent a tool even if you use it only a couple of times a month, as well as having to get used to unfamiliar equipment, having no records of how well the rental tool performed earlier.
I'm so happy to be out of the office. Being able to work whenever works for me (and my ADHD brain) has probably given me at least 50% more output on average. Hours don't mean anything to me and nobody has ever complained about my work pace (rather the opposite).
Pretending to be busy in an office was torture.
Wish the promise of "Salaried means we pay for the job to be done" ideal was more of a reality.
She Has collapsed before when total was getting above 80 for several weeks.
They want to promote her to VP. They work even more hours then she does.
I make more then triple what she does.
This part doesn't make sense to me, can you please explain (I'm genuinely asking). My children are in elementary school, and the day is from 8:45-2:30. I can understand being there at 8am(i definitely have seen teachers showing up later than this though), and when I've driven by the school at 3pm nearly all the cars are gone from the teachers lot (if not all). I can understand that there's a lot of work outside of school, but I don't understand how you could ever get to 60 hours at school.
Before: you take a stack of papers, and go through each one with a red pen.
Now: you log on a system, wait, click on something, wait, click on something else, wait... the stupid tests are auto-graded, but chances are there is still something you have to grade student-by-student, and that's now slower to do. Plus, obviously, the usual annoyances (got to update this, got to reboot that, my typing is 5WPM, etc etc).
You know, if someone wants to write The Next Great JS framework, give me one that above all else prioritizes latency and expert-level usage. There's no fundamental reason we can't have most of the nice things from the modern graphical web, and get to the legendary efficiency of those text-based consoles... but it will take some work and thought. (For example, you're going to need to insert yourself in between the user and the browser's concept of events, so you can buffer up commands the user is typing while their target hasn't quite loaded yet. This is one of the fundamental reasons why GUIs are less efficient than TUIs, though by no means the only one.)
This framework won't take over the world, but it sure would save a lot of people a lot of time.
Sooooo tiiiiirrrrreeeeed of programs that take seconds to do every... little... thing!
I remember having to use educational software in college for a discussion board and it was terrible and sucky. I could only imagine what the teacher end of it looked like.
—-
For a comedic look at how this affects teaching, the new comedy show Abbott Elentary has an episode on this. It’s like Parks and Rec but at an inner city Philadelphia public school.
Until 2011, my local school district was using a DOS-based attendance and grading system. No GUI.
In 2011 they switched to an internet-connected system that looked like it was built on Windows 3.1. Non-resizable text fields. Inability to tab from one field to the next. A tiny non-resizable window that you had to scroll manually with the scrollbar to enter data in all the fields, so to enter attendance for a whole class you had to scroll left and right with the mouse for each child.
It crashed every morning for months. Teachers would coordinate with each other to ensure they didn't overload the system.
My wife’s school is big on community, which is great in some ways but leads to long days with staff expected to attend dances, games, etc.
My dad was up at 6 and at school for 7am. Worked 7am-3pm (8 hours). He did marking for an hour or two most evenings, and a solid chunk on the weekends. Probably 50 hour weeks. And that's after 20 years of teaching the same classes, so he had all the materials.
My ex-wife was brand new to teaching so had to develop curriculum on top of this. She worked 7am-5pm every day plus weekends.
Calling parents, dealing with kids with special needs, developing curriculum, marking, department meetings, making lesson plans, running extra-curricular activities or clubs, private lessons, doing paperwork or photocopying, etc etc, it all mounts up. There's a lot of behind the scenes work.
Now, some teachers simply don't do this. You can easily skate by, work the bare minimum 6 hour days, and not give two shits about the kids. But most teachers care about children and education (I mean, you don't become a teacher for the money).
What if at least part of the 20% is spent doing social activities, water cooler conversations, etc. that enable the remaining 80% to flow more efficiently?
It's foreplay but for work. Forework?
Most people structure their days based on what they want to accomplish (goal driven), rather than how to spread out work evenly across a fixed number of hours (time driven). So if someone knows that they are expected to deliver task A + B in one day then they will do it. If they have a 4 hour work day they'll do it in 4 hours and then happily clock off. If they have to do it in an 8 hour work day they'll do it in 4 hours and then waste time for the remaining 4 hours.
Also, when we consider capacity to focus instead of just time spent at work, I think normal rate is 2 focus bouts of 1.5h each per day. You can get to 3 if you train, but not much more. (I got this from Hubberman's lab podcast, not sure what's the underlying research)
So if you decrease work time to 5h, you give 2x bouts of focus + 1h break between bouts and have 1h left for marginal stuff/meeting.
Maybe going up to 6h would allow for the extended stuff (email, meeting, discussion, lunch) But I feel like 8h just create a world where you need to waste time in the end, just because of physiological concerns.
At my previous startup we saw an 8% productivity _increase_ from moving to a 4-day work week, and this was across a variety of metrics like issues closed, lines of code, etc. We don't even know if 4 is optimal, it could be 3. Only way to find out is to try it.
Maybe they were burned out from the extra hour of the previous days, but considering the Thursdays of the remaining 5 day weeks didn't display this behavior, I doubt it. Now there was the complication that once management saw a dip in productivity, there was a near mutiny at the mere suggestion of going back to a normal workweek.
The implication is no matter how long/short the work week is, people will adjust to make the end a slack day.
This seems to land in the area of untested hypothesis. Sure, we can speculate on all kinds of mechanisms. I could speculate that by going to 3 day weekends would lead to a bigger "rejuvination effect" and more productivity. But the data gathered from my org showed the opposite. Productivity went down. And now management had a lot of pushback to just get back to their baseline (more productive) schedule.
Now I'm willing to concede that it's going to be different industry to industry. It may very well work well in SWE and I think we see a lot of that bias in tech-centric circles. I also think it’s an error to assume it holds for most industries. My example was from an R&D area and not strictly software engineering. Do you, for example, think your doctors office would have more patient throughput if they went down to 4 eight-hour days? Or manufacturing? I'd be skeptical until I see the data. And I concede that a lot of work cultural differences also matter. And leadership matters. My original post was not claiming some definitive answer, just giving some pause to the sentiment that reduced hours is a generalizable rule to increase productivity*. I think a lot of people let their cognitive biases get the best of them and run with the idea.
* I also think "productivity" is the wrong way to frame the problem. Some things, like work-life balance, are a net good and worth a hit on productivity. The economy should serve society and not the other way around.
I mostly agree with what you're saying, especially about going across industries, but I do believe it is quite easy to lower productivity, regardless of the industry, by dramatically imbalancing work-life balance. Put another way, having good work-life balance is a net good, partially _because_ people with good work-life balance are more productive than people who are burned out.
Your medical doctor isn't going to be very good at diagnosing patients when he's in his 140th working hour of the week, if he were to attempt such a thing (with ~3 hours of sleep per night and no time off other than that)
This is actually what I'm pushing against. I don't like productivity being a primary principle. I'm saying it's worthwhile irrespective of the impact on productivity. (the use of 'net good' was a bad choice on my part because it implies a balancing act).
It's quite common for healthcare workers (particularly surgeons) to work extremely long hours, but that's being re-thought in some areas (esp. in regards to residents). To your point, though, I think a lot of the rethinking is driven by trying to reduce medical errors. It's more related to quality than productivity, but I don't think they can be easily parsed.
They will work more than 80%, less than 100%, say 87%. And that is what you want: keep some off time for conversation, recovery, etc..
You don't want 100% (very short hours) and you don't want too low a percentage (long hours). There is some balance in between and no slippery slope.
Given humans are highly adaptable I imagine we will adjust to the new normal and keep finding time to mess around at work.
Even years ago when I was in the office, everyone would go on insanely long lunch breaks on Friday instead. If you work an office job, I can assure you that the number of people actually working on Friday is statistically irrelevant.
> In October, the average workweek for all employees on private nonfarm payrolls was 34.5 hours for the fifth month in a row.
I see the report calls out part time workers at 3.7m yet still I wonder.
A UK company did a study which showed the average office worker, who is in the office 40 hours a week, is only productive for less than 3 hours a day.
https://www.vouchercloud.com/resources/office-worker-product...
I would guess the average workweek, only counting the time people are actually productive, is 10-15 hours a week. The rest of the time people waste procrastinating, posting on social media etc.
I used to do a lot of walks (before I moved from Upstate NY to Houston) where I would escape the code and think about the product. That was all billed time, and understood by my clients. Just because my fingers are not furiously typing, doesn't mean I'm not actively engaged in my work.
This company's policy is the clock is only running if you're 100% engaged. I try to stick with that. As time has gone on I've gotten better about mentally turning the switch more all the way on/all the way off. There's some grey area on both sides that I figure comes out in the wash. And if I have a serendipitous moment, it's not hard to turn the clock back on and have at it.
It'd also look more different if the billing increment was wider. In a very past life I billed at 15 minute intervals. So if I was "on" for 12 minutes but stepped away to clear my head, the full 15 was billed.
Yeah this is a pretty interesting phenomenon. I feel like as a kid I had no idea it would be this way, but every job I've worked, blue and white collar, has involved a lot of "time wasting." It's very surprising at first.
40 -> 32 -> 30 -> 29.5 -> 29.3 -> 29.2 -> really, we are talking about minutes(?). Just keep 29-ish and check again in a century.
Arguably, you can't turn it off when you clock out either. It's why I argue for a retainer model on intellectual workers.
Do you have any books you'd received recommend that have any additional tricks?
When I get into a “flow” on a project I can work 12+ hour days. My productivity dwindles as the day gets old for sure, but I don’t think it ever gets to zero or close. I dream/think about the project and the first thing on my mind in the morning is the next step on the project.
Last time I was in flow, I single handedly built the next generation of a tool in 2 months. It’s currently taking the other team about 6 months to do the same but for another platform. The complexity is roughly the same and I think the engineers are as smart, if not smarter than me. I think the difference was that I did 12-16 hours for 2 month (including weekends).
This is not sustainable of course. I developed my back and wrist pain at the end of the 2 months. This is something I consciously stop myself from doing ever again because health is all you got at the end of the day.
I typically code for like 3-4 hours a day, maybe 6-7 when I'm super into what I'm doing. BUT, I very frequently think about my work when I'm not working.
It just feels to me like some sort of secret we all share and pretend like it's fine, but being honest and just doing the same stuff in say 32 hours and cutting out the cruft in between would be great.
Or maybe it's just my add that likes a bit more pressure, I don't know. But what I do know is that, even with a very relaxed employer that allows you to take your time and chill, go workout or play a game for an hour, I can't fully relax or disconnect knowing that I'm expected to do those 40 hours, regardless of how often they say it's fine.