Dude it is 2017. Word lost because Microsoft is actively carrying the ball for the other team toward their own end zone now. Deal with it. The world runs on iOS and Linux/Android running Google Apps, Facebook Apps, and Twitter, Tinder, etc.
First and foremost, when a customer says they're down, try to ping other modems in the same neighborhood. If those are down too, roll a line truck. Do not claim it must be a problem at their house.
Re-emphasize in training, if any light other than network activity is flashing on the modem, it is not a problem with their computer, don't try to sell them on paid Windows support, especially when they say they don't have Windows.
If the customer is using words you are unfamiliar with such as traceroute or ping, just elevate the call to someone who understands the problem.
You're not making any sense. Try later after you sleep Saturday night off.
Even if there is disagreement, the bug/not-a-bug decision is in part made based on attitude (see NIH), and is reflected in the code.
Because it IS a bug, but by stamping it not-a-bug, it remains in the source.
In Linux, that's called ALSA.
Oddly enough, yes in a sense. Every refusal to acknowledge a shortcoming, every NIH, every not-a-bug is reflected in the source.
The capital expense for solar is significantly lower than coal - and it is much quicker to build. If you start building a coal plant and a solar plant of equal capacity at the same time -the solar plant will be done in 2 years, the coal plant is a minimum of 7 and 10 is more common. The solar plant will also cost a fraction. Every coal plant in Africa was built by the government - most solar plants were privately funded (because it's a much more sensible investment for a private investor).
And of course, solar can be done economically at any scale - people stick it on their roofs to produce for one family. And to really hammer how cheap it is - my dad is an electrical engineer and he did the math, if you BORROW the money to do that, the money you save on power bills will be enough to pay back the loan AND the interest before you even need to replace the batteries - and in fact will pay for the replacements and STILL make a profit.
They run Chrome OS. Basically an extension of Google into your lap. Like android phones are a extension of Google into your hands and pockets.
Complaining that Google is observing it's users is like complaining that water is wet. Observing users is Googles freakin business model, that's what they earn money with. That's why you get all the neat stuff including cloud storage basically for free. This is also the reason Google is not another MS or Apple. They are a different league. They don't care what your device costs and which software it runs, as long as you use Google. Plain and simple.
And because of this, Google could offer services for minors no other company could. Like, for instance, warning parents when the child is communicating with a person that is obviously an unknown middle-aged man posing as a teenager.
I guess the EFF get's the Captain Obvious Award for stating that Google observes it's users.
... and I'm usually judged 7-12 years younger than I actually am (47). I even feel that way too. Given, I also dance a lot. But I combine my biking with PT, so that evens it out.
I offen get angry seeing avalanches of SUVs and full sized cars with only one Person in them. Germanys cities are clogged to the Brink with Cars and it's a freakin' Pita for everybody. We even start seeing the push for larger Bike Infrastructure at federal Level
Everybody I know who uses the bike as a main means of transport is a healthier happier person for it, including myself. We have too many cars. We need less better cars and caresharing at national level. And a private car limitation for cities.
Everything would improve.
My 2 eurocents.
They invest the time and the learning to master a workflow. They expect a payoff from this investment in their ability to use these workflows to achieve other ends. When you mess with a workflow, you negate that investment. They have to spend time learning and mastering a workflow all over again before they can apply it toward their actual goals.
Nobody uses software "to be using software" or "for a good experience." They use it to get things done. If they have to spend two weeks mastering a new workflow then your improvements had better deliver a multiple of that value in return, or they're going to come back with "that's cool, but it would trip me up for all of my muscle and click memory to be invalidated."
People aren't averse to improvements. They're averse to evolutionary improvements that cost more to the user in practice (time invested and mistakes avoided) than they deliver on the other end. "Small tweaks" often fall into this category. Some dev moves a button to a more "logical" placement and for the next two weeks, the users lose five or ten seconds every single time they need to use it because their absent minded clicking—absent-minded because they're focusing on what they're really trying to accomplish, not on 'using the software'—keeps ending up in the wrong place vs. what they're accustomed to.
Dev says "BUT IT'S BETTER." User experience is actually that of being irritated and not getting things done as efficiently as usual, so their response is "IN PRACTICE, IN THE CURRENT CONTEXT OF MY LIFE, NO IT'S NOT."
Riches cover a multitude of woes. -- Menander