... being physically present increases both the communication bandwidth but also the ease of communication which means that things get discussed which would not if the only meetings were virtual....
I actually agree with you on this. I currently work from home one day a week; and, for my job, doing that five days a week would not be the best allocation of my time. I do need to meet with people to discuss projects occasionally, and that does work better face to face. However I am *supposed* to be coding the majority of the time, which I invariably am able to focus on more when I'm at home - for one thing, faculty aren't popping into my living room unannounced, like they do at my office (sometimes to ask simple questions, and sometimes apparently just because they're bored).
In an ideal world, I'd probably be telecommuting three days a week, which would result in my getting more done... but one day is still better than none.
My experience with the Perl hate is it's usually from younger people (by which I mean anyone under about 40).
I suspect much of the perl hate is from people who haven't actually learned perl but at some point in time were asked to update or troubleshoot a perl script.
There are languages which a "non-speaker" can often get the gist of and troubleshoot existing code to some degree. Perl is not one of them. Then again, those easy-to-read languages seem to give novice coders a false sense of adequacy - which may be the reason we see so many security exploits in code using them. When was the last time you saw a perl exploit?
Oh, haha... I was referring to the subject line rather than the post’s contents - but you’re right, there is also a superfluous comma in the post itself.
In 50 years, hopefully we will have done away with daylight savings time completely and this topic will be dead, but if we have not, Daylight Savings Time will be the correct way to say it.
Perhaps, at that same time, it will also be grammatically correct to insert superfluous apostrophes willy-nilly.
I can see the (different) security implications of either a front-end or back-end hook, so I'm not sure if Mozilla would ever implement such a scheme, but some way of integrating third-party password managers in a better way would be nice.
Firefox on OS X (aka macOS) has worked this way for years - it ties into the built-in encrypted keychain. It started out as a plugin, but IIRC it's now part of the core (I stopped using Firefox a few years ago, so it's possible I'm remembering incorrectly).
So it would seem the hooks are already present - it's just a question whether they're written in an extensible way, or if it's a horrible kludge written specifically for the OS X Keychain.
... being physically present increases both the communication bandwidth but also the ease of communication which means that things get discussed which would not if the only meetings were virtual. ...
I actually agree with you on this. I currently work from home one day a week; and, for my job, doing that five days a week would not be the best allocation of my time. I do need to meet with people to discuss projects occasionally, and that does work better face to face. However I am *supposed* to be coding the majority of the time, which I invariably am able to focus on more when I'm at home - for one thing, faculty aren't popping into my living room unannounced, like they do at my office (sometimes to ask simple questions, and sometimes apparently just because they're bored).
In an ideal world, I'd probably be telecommuting three days a week, which would result in my getting more done... but one day is still better than none.
No, the REAL question is - does this ex-employee have a Patreon?
Found the manager!
Everyone keeps suggesting audiobooks but I simply cannot focus on a spoken novel while driving.
Not everyone is like you - which is why traffic deaths have been going up over the past several years, after steadily heading down for decades.
Fortunately when one of those inattentive drivers meets my train, the train wins. Every time.
I still use perl quite a bit, as have my co-workers past and present. So... I see perl written by other people all the time.
It's the year of the ISS Linux Desktop!!
Given LastPass' track record, perhaps we need a companion article:
"LastPass Reveals the Threats Posed By Using LastPass in the Workplace"
My experience with the Perl hate is it's usually from younger people (by which I mean anyone under about 40).
I suspect much of the perl hate is from people who haven't actually learned perl but at some point in time were asked to update or troubleshoot a perl script.
There are languages which a "non-speaker" can often get the gist of and troubleshoot existing code to some degree. Perl is not one of them. Then again, those easy-to-read languages seem to give novice coders a false sense of adequacy - which may be the reason we see so many security exploits in code using them. When was the last time you saw a perl exploit?
Manzierre!
This subthread reminds me of our local Puget Sound area summer:
https://www.youtube.com/watch?...
On a side note - those of us who garden in this corner of the US often look to England for guidance, given the similarities in climate.
Oh, haha... I was referring to the subject line rather than the post’s contents - but you’re right, there is also a superfluous comma in the post itself.
(Insert your own joke about there being two days of actual summer in the UK here).
Oh, you guys have gained a day! Is that because of global warming?
Do NOT give them any ideas!
I think we should be on DST year round. I want my sunlight at the end of the work day instead of the beginning.
Id give you all my mod points, if I had any.
(Sorry about the missing apostrophe - a guy further up the page stole it)
In 50 years, hopefully we will have done away with daylight savings time completely and this topic will be dead, but if we have not, Daylight Savings Time will be the correct way to say it.
Perhaps, at that same time, it will also be grammatically correct to insert superfluous apostrophes willy-nilly.
People will complain about it, though - just like they did when AT&T shut down its 2G towers.
... says 2008 me.
The Japanese stakeholders were unwilling to start wearing pink shirts.
How is closing the door to new subscribers, killing off the program?
I imagine the author thinks Microsoft is going to follow Google's playbook here.
I can see the (different) security implications of either a front-end or back-end hook, so I'm not sure if Mozilla would ever implement such a scheme, but some way of integrating third-party password managers in a better way would be nice.
Firefox on OS X (aka macOS) has worked this way for years - it ties into the built-in encrypted keychain. It started out as a plugin, but IIRC it's now part of the core (I stopped using Firefox a few years ago, so it's possible I'm remembering incorrectly).
So it would seem the hooks are already present - it's just a question whether they're written in an extensible way, or if it's a horrible kludge written specifically for the OS X Keychain.
Use a photo of your Yubikey!
Wish I’d thought of that - I used my pet Boa Constrictor.
While still not a fortune, $538 was worth more in 1938 than we might initially think - roughly half a year’s income.
Not to mention that, whatever the object is, you’ve got to have it with you at all times - so pick carefully!
Really, Stanford? Are you going to look at their hopes and dreams next?