Highly recommend the book "Voices From Chernobyl" by Svetlana Alexievich (she won the 2015 Nobel Prize in Literature partially for this work), it is an illuminating account of the Belarusian struggle and subsequent cover-up of the aftermath of the Chernobyl accident.
This is the same Robin Hanson that recently authored "The Elephant in the Brain: Hidden Motives in Everyday Life". His physics background makes for interesting economic analyses.
Couldn't agree more, it had me going back to the Algorithms book to refresh on most of part VI (Graph Algorithms). For those interested, Bellman-Ford is 24.1, and Dijkstra's algo is 24.3 in CLRS. Reviewing those helped step through the VisuAlgo link in the article: https://visualgo.net/en/sssp
Yes! And be careful and very picky about what you read! To quote a popular Quora answer [1]:
"If you really want to learn C++, I advise against any and all online tutorials and against most books. Without any kind of quality control, many professional book writers published many awful C++ textbooks that may be easy to read and sell well, but teach lies. Stick with the community-verified book list available at StackOverflow"
In other words, use the StackOverflow list to choose the right teaching material [2]. A Tour of C++ (Bjarne Stroustrup) has been a good refresher, with C++ Primer (Stanley Lippman, Josée Lajoie, and Barbara E. Moo) as the primary reference for further clarification. Also use GeeksForGeeks and LeetCode practice problems.
The biggest EMR company was Epic and uses Mumps [0]. However, they are losing share to Center and others [1], so this formula will only work for a little while longer.
If you have ever worked with epic, they offer "managed" solutions, which you either do the epic designed way, or don't go epic... They have enough market share and business to dictate how things will work in a hospital env
Confirmed: The stars in the background behind Comet #67P are in Canis Major: the cluster NGC2362 "falls down" past the limb at top-left; sparse cluster NGC2354 & the star 27CMa are also in the field.
Programming challenge: filter out (or otherwise remove) the sky from the video to isolate the comet surface for better analysis.
This can also be driven by unreasonable reporting requirements. Say you go against your boss and deliver X,Y, and Z in the first month, and during the second and third months you cannot deliver anything tangible because you have uncovered larger and more complicated problems that take longer to fix.
Often in these situations the funding company would critisize you for underdelivering, since you have obviously demonstrated that you are capable of delivering X,Y, and Z in one month, but have since not contributed anything tangible in the following two months.
On a graph, you would see a spike for the first month, and a plateau for the 2nd and 3rd. Execs do not like seeing downward sloping trends, and middle managers will do everything to avoid them since their job literally depends on them, hence your bosses boss merely understood the responsibilities and requirements of all stakeholders involved.
A meaningful consulting relationship starts with detailed, reasonable, and sane reporting guidelines, which is very difficult to achieve and don't always work well with a programmers mentality.
Do you have any pointers/references for getting started with Software Defined Radios? i.e. the state of the art software, hardware, and common hobbyist applications? Any open source communities?
Schematiq - https://www.schematiq.com also handles source control for spreadsheet and a lot more. The platform is about making sheets enterprise grade applications -
regression, testing, CI etc and introduces new features to simplify spreadsheet logic.
I remember I wrote not long ago a VB Macro for Excel, where all the VB code inside was imported/exported, git pull/commit+push, etc, all of a button push.
It became an instant hit in that company and I short of a medal :).
Note that Pathio has been relaunched as https://www.xltrail.com - it supports the standard Git workflow and every Git system (GitHub, Bitbucket, Gitlab etc.).
My pet theory is that the long-term reasoning for artificially limiting the number of residencies/medical school spots is to avoid an oversupply of healthcare professionals after the baby-boomers die off in 15-20 years.
Sure, there is tremendous strain (and consequently profit to be made) in the system now, at the expense of overworked doctors with limited interaction with their patients. But if the supply of doctors met market demand _right now_, in 20 years there would be an over supply. An over supply of doctors would introduce a new set of problems associated with lower salaries and eventually lower quality of care (see Soviet Union). So in a way, this artificial market manipulation of the supply of doctors is forcing innovation and timing the population market, and betting on medical advances that will eliminate many doctor visits through preventative medicine or computer asssisted diagnostics.
Essentially the AMA is lobbying to prevent a scenario that created the artificial STEM shortage myth in the 1990's that new career scientists have still not recovered from.
How did having too many doctors cause an decrease in quality of care in the Soviet Union?
And the AMA is lobbying for decreased slots because it increases their salary. American doctor's pay is way out of line with the rest of the developed world.
