Sure it is, if you don't understand economics, which few Merkins do. The evidence is right in front of us.
jdnewmil
Agree. For clarity, the circuits that show the low-voltage status are much less hungry for current than the circuits that measure weight. So no, having enough battery to report low voltage does not imply that there is enough to make an accurate weight measurement.
Clear and Clear Entry.
The better option is to use an RPN calculator as Hewlett-Packard used to make. Then the back arrow button just eliminates one digit at a time.
the ones that lost? those generals?
Republicans don't mind a troubled economy because they believe they are avoiding worse pain. Democrats are more willing to increase the cash flow at all levels of the economy. There really isn't much to be surprised at here.
Of course, they often don't present their positions that way, but lying is like breathing to all politicians. Trump kind of abandons any pretense otherwise.
Read other people's code... particularly code by experienced developers. One good way to do that is to single-step debugging through the test code in a well-known package, stepping into the code being tested.
I suppose if you don't know how test frameworks like pytest work, tackling how they work and how to do single-stepping with some toy example code will be a prerequisite for the above, as will spending some time studying how packages are made. (The latter may seem unattractively tedious, but the knowledge will pay off even if you never become an expert at making your own packages.)
These exercises are very likely to expose weaknesses in your understanding of all sorts of things. Be patient and keep studying!
When you come across some Python code for something written 5 years ago and they used four contributed packages that the programmers have changed the API on three times since then, you want to set up a virtual environment that contains those specific versions so you can at least see how it worked at that time. A small part of this headache comes from Python itself mutating, but the bulk of the problem is the imported user-contributed packages that multiply the functionality of Python.
To be sure, it would be nice if those programmers were all dedicated to updating their code, but with hundreds of thousands of packages that could be imported written by volunteers, you can't afford to expect all of them them to stop innovating or even to continue maintaining past projects for your benefit.
If you have the itch to fix something old so it works in the latest versions of everything, you have that option... but it is really hard to do that if you cannot see it working as it was designed to work when it was built.
Published in the Journal of Improbable Research?
I didn't say it was unobtainable. But it might look/behave quite different than the tools you are currently using.
As for Microsoft Exchange, I only use that for work, and my employer would not allow me to connect from my personal machine anyway. I am not saying that you that you have to give up your favorite tools... but I am saying that it you are putting up so many fences then you might as well stay with what you have.
No.
If you ever so carefully paint yourself into a corner then the corner is where you will be stuck. How badly do you want out of your corner?
There are FOSS and SAAS options that could work if you wanted them to... but whether they will depends on you.
Meat eaters trying to become vegetarian for ethical reasons often fail because the "un-meat" options out there don't meet their standards. Success almost always requires some letting go and re-adjusting. If you are not open to that then don't force yourself to put up with something you don't really want.
I think you meant "propagated".
How do you monitor your email functionality? How long would it be before you noticed it was offline? What about paying for and configuring the new email server?