Some of the errors are not relevant, mainly having my code in a managed (i.e..NET) environment. The SQL injection and XSS potential vulnerabilities are still very relavent to me. Although most of my responsibility lies in code which is only reached via a https authenticated connection, as with any other web programmer, a "trusted" user can still -especially- find exploits.
This is even more true in inherited code. If you inherited code from a previous employee, I recommend a rigorous audit of the input and output validation. You just don't know what was missed in something you didn't write.
If so, it could be the coolest Windows tablet yet given the proper Boot Camp drivers. Much as I enjoy OSX, when it comes to work, it is nice to run Windows 7 on my MacBook. Given that tablets will be used more and more by doctors, I know they would love to be using their EMR with pretty Apple hardware.
Given all the new tablet features introduced in Windows 7, it would be a bit ironic for Apple to have the first hardware where the masses might truly want to use it.
That reminds me of the oil light on a Lincoln Continental. It lights up, then a few seconds later, your engine seizes!
A few seconds warning sometimes just adds to the drama of the inevitable. In the relativity of time, that means if we got a few hours warning of an imminent asteroid impact, it would just be enough time maybe for a little mass-hysteria and to kiss your family good-bye.:)
DRM does not depend on a particular programming paradigm, nor does Open Source. PGP is a great example of open source security which remains secure. The challenge really lies in the implementor, who needs to enforce security while not falling back on closed-cource obfuscation to achieve the task.
Do you think google should get rid of GFS and bigtable and move off their cloud to a more centralized datastore? I'm sure they can handle all of their data and computing needs without using a cloud
Maybe, but I would rather not use something that bursts and shoots its data everywhere when it is saturated. Oh wait, did I take the "cloud" metaphor too far?:)
A lot of people still use HL7 2.4 because they don't want to switch to XML, but the format is not the challenge. The issue is the receiver's interpretation of the data.
For instance, one EMR puts the doctor for an Appointment in one HL7 field, and the system it sends to looks in another. These are the sort or impedance mismatches I work on every day as a developer. The issue is really healthcare-wde, not just EMRs. ANSI transactions (such as 837 claims) are hugely open to interpretation. One workaround a lot of entities have come up with is to write up a "Companion Guide" which lays out what they expect in each data element.
But if you care about your sanity, or the sanity of your users, you are shit out of luck with Access. There is a mass exodus occurring with Access Runtime developers to.NET. Join them and be free to code your own way, in your favourite language. With SQL and.NET Express, there is really no excuse for writing apps that way anymore.
and it isn't so bad. I actually changed my mind about throwing the party and e-mailed Microsoft asking them to cancel me as a host. They replied saying I did not need to throw the party but they had already sent the pack out and to "use it responsibly". It has ten tote-bags with a cool psychadelic picture (one of the new windows 7 wallpapers), a pack of cards with a similar picture on them, some coupons for third-party software, a centerpiece, and some napkins. The only thing I found odd was the balloons and streamers were not branded, just solid colors like you'd get at any party store. I gave away the signature edition of Ultimate because I already get plenty of copies for myself from MSDN.
Although they got a lot of flack for the house parties because the idea is pretty lame to the initiated, any publicity is good publicity. I also liked the fact that they included the third-party coupons. To me it shows that they are trying not to shut others out as they used to. One could just as easily use the built-in disc burning in windows, so giving a coupon away for Nero is at least a nod to the competition.
I did read your example, and I don't think either of us are "wrong". How concurrency and transactions are utilized still is an exercise for the programmer in cases like this, I agree.
If a certain amount of time needs to be guaranteed between changes to a record, a "Last Changed" timestamp could be used, checking if a certain interval of time has elapsed since the record was touched.
Sorry, I just don't get why one would hold a transaction open while a web user goes to get a cup of coffee. The transaction shouldn't even start until the user clicks a "Save" button. Yes, HTML is stateless, but there are plenty of options for keeping some variable values for a predetermined amount of time.
Locking is a solved problem in most Database Management Systems. I think you are worried about the wrong layer of your application. Web and Application code is most often agnostic to how records are retrieved, updated, and locked for concurrency. For reference, look up the ACID properties of a typical RDBMS.
OMG! Have you tried to get to View->Source in IE8 nowadays? You actually have to right-click inside the web page now and choose "View Source" in the context menu. How counter-intuitive is that? NOT!
I saw a Pen & Teller "Bullshit" episode yesterday about dolphins being more intelligent than humans. The name of the TV show obviates the host's bias regarding the subject. The fact that the only scientist who seemed to claim dolphins were more intelligent was doing studies with them involving LSD seems to discredit the idea...
Although hard-coding things is generally frowned upon, I can see why it is used for "quick and dirty" reasons. What really caused the FAIL in the OP's code is the short-circuit AND (&&). If a single & was used, the artist would have seen their object.
Maybe the critical mass will be when Crossover is able to natively run the.NET Framework. It might sound like blasphemy while Mono may gain more traction, but developers being lazy by default, it would be nice to run a ClickOnce app on Linux or Mac. Currently, there aren't even hoops to jump through for that, ClickOnce just plain does not work yet.
Slashdot Mirror
Some of the errors are not relevant, mainly having my code in a managed (i.e. .NET) environment. The SQL injection and XSS potential vulnerabilities are still very relavent to me. Although most of my responsibility lies in code which is only reached via a https authenticated connection, as with any other web programmer, a "trusted" user can still -especially- find exploits.
This is even more true in inherited code. If you inherited code from a previous employee, I recommend a rigorous audit of the input and output validation. You just don't know what was missed in something you didn't write.
Enough Said.
If so, it could be the coolest Windows tablet yet given the proper Boot Camp drivers. Much as I enjoy OSX, when it comes to work, it is nice to run Windows 7 on my MacBook. Given that tablets will be used more and more by doctors, I know they would love to be using their EMR with pretty Apple hardware.
Given all the new tablet features introduced in Windows 7, it would be a bit ironic for Apple to have the first hardware where the masses might truly want to use it.
Cyberpunk and Paranoia are probably ok then.
Actually, that would have been astronaut@stox.nasa.gov!ihnp4!seismo!nasa!iss
I often look nostalgically back and think of the old bang paths for e-mail. Boy, I don't miss 'em! :)
That reminds me of the oil light on a Lincoln Continental. It lights up, then a few seconds later, your engine seizes!
A few seconds warning sometimes just adds to the drama of the inevitable. In the relativity of time, that means if we got a few hours warning of an imminent asteroid impact, it would just be enough time maybe for a little mass-hysteria and to kiss your family good-bye. :)
DRM does not depend on a particular programming paradigm, nor does Open Source. PGP is a great example of open source security which remains secure. The challenge really lies in the implementor, who needs to enforce security while not falling back on closed-cource obfuscation to achieve the task.
Maybe, but I would rather not use something that bursts and shoots its data everywhere when it is saturated. Oh wait, did I take the "cloud" metaphor too far? :)
A lot of people still use HL7 2.4 because they don't want to switch to XML, but the format is not the challenge. The issue is the receiver's interpretation of the data.
For instance, one EMR puts the doctor for an Appointment in one HL7 field, and the system it sends to looks in another. These are the sort or impedance mismatches I work on every day as a developer. The issue is really healthcare-wde, not just EMRs. ANSI transactions (such as 837 claims) are hugely open to interpretation. One workaround a lot of entities have come up with is to write up a "Companion Guide" which lays out what they expect in each data element.
But if you care about your sanity, or the sanity of your users, you are shit out of luck with Access. There is a mass exodus occurring with Access Runtime developers to .NET. Join them and be free to code your own way, in your favourite language. With SQL and .NET Express, there is really no excuse for writing apps that way anymore.
When it DOS not DOS? When it runs on an Atari.
and it isn't so bad. I actually changed my mind about throwing the party and e-mailed Microsoft asking them to cancel me as a host. They replied saying I did not need to throw the party but they had already sent the pack out and to "use it responsibly". It has ten tote-bags with a cool psychadelic picture (one of the new windows 7 wallpapers), a pack of cards with a similar picture on them, some coupons for third-party software, a centerpiece, and some napkins. The only thing I found odd was the balloons and streamers were not branded, just solid colors like you'd get at any party store. I gave away the signature edition of Ultimate because I already get plenty of copies for myself from MSDN.
Although they got a lot of flack for the house parties because the idea is pretty lame to the initiated, any publicity is good publicity. I also liked the fact that they included the third-party coupons. To me it shows that they are trying not to shut others out as they used to. One could just as easily use the built-in disc burning in windows, so giving a coupon away for Nero is at least a nod to the competition.
I did read your example, and I don't think either of us are "wrong". How concurrency and transactions are utilized still is an exercise for the programmer in cases like this, I agree.
If a certain amount of time needs to be guaranteed between changes to a record, a "Last Changed" timestamp could be used, checking if a certain interval of time has elapsed since the record was touched.
Sorry, I just don't get why one would hold a transaction open while a web user goes to get a cup of coffee. The transaction shouldn't even start until the user clicks a "Save" button. Yes, HTML is stateless, but there are plenty of options for keeping some variable values for a predetermined amount of time.
Locking is a solved problem in most Database Management Systems. I think you are worried about the wrong layer of your application. Web and Application code is most often agnostic to how records are retrieved, updated, and locked for concurrency. For reference, look up the ACID properties of a typical RDBMS.
OMG! Have you tried to get to View->Source in IE8 nowadays? You actually have to right-click inside the web page now and choose "View Source" in the context menu. How counter-intuitive is that? NOT!
Dear potential Client,
How's it feel to want?
Sincerely,
Western Digital
I saw a Pen & Teller "Bullshit" episode yesterday about dolphins being more intelligent than humans. The name of the TV show obviates the host's bias regarding the subject. The fact that the only scientist who seemed to claim dolphins were more intelligent was doing studies with them involving LSD seems to discredit the idea...
True, but most people skipped Vista. Compared to XP, it is a major release.
Although hard-coding things is generally frowned upon, I can see why it is used for "quick and dirty" reasons. What really caused the FAIL in the OP's code is the short-circuit AND (&&). If a single & was used, the artist would have seen their object.
Yes, and the text above the hand could have read: "If you expected memory protection..."
Maybe the critical mass will be when Crossover is able to natively run the .NET Framework. It might sound like blasphemy while Mono may gain more traction, but developers being lazy by default, it would be nice to run a ClickOnce app on Linux or Mac. Currently, there aren't even hoops to jump through for that, ClickOnce just plain does not work yet.
There is a job on Ars posted where Canonical is wiling to hire someone to help change that situation.
ATM Machines don't count.