21–30 of 81 posts
> I even disable all notifications on my iPhone before I go to bed, so I don’t see them before I start working next day.
Not convincing to me. I do agree with the general notion that working 8 productive hours everyday does not work long-term. But assuming that you could work three hours completely productively every day, that does not imply that the remaining five hours would be completely worthless. In a normal work week, I am sure you could get more out of the remaining 5x5 = 25 hours than the six hours at the weekend. Especially th…
> Yes, I have to do everything, including UI&UX design, marketing, supporting and so on, since I’m a solo person. The coding might be around 50% of the work time.
The headline doesn't reflect the reality - I think what is really going on here is that 3 hours are spent doing what is considered 'work' by the outside world (sitting in front of the machine and writing the code that people believe is what the job is). However, creative stuff like programming doesn't tend to fix in such a neat box, and the preparation, or creative thinking which leads to elegant solutions to problem…
> I've never tried to average it out, but 2-4 hours of actual productive coding per day sounds about right. And how many unproductive hours of work do you spend per day? I tend to fix my working hours (productive or not) to around 4 per day. When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about worki…
We'd have much less pieces from Mozart if he had followed such advice
Saying that OP's point doesn't/wouldn't/shouldn't apply to an extremely exceptional case is a tautology (and this is even assuming that Mozart didn't already follow OP's advice in the first place, which you haven't exactly established). Here's a more interesting example, which at least shows that it doesn't apply to a much larger category of jobs than genius composer: If Amazon warehouse workers'd follow such advice,…
The headline doesn't reflect the reality - I think what is really going on here is that 3 hours are spent doing what is considered 'work' by the outside world (sitting in front of the machine and writing the code that people believe is what the job is). However, creative stuff like programming doesn't tend to fix in such a neat box, and the preparation, or creative thinking which leads to elegant solutions to problem…
> I've never tried to average it out, but 2-4 hours of actual productive coding per day sounds about right. And how many unproductive hours of work do you spend per day? I tend to fix my working hours (productive or not) to around 4 per day. When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about worki…
Honest question, do you unilaterally ignore any other parts of the contract?
Earlier quoted context omitted.
> I've never tried to average it out, but 2-4 hours of actual productive coding per day sounds about right. And how many unproductive hours of work do you spend per day? I tend to fix my working hours (productive or not) to around 4 per day. When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about worki…
> When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about working hours. Honest question, do you unilaterally ignore any other parts of the contract?
Earlier quoted context omitted.
> When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about working hours. Honest question, do you unilaterally ignore any other parts of the contract?
Nobody works exactly to the contract. Except perhaps in the most monitored and hellish workplaces (e.g. Amazon warehouses).
Earlier quoted context omitted.
> I've never tried to average it out, but 2-4 hours of actual productive coding per day sounds about right. And how many unproductive hours of work do you spend per day? I tend to fix my working hours (productive or not) to around 4 per day. When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about worki…
> When I tell fellow engineers about it, they think it’s unethical because my contract specifies 40h/week (I’m an employee). I couldn’t care less what the contract says about working hours. Honest question, do you unilaterally ignore any other parts of the contract?
What (most) managers want is your output, irrespective of how long it will take, may be 12h or 3h.
One could argue, that while working 3h or 4h one should still be available to support, help, communicate, meet with, your team and stakeholders for the remaining hours of that contract.
I would not have an issue with less hours provided you don't ghost for the remaining hours, if one of your colleagues hits a block, or your manager gets hit with a shitstorm, then you need to have a communication line open (which should also not be 24 hours but for the hours in your contract).