So that will solve it?
-
From the CP newsletter There’s More Proof That Return to Office Is Pointless[^] Discusses claims that return to office is more efficient and then covers research that suggests otherwise. It also closes with the following "The United Parcel Service is mandating staff return to the office five days a week ... The package shipper hopes this change, and 12,000 layoffs, will help the company bounce back from a slowdown in shipments" I can only hope that the article phrased that badly, because of course that is nonsensical.
-
From the CP newsletter There’s More Proof That Return to Office Is Pointless[^] Discusses claims that return to office is more efficient and then covers research that suggests otherwise. It also closes with the following "The United Parcel Service is mandating staff return to the office five days a week ... The package shipper hopes this change, and 12,000 layoffs, will help the company bounce back from a slowdown in shipments" I can only hope that the article phrased that badly, because of course that is nonsensical.
I prefer an office. There are too many distractions at home.
-
I prefer an office. There are too many distractions at home.
-
I prefer an office. There are too many distractions at home.
I miss an office for the same reason. The kitten isn't helping matters. :laugh:
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I miss an office for the same reason. The kitten isn't helping matters. :laugh:
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
The kitten was a choice.
-
The kitten was a choice.
A choice by Himself, that I opposed.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
From the CP newsletter There’s More Proof That Return to Office Is Pointless[^] Discusses claims that return to office is more efficient and then covers research that suggests otherwise. It also closes with the following "The United Parcel Service is mandating staff return to the office five days a week ... The package shipper hopes this change, and 12,000 layoffs, will help the company bounce back from a slowdown in shipments" I can only hope that the article phrased that badly, because of course that is nonsensical.
I always feel these studies are very one-sided or leave things out. For my own employees, I have a sort of 50/50 rule, but I'm flexible. The thing I notice is, when we're at the office we talk, we laugh, we share knowledge, etc. They may not be the most productive days in terms of lines of code, or however you want to measure programmer productivity, but we're making progress, not just now, but also for the future. Like this guy who wrote a health check in .NET and I was like "Hey other guy, you should see this! We're going to build this into every application from now on, so you too." This sort of interaction is priceless and it's simply missing at home. Let's put it into numbers. We have a junior employee with a productivity of 6 at the office and 5 at home, because at home they can't ask questions like they do at the office. Worse case scenario, the junior has a productivity of 6 or even 7 at home, so they code bugs even faster, but let's stick to 5. We also have a senior employee with a productivity of 7 at the office, but 9 at home because the junior is not nagging him as much. Some simple math tells us productivity at the office is 6.5, but productivity at home is 7! If the junior has his way and isn't corrected, the "productivity" could even grow to 8!!! However, neither party learns something and the junior might get frustrated with their job and fall back to 4 productivity in the long run, (silent) quit their job, or unleash all kinds of horrors into production systems. That's longer term, of course, so for now we're happy with a productivity of 7 (or higher). When the senior quits you're left with a junior who never got to learn from his peers. I think you need a very well oiled development machine (with code reviews and everything) to be able to have the same kind of productivity from home that you have at the office. I think what hampers productivity is the "you have to be at the office five times a week" mentality. It shows an employer who doesn't care about their employees' wellbeing. Also, having long commutes is killing, that's why I won't soon hire people that live further than approximately 45 minutes away. That's why I like 50/50, it's the best of both worlds. You just can't convince me either one is all good or all bad. Any study that says otherwise, like this one, is flawed and drawing wrong conclusions. Case in point, this particular study studied the largest corporations America has to offer, but I'm just a small business in the Netherlands, which is (probably) c
-
From the CP newsletter There’s More Proof That Return to Office Is Pointless[^] Discusses claims that return to office is more efficient and then covers research that suggests otherwise. It also closes with the following "The United Parcel Service is mandating staff return to the office five days a week ... The package shipper hopes this change, and 12,000 layoffs, will help the company bounce back from a slowdown in shipments" I can only hope that the article phrased that badly, because of course that is nonsensical.
Can't stock shelves sitting at home. Then again, I've had to "share" a desk and / or computer. (Contractor).
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
From the CP newsletter There’s More Proof That Return to Office Is Pointless[^] Discusses claims that return to office is more efficient and then covers research that suggests otherwise. It also closes with the following "The United Parcel Service is mandating staff return to the office five days a week ... The package shipper hopes this change, and 12,000 layoffs, will help the company bounce back from a slowdown in shipments" I can only hope that the article phrased that badly, because of course that is nonsensical.
Well, I sure hope someone there figures out that it would be a good idea to find a workable solution for each individual/team. Maybe they try to avoid common sense. :) Client has a marketing engineer who can do just about everything at home. He decided, on his own, that he did better in the office. Most do hybrid. For my client, I do what I can from home (50 miles), via VPN, and go down there when I have to. One hour train ride.
>64 There is never enough time to do it right, but there is enough time to do it over.
-
I always feel these studies are very one-sided or leave things out. For my own employees, I have a sort of 50/50 rule, but I'm flexible. The thing I notice is, when we're at the office we talk, we laugh, we share knowledge, etc. They may not be the most productive days in terms of lines of code, or however you want to measure programmer productivity, but we're making progress, not just now, but also for the future. Like this guy who wrote a health check in .NET and I was like "Hey other guy, you should see this! We're going to build this into every application from now on, so you too." This sort of interaction is priceless and it's simply missing at home. Let's put it into numbers. We have a junior employee with a productivity of 6 at the office and 5 at home, because at home they can't ask questions like they do at the office. Worse case scenario, the junior has a productivity of 6 or even 7 at home, so they code bugs even faster, but let's stick to 5. We also have a senior employee with a productivity of 7 at the office, but 9 at home because the junior is not nagging him as much. Some simple math tells us productivity at the office is 6.5, but productivity at home is 7! If the junior has his way and isn't corrected, the "productivity" could even grow to 8!!! However, neither party learns something and the junior might get frustrated with their job and fall back to 4 productivity in the long run, (silent) quit their job, or unleash all kinds of horrors into production systems. That's longer term, of course, so for now we're happy with a productivity of 7 (or higher). When the senior quits you're left with a junior who never got to learn from his peers. I think you need a very well oiled development machine (with code reviews and everything) to be able to have the same kind of productivity from home that you have at the office. I think what hampers productivity is the "you have to be at the office five times a week" mentality. It shows an employer who doesn't care about their employees' wellbeing. Also, having long commutes is killing, that's why I won't soon hire people that live further than approximately 45 minutes away. That's why I like 50/50, it's the best of both worlds. You just can't convince me either one is all good or all bad. Any study that says otherwise, like this one, is flawed and drawing wrong conclusions. Case in point, this particular study studied the largest corporations America has to offer, but I'm just a small business in the Netherlands, which is (probably) c
-
The kitten was a choice.
-
Well, I sure hope someone there figures out that it would be a good idea to find a workable solution for each individual/team. Maybe they try to avoid common sense. :) Client has a marketing engineer who can do just about everything at home. He decided, on his own, that he did better in the office. Most do hybrid. For my client, I do what I can from home (50 miles), via VPN, and go down there when I have to. One hour train ride.
>64 There is never enough time to do it right, but there is enough time to do it over.
theoldfool wrote:
marketing engineer
There is something inherently wrong with this title! And I feel sorry for the poor bloody engineer that got dumped into marketing.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
theoldfool wrote:
marketing engineer
There is something inherently wrong with this title! And I feel sorry for the poor bloody engineer that got dumped into marketing.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
Seems oxymoron-ish to me as well.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
-
theoldfool wrote:
marketing engineer
There is something inherently wrong with this title! And I feel sorry for the poor bloody engineer that got dumped into marketing.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
You managing to stay above water level?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
-
I always feel these studies are very one-sided or leave things out. For my own employees, I have a sort of 50/50 rule, but I'm flexible. The thing I notice is, when we're at the office we talk, we laugh, we share knowledge, etc. They may not be the most productive days in terms of lines of code, or however you want to measure programmer productivity, but we're making progress, not just now, but also for the future. Like this guy who wrote a health check in .NET and I was like "Hey other guy, you should see this! We're going to build this into every application from now on, so you too." This sort of interaction is priceless and it's simply missing at home. Let's put it into numbers. We have a junior employee with a productivity of 6 at the office and 5 at home, because at home they can't ask questions like they do at the office. Worse case scenario, the junior has a productivity of 6 or even 7 at home, so they code bugs even faster, but let's stick to 5. We also have a senior employee with a productivity of 7 at the office, but 9 at home because the junior is not nagging him as much. Some simple math tells us productivity at the office is 6.5, but productivity at home is 7! If the junior has his way and isn't corrected, the "productivity" could even grow to 8!!! However, neither party learns something and the junior might get frustrated with their job and fall back to 4 productivity in the long run, (silent) quit their job, or unleash all kinds of horrors into production systems. That's longer term, of course, so for now we're happy with a productivity of 7 (or higher). When the senior quits you're left with a junior who never got to learn from his peers. I think you need a very well oiled development machine (with code reviews and everything) to be able to have the same kind of productivity from home that you have at the office. I think what hampers productivity is the "you have to be at the office five times a week" mentality. It shows an employer who doesn't care about their employees' wellbeing. Also, having long commutes is killing, that's why I won't soon hire people that live further than approximately 45 minutes away. That's why I like 50/50, it's the best of both worlds. You just can't convince me either one is all good or all bad. Any study that says otherwise, like this one, is flawed and drawing wrong conclusions. Case in point, this particular study studied the largest corporations America has to offer, but I'm just a small business in the Netherlands, which is (probably) c
Sander Rossel wrote:
The thing I notice is, when we're at the office we talk, we laugh, we share knowledge, etc. They may not be the most productive days in terms of lines of code, or however you want to measure programmer productivity, but we're making progress, not just now, but also for the future.
This!
Wrong is evil and must be defeated. - Jeff Ello
-
Just have to make sure people are at the office at the same time
Wrong is evil and must be defeated. - Jeff Ello
-
I always feel these studies are very one-sided or leave things out. For my own employees, I have a sort of 50/50 rule, but I'm flexible. The thing I notice is, when we're at the office we talk, we laugh, we share knowledge, etc. They may not be the most productive days in terms of lines of code, or however you want to measure programmer productivity, but we're making progress, not just now, but also for the future. Like this guy who wrote a health check in .NET and I was like "Hey other guy, you should see this! We're going to build this into every application from now on, so you too." This sort of interaction is priceless and it's simply missing at home. Let's put it into numbers. We have a junior employee with a productivity of 6 at the office and 5 at home, because at home they can't ask questions like they do at the office. Worse case scenario, the junior has a productivity of 6 or even 7 at home, so they code bugs even faster, but let's stick to 5. We also have a senior employee with a productivity of 7 at the office, but 9 at home because the junior is not nagging him as much. Some simple math tells us productivity at the office is 6.5, but productivity at home is 7! If the junior has his way and isn't corrected, the "productivity" could even grow to 8!!! However, neither party learns something and the junior might get frustrated with their job and fall back to 4 productivity in the long run, (silent) quit their job, or unleash all kinds of horrors into production systems. That's longer term, of course, so for now we're happy with a productivity of 7 (or higher). When the senior quits you're left with a junior who never got to learn from his peers. I think you need a very well oiled development machine (with code reviews and everything) to be able to have the same kind of productivity from home that you have at the office. I think what hampers productivity is the "you have to be at the office five times a week" mentality. It shows an employer who doesn't care about their employees' wellbeing. Also, having long commutes is killing, that's why I won't soon hire people that live further than approximately 45 minutes away. That's why I like 50/50, it's the best of both worlds. You just can't convince me either one is all good or all bad. Any study that says otherwise, like this one, is flawed and drawing wrong conclusions. Case in point, this particular study studied the largest corporations America has to offer, but I'm just a small business in the Netherlands, which is (probably) c
Sander Rossel wrote:
That's why I like 50/50, it's the best of both worlds.
All of that of course is the same sort of rationalization that others make for the same sort of rules. The difference is in objective versus subjective data.
Sander Rossel wrote:
We have a junior employee with a productivity of 6 at the office
Did you specifically assign a senior level employee to mentor the junior employee? Subjectively that would seem to be better. Also subjectively my take is that a senior that is assigned to a junior employee can expect as much as a 50% decline in productivity.
Sander Rossel wrote:
You just can't convince me either one is all good or all bad
As another case for increasing productivity what other specific steps have you taken? For example meetings: - Reducing the number of meetings. - Insuring that those in the meeting must be there. - Reducing the length of meetings. - Insuring that meetings stay on topic.
-
theoldfool wrote:
marketing engineer
There is something inherently wrong with this title! And I feel sorry for the poor bloody engineer that got dumped into marketing.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
Mycroft Holmes wrote:
that got dumped into marketing.
According to engineers and scientists, the Earth has come to an end, and humanity built three giant rockets to leave Earth. The first one, as the leading one, is for management and marketing : they are pioneers, the are to take the lead and show the way. The second one, is for engineers : they need to build everything up for settling the rest of the population when they follow up. The third one, a bigger one, is for the rest of the population. The first one is launched, and the management and marketing are launched into space. Then the engineers and scientists come out of the second one, and say: "- OK, they are gone, let's go back to a better life".
