Are you saying that if they were overwhelmingly female that they would appreciate MATLAB more?
I don't know. In my only actual programming job in the early 90s I worked with some great MUMPS developers who happened to be female and they were at a far higher percentage of the developers I worked with than listed in the survey. I'm just pointing out that the demographics of the SO survey may not really represent what the programming community is, so what they say as what they like may not be reality.
Also, consider that it is Stack Overflow. It's mostly code-snipet "programmers" and people looking for help with homework.
That's true. It's been a real help in (re)learning Python.
Take a look at the demographics of the people that responded. Overwhelmingly male, average age is 29, half have been coding for less than 5 years, and almost half don't have at least a BS degree in CS.
Releasing the source code would actually made it worse for the compatibles - in order to prevent infringement, the clones had to reverse engineer the BIOS in a clean room fashion, so no looking at the source code at all.
Think of makers more as open source software developers - it'll scratch the itch they have. It may or may not be suitable for someone outside the community, and it would be a lot of work to make use of it. Doesn't make it bad, just different.
Know, ask, or was able to find out? In some cases the doctor will pre-approve you for a procedure. In doing to, they should be sending what will be happening and what they will bill for.
That sounds more like a problem with the insurance company than the medical provider. I have a high-deductible insurance and I've been notified well in advance of the amount they covered and the amount that I'm responsible for (which itself may be different than what the original bill amount was). Looking at a cough may be a simple transaction, but if it turns out the person has lung cancer the ICD-10 codes will start piling up. By describing procedures in a consistent way you can ensure that billing is actually more open, since you can go to various providers and say "how much for a V97.33XD?" and get an answer back on what they'd bill.
It's not easy now, and ICD-10 was only recently implemented in a lot of places (despite being out for 20 years), but it should make things easier over time.
So how does a makerspace address this? Don't get me wrong, I like going to the one near me as I help them with Linux and they help me with electronics, but they don't have Solidworks installed to do the simulations described up top.
I gave an example and backed it up with my personal experience with the caveat that this is about EMRs and not wait times, which an EMR can't really help much with. I'm not seeing much in the way of examples to counter the statements I made.
I'll grant you that. I think you'll see that over time doctors get better at it especially as older doctors retire and newer ones take their place. My daughter's pediatrician walks around with a tablet PC that he drops the information into and has already recorded things like the pharmacy we go to. "Still go to the CVS on Boston Road? Ok, it'll be ready when you get there"
and having seen most of the programs available and their output, a lot of it is because of lazy programming that makes simple tasks difficult.
That's just bad design. When I worked at the VA there was a good bit of discussion between developers and the people that actually used the software. Granted, this was 1993ish so they were all text-based, but there were a number of things that developers put in to make it easier for users to enter the data they had to. Don't know how that's changed in the past 20 years, probably for the worse.
That's an ICD-10 code, and the Feds don't generate them, WHO does.
If anything, codes like that standardize care, reporting, and billing. This way, two systems that are otherwise incompatible can have the following conversation:
What was the cause of injury? Sucked into an airplane engine What treatment did the patient receive? (insert set of ICD codes for treatment) Insurance company pays rates based off the ICD codes, done.
There's 68,000+ codes in ICD-10. There's going to be a few odd ones in there.
Nice. I worked for the VA for a few years in the early 90s, which is why I know at least how they operate. I think the bigger issue in the future is going to be translating records between institutions, just like the DoD and VA can't easily move records. When each system grows organically over time and doesn't think it'll need to communicate with others, it creates a huge problem when you do.
In general, SAs are a dying breed. Yes there's some still around and there will be in the future, but many of them are being folded into 'DevOps' which is really developers that use short-term instances to do the job they need. Since each single instance does one job, does it well, then gets destroyed there's no need to have someone handle the long term care and feeding. Since you block everything in a VPC and you don't have users connecting directly there's no security or user administration issues. Storage? Networking? Logging? Pfft, whatever.
It's fairly easy to see when you have developers that demand the latest and greatest versions of RoR/NodeJS/MongoDB/PostgreSQL/whatever while SAs are tearing their hair out trying to figure out how to install, let alone support, multiple versions of software distributed via github for developers that may themselves be coding against different versions of the above. So IT is seen as inflexible and AWS and the cloud offered developers a way to skirt around the surly SAs and build whatever sandbox they wanted with the versions of software they wanted and in a faster time than the SAs could reply to a ticket.
As a former SA, this is going to go on for a bit but given how the cycles of computing go SAs sill be back in fashion in 10-15 years. Until then, I hope you know Ruby.
For 6 weeks a year I have a compilation of Christmas music that I broadcast online for anyone to listen to. Two years ago I figured I'd go legal and do my bit to make sure artists get paid, so I set up an account at Stream Licensing, mostly since I didn't want to deal with individual licensing organizations. The rules placed on SL that then get placed on me are crazy. Here's a small sample from their TOS
In any three-hour period, you should not intentionally program more than three songs (and not more than two songs in a row) from the same recording; you should not intentionally program more than four songs (and not more than three songs in a row) from the same recording artist or anthology/box set.
Requests may not be played at a specified time and must not intentionally break the artist and song rotation rules (above). If your service substantially consists of programming from requests, requests must be delayed for at least one hour. For more info see under Item 13 below.
This license is for non-interactive streaming which means your listeners may not determine in any way when a specific song will be played. Non-interactive streaming specifically means broadcasting an Internet radio stream. You may NOT archive old shows and make them available as podcasts or as shows available on demand. Should you choose to do so, such activity is NOT covered under your StreamLicensing Affiliation. This is not a rule we made up, it is copyright law.
Not only that, I can't have users go directly to my site to listen. I need to either include a flash player widget on my site or create a frame that really goes to SL's site in order to give people a link to go to.
Slashdot Mirror
Take a look at how we treat those we consider lower than us. Even if they're human.
How is it illegal if there's a court order?
For the witty commentary and the recollections of /. old timer stories?
I remember this one time...
Are you saying that if they were overwhelmingly female that they would appreciate MATLAB more?
I don't know. In my only actual programming job in the early 90s I worked with some great MUMPS developers who happened to be female and they were at a far higher percentage of the developers I worked with than listed in the survey. I'm just pointing out that the demographics of the SO survey may not really represent what the programming community is, so what they say as what they like may not be reality.
Also, consider that it is Stack Overflow. It's mostly code-snipet "programmers" and people looking for help with homework.
That's true. It's been a real help in (re)learning Python.
n00b
Take a look at the demographics of the people that responded. Overwhelmingly male, average age is 29, half have been coding for less than 5 years, and almost half don't have at least a BS degree in CS.
Oh, I found it *eyeroll*
http://stackoverflow.com/resea...
The link for "most loved" at SO takes me to "compensation by technology" which merely shows pay. And doesn't even list Swift.
Releasing the source code would actually made it worse for the compatibles - in order to prevent infringement, the clones had to reverse engineer the BIOS in a clean room fashion, so no looking at the source code at all.
Just like open source developers.
Because they're afraid they might sustain injury by cow (other) and need treatment.
Think of makers more as open source software developers - it'll scratch the itch they have. It may or may not be suitable for someone outside the community, and it would be a lot of work to make use of it. Doesn't make it bad, just different.
Know, ask, or was able to find out? In some cases the doctor will pre-approve you for a procedure. In doing to, they should be sending what will be happening and what they will bill for.
That sounds more like a problem with the insurance company than the medical provider. I have a high-deductible insurance and I've been notified well in advance of the amount they covered and the amount that I'm responsible for (which itself may be different than what the original bill amount was). Looking at a cough may be a simple transaction, but if it turns out the person has lung cancer the ICD-10 codes will start piling up. By describing procedures in a consistent way you can ensure that billing is actually more open, since you can go to various providers and say "how much for a V97.33XD?" and get an answer back on what they'd bill.
It's not easy now, and ICD-10 was only recently implemented in a lot of places (despite being out for 20 years), but it should make things easier over time.
So how does a makerspace address this? Don't get me wrong, I like going to the one near me as I help them with Linux and they help me with electronics, but they don't have Solidworks installed to do the simulations described up top.
http://www.cbsnews.com/news/va...
I gave an example and backed it up with my personal experience with the caveat that this is about EMRs and not wait times, which an EMR can't really help much with. I'm not seeing much in the way of examples to counter the statements I made.
IOW "Government did it, government can't do anything right, therefore I don't like it" - I find that attitude disappointing and shortsighted as well.
EMRs are dangerous in the hands of lazy doctors,
I'll grant you that. I think you'll see that over time doctors get better at it especially as older doctors retire and newer ones take their place. My daughter's pediatrician walks around with a tablet PC that he drops the information into and has already recorded things like the pharmacy we go to. "Still go to the CVS on Boston Road? Ok, it'll be ready when you get there"
and having seen most of the programs available and their output, a lot of it is because of lazy programming that makes simple tasks difficult.
That's just bad design. When I worked at the VA there was a good bit of discussion between developers and the people that actually used the software. Granted, this was 1993ish so they were all text-based, but there were a number of things that developers put in to make it easier for users to enter the data they had to. Don't know how that's changed in the past 20 years, probably for the worse.
That's an ICD-10 code, and the Feds don't generate them, WHO does.
If anything, codes like that standardize care, reporting, and billing. This way, two systems that are otherwise incompatible can have the following conversation:
What was the cause of injury? Sucked into an airplane engine
What treatment did the patient receive? (insert set of ICD codes for treatment)
Insurance company pays rates based off the ICD codes, done.
There's 68,000+ codes in ICD-10. There's going to be a few odd ones in there.
Nice. I worked for the VA for a few years in the early 90s, which is why I know at least how they operate. I think the bigger issue in the future is going to be translating records between institutions, just like the DoD and VA can't easily move records. When each system grows organically over time and doesn't think it'll need to communicate with others, it creates a huge problem when you do.
From an EMR standpoint? I find that attitude disappointing and shortsighted.
While there's problems scheduling at the VA and getting in to see a doctor, they've had EMRs for 50 years. It's all online and easy to search.
In general, SAs are a dying breed. Yes there's some still around and there will be in the future, but many of them are being folded into 'DevOps' which is really developers that use short-term instances to do the job they need. Since each single instance does one job, does it well, then gets destroyed there's no need to have someone handle the long term care and feeding. Since you block everything in a VPC and you don't have users connecting directly there's no security or user administration issues. Storage? Networking? Logging? Pfft, whatever.
It's fairly easy to see when you have developers that demand the latest and greatest versions of RoR/NodeJS/MongoDB/PostgreSQL/whatever while SAs are tearing their hair out trying to figure out how to install, let alone support, multiple versions of software distributed via github for developers that may themselves be coding against different versions of the above. So IT is seen as inflexible and AWS and the cloud offered developers a way to skirt around the surly SAs and build whatever sandbox they wanted with the versions of software they wanted and in a faster time than the SAs could reply to a ticket.
As a former SA, this is going to go on for a bit but given how the cycles of computing go SAs sill be back in fashion in 10-15 years. Until then, I hope you know Ruby.
For 6 weeks a year I have a compilation of Christmas music that I broadcast online for anyone to listen to. Two years ago I figured I'd go legal and do my bit to make sure artists get paid, so I set up an account at Stream Licensing, mostly since I didn't want to deal with individual licensing organizations. The rules placed on SL that then get placed on me are crazy. Here's a small sample from their TOS
Not only that, I can't have users go directly to my site to listen. I need to either include a flash player widget on my site or create a frame that really goes to SL's site in order to give people a link to go to.