Hacks are ok with web and app deployments where you are able to patch and fix to your heart's content and the damage is not life threatening.
I have worked with the medical industry, the amount of formal validation and verification that goes through on software is insane compared to what we have in the "move fast and break things" world.
Even if it is "temporary" and "desperate" I would stay away from this mentality as much as humanly possible.
Different circumstances with different levels of risk, require the ability to adapt.
Nobody is suggesting 'sharing ventilators' would be normal practice because in normal circumstances we want to make sure that equipment is 99.999% reliable.
But as you imply, this requires extensive testing and regulation. Within these regulations are also significant safety margins that can be exploited if conditions change. If we can multiply the usage and maintain 99.99% reliability, then this is probably a risk worth taking.
Also - if you've worked in the medical industry, you know how vastly overpriced and bureaucratized everything is.
The situation of 'not enough ventilators' is literally happening right in front of us, and it is causing death.
The risk tolerance for utilizing the gear in such a manner is such that it may very well be possible to create better outcomes.
The individuals involved are medical practitioners who are well versed in the equipment, procedures, and inherent moral dilemmas, they're not fools.
This is exactly the kind of procedural innovation required in times of crises - hopefully, a few doctors and especially the Engineers from the manufacturer can be involved. The people who built the gear may be able to give a much better articulation of the actual risks involved, and they may even be able to mitigate, for example 'the risk will be power consumption' or 'the risk will be this specific valve which could wear and break' thereby implying the 'new operational procedure' would involve daily checking of said valve etc..
The world is facing crises we absolutely must be adaptive while trying to quantify risk and outcomes.
>Also - if you've worked in the medical industry, you know how vastly overpriced and bureaucratized everything is.
Quality guy here,though not in medical devices... Yet. Still trying to get up to speed on all the regulations; but I know enough to be able to vouch for some of the bureaucracy around the industry.
The risks in medicine being what they are, when launching into any novel space, there is simply no substitute for A) data and B) audit trail.
Your data varies from lot numbers of source material from suppliers (contamination happens), batch numbers of parts (and revision numbers of the process involved in making that batch) from manufacturers, to serial numbers matched up to individual patients in order to be able to implement some form of high-level statistical process control, and rapid intervention when things go wrong in order to figure out why, what you can do about it, and who else may be at risk. No one wants to be the one told "whoops, someone goofed, and that thing we put you on is trying to kill you," anymore than anyone in the chain from treatment inception, to installation wants to hear that they missed something, and even worse, get caught not knowing what to do about it.
That means paperwork, signalling mechanisms, and procedures involved with marshalling whatever response is to follow, which is not at all a trivial process to orchestrate, and while all of us wish there wasn't so much bullshit, there are plenty of examples where "falling asleep on the job" has led to catastrophic outcomes.
I can't necessarily say I that justifies the overriding though. The markups are ridiculous, but without access to the books, I can't really discount it either.
In Northern Italy patients are being turned down on triage because there is not enough treatment capacity. They go home and many of them die.
Just like you would use a sweaty t-shirt over an open wound in a life or death situation if there is no certified sterile bandage at hand. The calculus is different.
On more than one occasion I have "broken the rules" or Macgyvered my way out of a life-threatening situation (for my patients), either with equipment or drugs. This is a crisis. Our systems aren't working fast enough to cope.
So if you end up in a situation where a doctor is deciding whether to put multiple people on a ventilator, is the idea that they would certainly pick you?
You don't seem to be reacting to the situations that the idea addresses, situations where there is an immediate shortage of ventilators.
Such a foolish statement, you clearly don't understand the number of lives lost due to ventilator shortages right now or you'd delete your comment in embarrassment. Doctors should be using absolutely any method available to them to maximize lives saved. You don't need to "have worked with the medical industry" to understand this perspective.
Medical facilities in Lombardy will “soon” be unable to help new coronavirus cases, regional Gov. Attilio Fontana said Wednesday, as he urged everyone to stay at home.
Use the language your team is familiar with! If it is PHP don't hesitate just because it is not "cool"..
PHP was a great tool back in the day and today!
PHP with a decent framework like Laravel [1] or Zend Framework [2] really works well and addresses all the features that you have listed (except the last 2).
Uniquely among modern languages, * PHP was born in a web server *. Its strengths are tightly coupled to the context of request-oriented, server-side execution.
We've managed to develop several complex apps over the last 10 years on PHP. For Web Socket support, we use Socket.IO or Firebase and it both really well together with PHP.
If you choose PHP now, you are not alone. Many companies still choose PHP for their Web Application. Slack uses PHP for most of its server-side application logic [3]
I don't know about 'back in the day'... php was way ugly and hackety hack... BUT... laravel + composer now is a beautiful thing, super easy to get going. PHP in 2017 has grown up a lot and isn't the same as php in 2007.
I think most important thing is picking something that you can hit the ground running fast, it doesn't matter what you build in (though I'd stay away from nosql personally... never know when you'll need rdbms on scaling, and starting w/ mysql/postgres is safer in many cases)..
As someone who uses Laravel the most between all backend frameworks, it still sucks because it's rare to impossible to find jobs that use it and employers still largely care about what you're most proficient with and look down on it because it's PHP. That said, I do really like Laravel
Well, to be honest if you want to use websockets, you better do that part in Node.js, Elixir or Go. The creator of Juggernaut, which was one of the most popular websocket library for Rails, ended up porting to Node.js until he said that people should stop using websockets and rely on Server Sent Events instead.
If by "websockets" you mean "notify a web client immediately when a server side event occurs", then PHP + Laravel + Pusher is a mature solution for this.
I wrote an HTML file in Microsoft Word. Then uploaded that .html file which had 800 lines. HtmlWasher cleaned up all the file content, the endless meta tags, non sense IE style tags, etc.
My experience has been the company lawyer has written the contract in word, then it has to be exported to html and cleaned of all the cruft that gets saved with word docs.
Good launch and good start. All 3 stages complete. It's in space in a matter of seconds. Need another 45 mins to declare launch success and 10 months to reach mars!
There isn't a single house or flat (for any price whatsoever) within 4 hour by train radius from Liverpool St that compares to a three bedroom in Barcelona.
Well sure, the selection of tapas in England is rather limited, it's colder and rains more, the local football teams aren't as good and you have to speak English all the time because Catalan and Spanish aren't very widely understood. But if you can't beat Barcelona for living, you'd probably want to work there too. You can definitely get similar space for your money to the Barcelona flat highlighted in the blog post in a perfectly adequate dormitory town a short commute from Liverpool Street, if Southeast England is more your thing.
Hacks are ok with web and app deployments where you are able to patch and fix to your heart's content and the damage is not life threatening.
I have worked with the medical industry, the amount of formal validation and verification that goes through on software is insane compared to what we have in the "move fast and break things" world.
Even if it is "temporary" and "desperate" I would stay away from this mentality as much as humanly possible.