I don't think the jury is still out. I have worked from home off and on for decades. In my current job, I was going into the office every 6 weeks until recently (haven't been in the office in probably 6 months). Since that also involves flying there and back, one week in the office is about as productive as one day at home. I'm not being facetious about that - I'm just considering burn down and tickets that actually get closed out.

While I do understand the desire to have face-2-face whiteboarding sessions, that's rarely what we are doing.

We use conferencing (Hangouts and unfortunately also WebEx at the moment) daily for an international team. While it may take a minute or two to start a chat online, when onsite it usually takes much longer to find each other AND an available room. Half the time, we crowd around one monitor anyway.

However, the less distracted assumption is also not really all that true. Even ignoring things going on at your own house (deliveries, pets wanting fed, etc), you still get constant distractions from meeting invites and slack conversations. The only real difference is you are less likely to be pulled into a meeting or an off-site lunch.

You'll probably find that how you manage your project has a bigger impact than a lot of that. How many administrative meetings are you having? How many scrums and retrospectives and grooming sessions and artificial deadlines etc?

All that being said, I do tend to turn down onsite jobs anymore because I don't want to waste 2 hours a day of unpaid time commuting.

If someone like ShapeShift wanted to challenge it, they could show that they had prior art in effect at the time of filing. They would most likely have to outspend BofA on lawyers, which is unlikely. In addition, BofA only has to have 3 points of differentiation from a company like ShapeShift - even if they already had a patent - for it to be a valid new patent. That could be something as small as whether or not to display a QR code on the screen.

The whole system is broken and favors large corporations over the individual inventors.

I started first grade in 1979. Computer programming was a required class for ALL students in elementary school. We too started with pseudocode and Logo (in 1st grade). Since I've been programming for 38 years and it's currently my career - I definitely think it was effective for me.

Your best bet is to start with the site supporting the firmware flavor (DD-WRT, OpenWRT, etc) that you want to run. Their site will be able to tell you which models currently work with their current firmware. When I went to buy my router, they had screenshots of the packaging to help identify between v1 and v2 - which the casual buyer might not have noticed. Support levels on them were different. If the shiny new router mentioned at CES isn't supported yet, you may need to rethink your plan or do a lot more work. The sites usually also include information like how you might have to flash to version 1.1.9 before you can downgrade to 1.1.8 again, etc.

using spaces simply because the code is consistent for everyone

That's a false assumption.

My father was legally blind. We were sharing code remotely, using spaces, and he could not differentiate the gaps in the same way that I could. Every commit he would change my 2 or 4 spaces to 8 or 16 spaces. Every commit I would change it back, because it was horrible for me. We eventually switched to tabs, and the constant code reformatting stopped because we could each choose how strong that spacing looked for each of us, independently.

At work, they are currently enforcing that we use spaces, so I am.

I would no longer choose to do so on my own project because I know that it makes the code inaccessible to the handicapped. I am quite honestly surprised that this argument goes back and forth. The ADA should probably just start suing companies for being non-compliant.

I just never need it, or never have the right amount. It's more inconvenient.

However, in much of the country I could imagine there being a concern about it being taken. Jon Oliver episode on Civil Forfeiture:
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fyoutu.be%2F3kEpZWGgJks

ESXi does have a very similar mediated passthrough. Here's a quick google hit for installing vgpu on ESXi. The two approaches are approximately equivalent in functionality, and should be similar in performance.

In a nutshell, there are four ways to do high-quality graphics in a virtual machine ... you can fully emulate a graphics card (which nearly everybody does, but it's slow); you can forward DirectX/OpenGL calls to the host (which works great for Mac-on-Mac, and not much else); you can directly pass through either the entire card or part of a card (via SR-IOV), which gives full functionality/perf but can't be shared; or you can use a mediation layer to mostly pass through but implement some interesting bits in software (vGPU, an nVidia trademark so you won't see many others using the term). VMware's approach requires custom code for each graphics card and only works with nVidia; this KVM approach is generic across graphics vendors, presuming your hypervisor is Linux/KVM (which rules out ESXi or Hyper-V).

I don't need paper for work. It probably helps that I telecommute, so there is never anyone handing me a piece of paper. When I travel, tickets are all on my phone. Timesheets are online, invoices are online, paychecks are direct deposit. The closest I get to paper is random PDFs.

VMware has shipped with hypervisor-level memory deduplication off by default since 2014, precisely because of this style of attack.

Being secure against this sort of attack has been the norm for years now.

The thermostat continues to function even if power goes out or if you remove it from the wall. It charges an internal battery from the wiring.

The Nest does charge from common (or other wires if you prefer). Not sure what the actual bug was that caused it to drain so fast. I'd assume some tight looping.

This is exactly what happened. A medical device refused to work, claiming it was too cold. I went to check the thermostat and it wouldn't function. I checked the mobile app and it said that it had lost connection with the Nest 5 hours earlier. I plugged it into USB for about 1/2 hour so that it had enough of a charge to startup the heater.

I had considered hot-wiring the HVAC behind the Nest panel, but my HVAC has protections against that.

It's a little too bad the USB port isn't external so that I could attach a charger to it while it was still on the wall.

So getting a program to work right with SELinux takes a RHCE? And elevated access so you can drop the context rule in the right secure place?

As one of the other posters noted here, the problem isn't configuring SELinux right on one system. The problem is that configuring it right is done differently on each user's different system - so you either have to write the configuration 3+ times (RPM, DEB, and pick some other common format, then listen to Linux users gripe about how you didn't support THEIR package format), or you have to write some sort of complicated setuid-root shell script that does the right thing. And to install this silly game (which doesn't require root), you have to be root! Remember how Windows got into a lot of trouble about how you had to be Administrator to install anything? But when it's SELinux with the same requirement, we are supposed to call this a good thing?

SELinux is a wonderful system - IF you can enumerate all permissions needed by all software that will ever be installed on the system. Which is true only for toy OSes or base OS installs or for people who have solved the halting problem. And that's why any non-trivial software immediately suggests turning off SELinux - the defaults are too restrictive for real-world software (JIT is only allowed for Java / Browsers / other things the SELinux rule authors have seen before), and you need to really know the system well to properly alter the configuration while still maintaining security. The point is, installing new pieces of "normal" software is a major piece of functionality for the OS, which means the OS needs to handle this itself and configuring security is not something that should be foisted upon the software being installed. Really fancy software - e.g. database servers and such - may need to carry a security configuration with it. But come on - a game needs security configuration ?!?!

(And before the Linux people skewer me for saying Windows is better - Linux is perfectly fine. It's SELinux that is ... difficult.)

This, and the meta point: the fact that the poster of this "Ask Slashdot" left the conversation WITHOUT having an answer to those questions is itself indicative of poor communication skills. A good communicator will convey that sort of information regardless of how poorly his report listens; a merely average manager will convey merely average general principles and it's up to the report to pull out more information. (And a poor manager will give non-committal evals then fire somebody without warning).

I'm reading the OP as "my manager told me I had poor communications skills. I didn't understand what he meant, so I nodded my head, said I'd work on it, and walked out." Thus proving the point. (Though OP gets some points for at least asking somebody a.k.a. Slashdot. It's the wrong somebody, his manager or his peers would be better choices, but Slashdot is better than nothing.) If the manager can't explain to your satisfaction, go to the next level up the chain and say "I got this feedback from my manager, we talked about it and I didn't understand, can you help me understand?" (But no further, and don't blame your manager.)

I'm reading between lines some here, but what I'm seeing is more conflict avoidance than anything else ... OP is more comfortable asking online / anonymously than face-to-face. I'm an introvert, I feel that too. I've just spent many years breaking that habit, because I realize I'm much more effective face-to-face (read: we all get what we want faster) and I've found online conversations less effective (written conversation has a tendency to include every argument, and ends up coming across very antagonistic).

But let me put a positive spin on things: poor communication is expected of an average, very junior person. This managerial feedback should be viewed as "improve this to get promoted", not "improve this or get fired". (Well, except at a start-up, where being merely average is cause for firing.)