> The newly-unveiled ATR feature is a technological breakthrough, enabling SPICE-250 to effectively learn the specific target characteristics ahead of the strike, using advanced AI and deep-learning technologies.
3,924 karma · joined September 20, 2017
https://www.deusinmachina.net/
> The newly-unveiled ATR feature is a technological breakthrough, enabling SPICE-250 to effectively learn the specific target characteristics ahead of the strike, using advanced AI and deep-learning technologies.
On top of that, trying to start a software business is tough, and if your will be shunned if your stack is non memory safe, why put yourself at a disadvantage?
A lot of these issue lie (lay?) with the UI of these systems. They are just not intuitive. This causes data to be entered incorrectly as honest mistakes. There are also fields which are free text, which should not be. I can't count how many times, I received data from a free text field for drugs, for example, and instead of information about drugs it said "The patient's pet passed away and they were sad today".
Furthermore, a lot of the data comes in separated value files, mostly CSVS (though I try to have them use TSVs if they can modify it). For such a ubiquitous format, at the volumes of data we receive, we get issues with the CSVs all the time. Lots of fields have strings that are improperly quoted, newlines in the strings, variable amount of fields per line, the usual.
That's on top of encoding issues. Randomly we will get files that aren't utf-8 and our parsers will blow up, and then we have to go back to the vendor and ask them to regenerate the data. Also trying to harmonize data across a bunch of proprietary file formats, and software is terrible
Also physicians and nurses are generally pretty skeptical when it comes to new technology even if you have a good product, and for good reason. They have been BURNED many times but companies coming in and promising the world, and delivering a half baked product. Anyone can get an MVP together quickly that kind of does what they need done, but to really support end users requires a lot more investment. I'm talking on-site trainings, software engineers actually watching the faculty USING THE TOOL, and taking notes when they struggle, being proactive about the wants and needs of the staff instead of adding features that seem useful. This almost never happens
Then there are factors outside of just EMRS and the user experience that just make the patient experience much more difficult, even when everyone involved is following standard practices. Data is king in this space, and companies are reticent to share it without lots of money and an books worth of clauses and agreements. You can win in this space just by having more data, or rare data. Lots of patient populations for obscure diseases require large sample sizes before you will have enough patients to perform a study. Pharma companies will approach you with prospective studies and the more data you have the more feasibility work you do that end up leading to studies where you get paid, and your name on paper. This HURTS patients and does nothing but help to keep competitive advantages.
On the bright side, since the U.S healthcare system is so capitalistic, we can usually find what we need coded in the billing data, because patients are nickle and dimed for everything that happens at a medical facility.
I have about twenty more pages of things I could talk about. This whole system is terrible and it doesn't have to be. On a more positive note, I love being able to track patient outcomes and see them improving, and I really enjoy working with huge datasets.
The things I like about C aren't really about the language itself. There just aren't many programming languages that do these things well
1. Cross platform across Linux, MacOS (Intel and Arm), Windows (Without the use of MinGW And Cygwin), *BSD
2. Ability to create an executable
3. Small programs that start quick
4. Simple syntax that does not obfuscate when allocations are occurring
For GCed languages GO is probably the one that best fits this criteria for most people.
Sometimes I wish someone just took C and improved it. Instead of looking at C++ and thinking "what features should C have that C++ has" It should look back at C and go "What features does C not have, that it should"? Some that come to mind are
1. A better syntax for creating pointers and dereferencing them
2. Fixed const so that it works with array initialization
3. Modules instead of headers
4. Cross platform string types that encoded length 5. Hash tables
6. Remove preprocessor macros and replace common use cases with things built into the language
7. Build system that didn't rely on Make, Cmake, Ninja, Autotools, configure etc
8. Easy interop with C
Maybe this is a lot to ask, but most languages I see are solving waay more problems then this.
2,4,5, can be done without leaving C, which is why most people homebrew their own solutions. I think Pascal actually comes close, but it's held back by the fact that the editor support is pretty poor. Pacal-Mode in Emacs is not good, and Lazarus with its multiple floating windows is infuriating to have to alt+tab multiple times to switch to and from it. Plus I could never actually get it to build my programs properly without throwing some dwarf errors.
Recently I've been playing around with Gambit-C and it seems to suit most of my needs. It compiles to C, and then the C code is compiled with Clang, MSVC, or GCC depending on what your platform is. I get the benefit of a language that has more features than C with it being R7RS (but still being small because it's Scheme) and implementing the most common SRFIs (including hashes), but with all the portability of C. It also has dead simple interop with C using the C-Lambda and C-Define special forms (you can write C directly inside the Gambit code)^1 which means you can leverage C code with hardly any effort. There are tradeoffs with this approach, but IMO almost all of them are ecosystem related which can be fixed, as opposed to language related, which might be impossible to fix without breaking compatibility with existing code
1. https://www.deusinmachina.net/p/gambit-c-scheme-and-c-a-matc...
One of the things “open” game engines run into (IE OpenMW) is that if source code for a game engine they are reimplementing leaks, they avoid it at all costs, since it could “contaminate” the project and ruin their protection as a fair use project.
I feel like this sets a bad precedent for the GPL because if anyone can do that, then it weakens the power of copy left licenses as a whole, but maybe I’m missing something because I’m not a lawyer
With this strategy, I've often seen videos from my favorite YouTubers within minutes of them posting a new video. It also allows me to "finish" watching YouTube for the day.
This stuff just takes time. I remember reading a news article where someone talked about drinking bubble tea in NYC before it was popular as a kid, as a treat. Now you can get bubble tea everywhere
It's really crappy that large organizations can still keep benefiting from these projects without putting any resources into them. Again I know some companies have donated to open source projects, or hired developers but that is the exception. Part of me wonders if Copy left viral licenses are the only way to combat this. If you are going to use a bunch of critical open source projects in your code base, and you aren't going to pay, you should at least pay it forward by making your source code available.
I've seen some people mention creating some sort of license that is Open source, but if you make more than X amount of money or have X amount of employees then you have to pay X amount in licensing fees. That seems reasonable and still allows small projects to still use these libraries like they always have. But then again that's pretty hard to enforce. And if the GPL is anything to go by, then a license doesn't necessarily stop flagrant misuse of the software anyway