|
Never had the pleasure to work with COBOL myself 
|
|
|
|
|
As it seems (I can't say, that was before I was born), some people would call that luck
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Since the birth of the personal computer, futurists have been predicting the death of the office. Works for me
|
|
|
|
|
Quote: Every morning, we have an all-staff video conference on GoToMeeting.
I found the cause of the productivity drop.
|
|
|
|
|
Quote: the death of the office
Bring it. No cubes or, even worse, open concept (except for the nomenklatura, of course). No commuting. Quality coffee. Farting when and wherever. How could remote work possibly suck? It's even finding its way into surgery.
|
|
|
|
|
Greg Utas wrote: How could remote work possibly suck?
I don't say it sucks, but it can be "not so nice" too, depending on many things.
First and most important. The person. Although I like the points you have made, I am not the "HomeOffice guy" (yet?).
Not having a dedicated room for "HomeOffice" is a PITA. I have to share my desk for private PC and Work-Laptop.
Being at home, you move way less than going to the office. Around 40% of my daily steps are walking from parking to office, office to restaurant, restaurant to office and office to car. I know you can compensate doing other things because you are supposed to have moree spare time by saving conmute, but having little kids and a working wife... you can forget it.
Once I concentrate, I don't care where I am, but I find it a bit more difficult to concentrate at home than in the office, there are more potential distractions.
Another important point (at least for me is pretty important), working in the office it is way easier for me to leave the possible problems / stress behind me, switch off and cool down before getting home. Working at home this "sacrosantum / clean atmosphere" feeling is not that clean, and I don't really like it.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Science sucks, and remote work rocks.
|
|
|
|
|
Developers and their surrounding application teams need to make daily decisions about what to build and how to build it, and they need to do them on their own. Managers deemed obsolete?
|
|
|
|
|
Let's build a tool to plan meetings to decide what to build and how. Oh, wait...
"Five fruits and vegetables a day? What a joke!
Personally, after the third watermelon, I'm full."
|
|
|
|
|
A physics paper proposes neither you nor the world around you are real. "Reality is that which, when you stop believing in it, doesn't go away."
Heavy, duuuuuude.
But I have to ask, "And?"
|
|
|
|
|
The simulation hypothesis, which the article mentions, is interesting and plausible, but this is bollocks. And neither of them is relevant to living life.
modified 28-Apr-20 22:01pm.
|
|
|
|
|
And?
I hit the stop button a minute or two ago. 1432 requests, 15.3 MB transferred, 38.3 MB resources.
I dont even care what the rest of the article says. That link should come with a complementary high-vis vest and a hard-hat.
Correction. It's now up to 1535, 16.8 and 40.1 
PBS Space Time - I could have had a video for this much data. Thanks for the fun!
|
|
|
|
|
I agree. Bollocks. Love the OP's comment, though (about Reality). I use that all the time with my science-denier friends.
|
|
|
|
|
With this release, Intel wants to make it easy to update your drivers between the OEM-provided drivers and its generic ones, without losing the custom features the OEM driver provides. Because two bleeding-edges are better than one?
I barely ever want to install the OEM ones for fear my machine is going to go south.
|
|
|
|
|
Just wow. This definitely takes the brass pair award.
modified 28-Apr-20 22:02pm.
|
|
|
|
|
In this article, I will walk through how to call some simple C/C++ and Rust code from C# in a WebAssembly app. Why create a solution in one language, when you can use them all?
OK, the intent isn't likely to use them all. One demo is better than four. I guess.
|
|
|
|
|
W in T actual F?! It's like a dog walking on its hind legs. It's not elegant or useful, and it's a miracle that it can be done at all.
modified 28-Apr-20 22:02pm.
|
|
|
|
|
There are two phrases which came to my mind when this weird idea popped into my head. “Duck Typing” and “Rubber Ducking”. That’s two more duck based terms than many industries have, excluding perhaps zoos and veterinary practices. Really. What the duck?
|
|
|
|
|
He forgot the silent duck, which so befits management that commits to unrealistic schedules.
|
|
|
|
|
|
It's always a good day when I learn something new or help someone else do the same. 
|
|
|
|
|
I remember two different "ducks" in my adult life
When I was in boot camp, our DI told us we were eating Duck. Cool I thought, the mess hall was making something nice. This was not so; as what was meant was, "We duck in, we eat, we duck out".
In software development, I suppose patches could be Programming Duck; in that we open a project, slap in or a fix a line of code, and recompile successfully in a few minutes.
The second reference was in the customer service industry. I do not recall the context but it went with the saying, "Why be a duck when you can soar like an eagle".
In software development, I guess this would analogous to doing the Programming Duck as a bandage to fix a symptom, and "soaring like an eagle" would be to go in and fix the underlying issue.
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
What makes a good design principle? One aspect that everyone seems to agree on is that a design principle shouldn’t be an obvious truism. "I don't believe in princerple, But, oh, I du in interest."
|
|
|
|
|
April 2020 marks 55 years since Intel co-founder Gordon Moore published 'Cramming more components onto integrated circuits', the paper that subsequently became known as the origin for his eponymous law. And I didn't get twice the gift density for it this year
Sorry, too tired to come up with a better one. I think it's time for my early-afternoon pre-late-afternoon nap.
|
|
|
|
|
We try to follow experts' cybersecurity and privacy recommendations but quite often many of us do so halfway or we give up. Lazy wins
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
