|
|
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
|
|
|
|
|
Not always. Cats have a habit of adopting humans.
|
|
|
|
|
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) completely different.
|
|
|
|
|
I agree 50/50 is a win/win
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Just have to make sure people are at the office at the same time
|
|
|
|
|
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!
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
You managing to stay above water level?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
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".
|
|
|
|
|
I successfully upgraded my PC's storage with an additional 4TB of 990 Pro goodness.
It almost didn't happen. I have a 4080FE GPU that's 3 slots wide. It completely covers the release lever used to pop the GPU out of the slot. You have to get under the card to get at the lever. You can't come in from the side because of the NVMe enclosures surrounding the slot.
Effectively you can't remove the NVMe shields without removing the GPU and you can't remove the GPU without removing the NVMe shields. I think Alice Cooper wrote a song about this.
When I say you can't, I mean physically impossible except perhaps if you remove the CPU cooler and RAM and come at it from the back, but that means reapplying paste as well as disassembling every major component on the board. A double wide GPU took me an hour with a couple of tools. This triple wide one simply wasn't happening.
So there I sit, scratching my head. Eventually I figure "ah hell, let's do the obvious first" - and after unscrewing the rear plane of the card I simply tried to lift it straight out of the slot, release lever be damned.
It came right out, like getting ready to kick a door in only to find the knob turns freely.
The mystery of that quickly sorted itself, as there was the lever, just hanging out on the motherboard, laying next to the PCIe slot it belonged to.
It isn't visibly broken. I think it just worked its way loose either removing my old 2080TI GPU, or installing this new 4080 one.
I could reinstall the release lever and effectively hermetically seal my machine as a result. You could weld the hood of your car shut. Why not?
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
You should mention the motherboard, otherwise someone may buy it accidentally...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
It's a good board. The issue is it's mATX. There's no room for anything. They packed a gaming board into mATX form factor. Anyway it's an ASUS Rog Strix. Just get the larger board. They have quick release.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
I know that motherboards must be build to be optimal, but DAMN, some of those motherboards are not meant to be maintained.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
The price of mATX form factor plus gobs of features.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
in that case, size DO really matters!! 
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
One day I will recount the adventure that has been buildin my last PC, after 7 years that I didn't build PCs.
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
The shortest horror story: On Error Resume Next
|
|
|
|
|
That was my experience with this machine!
I got picky, and none of the prebuilt starter systems I'd usually buy were geared for what I wanted, which is I wanted to build a machine with a 55" 4k fancy interface and have blistering C++ compilation speeds for around $3000USD. I did that, even though it would have been cheaper to build up a starter. The issue is I couldn't max out my ram speed if I did that, or go with 990 Pro NVMes, and I'd have to sacrifice bleeding edge performance, or otherwise replace parts right out of the box. None of the prebuilts had mobos with the options i wanted, and I fell in love with a particular chassis as well.
It was WORK. I was sweating clearances on my mail order parts until the day they all arrived. Was also worried about thermals because I'm on air, but it all worked out. Did my anxiety issues no favors though. 
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
You shouldn't weld the hood on the car because eventually you need to change the oil and the opening to put new oil in is under the hood. Hoses and other stuff wear out too.
I guess the delay of Apple cars is probably a good thing because knowing them, they WOULD weld the hood shut just so you'd have to but a new car after a while.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
I’m begging you for the benefit of everyone, don’t be STUPID.
|
|
|
|
|
That was basically what I was getting at. If I put that clip back in I can't service my computer if i need to upgrade the GPU or if the NVMe fails or something.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Offline, I'm working on the restoration of a vintage industrial diesel railway locomotive. In the cab, a horizontal shaft extends the width of the cab, connecting a brake lever each end to a single air valve. The shaft is held by three brackets to the cab front sheet. Two of the brackets allow the rod to rotate freely, as it should; the third (central) one is rusted solid. Try as I might I can't free it, and in order to do so I need to unbolt the bracket so that I can whack it really hard with a big hammer and get it to rotate on the shaft. There's a bolt running from inside the cab, through the bracket with a nut on the outside of the cab. To get to the nut to release it, thereby freeing the bolt so I can whack the bracket, I need to remove not only the bonnet sheeting, but the fuel tank. The tank holds 50 gallons and extends the width of the bonnet - and is therefore huge; takes 4 people minimum to move it. A fuel pipe runs from under the tank to the fuel valve/injectors. I could undo it that end, but to get to the connector I'd need to remove further bonnet sheeting and then unbolt the inlet manifold (weighing around 50lb) and the air filters, and then the fuel injector; alternatively I could undo the pipe directly under the fuel tank; but the pipe is too close to the top of the flywheel to get a tray underneath to catch spilled fuel; so I'd need to take the flywheel off. That means dismantling the bearing assembly that holds the drive shaft, and then undoing the flexible coupling in the transmission.
What I don't understand is the amount of design and planning that went into the assembly of all this over 60 years ago. The shaft connecting the two brake handles had to be done before the transmission and fuel systems had been fully installed. WTF?    And that's just one of several such conundrums.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
