If you still need to use the fan, the low-profile Golden Orb does work with this box.
The noise that this box generates is pretty heinous. And unfortunately, the loudest fan is in the power supply. Unless you wish to void the warranty, there isn't much you can do yet, b/c no aftermarket powersupply fits in this case.
I wrote a small piece about this issue a couple of months ago. It may help those who don't grub money for a living get an order-of-magnitude guesstimate of realistic share value.
The bottom line is that unless you have a good
grasp of the economics of the industry in which you are working, you understand your firm's capital structure, and you have figured out the probability of any number of "exit strategies" actually occuring (a big issue since the meltdown), you may not want to forsake too much cash.
Please leave me out of this! I have nothing to do with the current situation, as I parted ways with aD at the end of March.
I've made a lot of great friends at ArsDigita, and I want to see them succeed, despite the ongoing shenanigans.
I don't think that the majority of people who are posting really understand what's going on at the company, and to comment without fully understanding the situation is, IMO, irresponsible.
Remember, there are still about 200 people at aD. They are real people. People who are no doubt _very_ concerned with the events of recent days.
Why not wait until all the facts are known before jumping the gun? Piling on at this point serves no useful purpose. .. wolf out.
The OpenACS has many of the same features as phpgroupware. It comes with a pre-built data model, and includes features like group calendars, bboards, project management, etc. Runs with PG. It's also been around a bit longer than phpgroupware.
If you can stomach tcl, it's an interesting tool for promoting online collaboration. (disclaimer -- i work closely with the project coordinators.. etc..)
I've been watching this thread unfold throughout the day, and I think that many people are getting the wrong impression of the way programmers work at ArsDigita.
I handle developer relations for
ArsDigita, both internally and externally, and thus am in the position to monitor the culture that's evolving here quite closely.
The scenario that Philip describes in his paper closely resembled the way that ArsDigita ran during its "startup phase". Insane hours, put
in by a small core of individuals. Were these people putting in 70+ hours a week? Absolutely. Is this an unbalanced lifestyle? In my opinion,
Yes.
ArsDigita has now cracked the 230 employee mark, and I can assure you that we _don't_ force people to work 70 hour weeks. Many people will put in a significant amount of time here at work, because they _love_ their jobs. It's their choice.
Our CEO stresses a healthy mix of work + play. I have yet to receive any bad reviews or cat-calls for walking out of the office at 6:00pm, nor have I seen anyone tagged as "lazy" who does the same. It's not about the time you spend at the office, it's about results. Period.
I'm an ArsDigitan, a physician, and previously worked for a large medical IT/EMR firm. [so take this with a lick of salt.]
While Imedix is a cool product, I don't think it will meet his needs for a general purpose EMR.
The ACS (or OpenACS) can be customized to suit a variety of tasks, but no EMR module yet exists. So be prepared to do a little bit of hacking/data model extension. Drop me mail if you are interested in taking this route.
A better bet for what you're trying to do (at this point) is probably GNUmed. It uses Postgresql for its database layer (passes the ACID test). Dr. Horst Herb and his crew have built the software in a very thoughtful fashion -- they've clearly used lots of commercial products before.
One final thing to remember for those who wish to go it alone & code their own product is the importance of security.
Good security is critical for all EMR software, but is of particular concern in the USA, where HIPAA rules are starting to be implemented.
Because of these rules, the task of developing an EMR for use as a permanent medical record has become more time consuming, and complex. The law is, ultimately, a consumer protection act, and should lead to higher-quality, standards-driven EMRs in the future. Be sure to examine the rules before setting out on any healthcare project.
Apparently, the online version has not hurt the sales of the print edition. The two versions of the book offer a profoundly different reading experience.
The print version adds value by being printed on easy-to-read glossy paper, and by having interesting photographs scattered throughout. No monitor is as easy on the eyes.
On the other hand, the online version is frequently updated, and provides people with an easy way to reference passages via online searches. Many people who start reading the book online eventually buy the print version. In that sense, it could be considered an effective marketing tool. (Though convincing a publishing house that this is the case may be problematic.)
Quality Assurance No 1.0 release without testing and quality assurance! A set of applications that Wine "must" run should be defined, and regression tests should be done regularly.
Kudos to the wine team for getting this far. [Seeing Office fire up under wine never fails to amaze]
IMHO, the first target for QA testing should be popular e-mail clients, like Eudora, Agent and (ugh.. Outlook.) E-mail is still the most frequently used app in business, and many users are forced to work with a particular client, thus dooming them to a life of Windows [or, in more open-minded shops, Macs.] Giving these users one less reason to dual boot into Windows would go a long way to driving adoption of Linux in a corporate environment.
Of course, getting Office to run reliably would put the nail in the coffin. But is this realistic? The day it happens, you can expect a "service pack" release from Redmond. Sigh.
If you still need to use the fan, the low-profile Golden Orb does work with this box.
The noise that this box generates is pretty heinous. And unfortunately, the loudest fan is in the power supply. Unless you wish to void the warranty, there isn't much you can do yet, b/c no aftermarket powersupply fits in this case.
I believe this package is very popular with webhosts. One user can totally hose the machine, the rest are not impacted. Trust me, I know.
The bottom line is that unless you have a good grasp of the economics of the industry in which you are working, you understand your firm's capital structure, and you have figured out the probability of any number of "exit strategies" actually occuring (a big issue since the meltdown), you may not want to forsake too much cash.
Cash is king.
it looks like the field guide for the hunting trip already exists. *shudder*
I've made a lot of great friends at ArsDigita, and I want to see them succeed, despite the ongoing shenanigans.
I don't think that the majority of people who are posting really understand what's going on at the company, and to comment without fully understanding the situation is, IMO, irresponsible.
Remember, there are still about 200 people at aD. They are real people. People who are no doubt _very_ concerned with the events of recent days.
Why not wait until all the facts are known before jumping the gun? Piling on at this point serves no useful purpose.
.. wolf out.
It comes with a pre-built data model, and includes features like group calendars, bboards, project management, etc.
Runs with PG. It's also been around a bit longer than phpgroupware.
If you can stomach tcl, it's an interesting tool for promoting online collaboration.
(disclaimer -- i work closely with the project coordinators.. etc..)
[shameless plug]: the openacs. Uses PostgreSQL, can handle high-volume.
I handle developer relations for ArsDigita, both internally and externally, and thus am in the position to monitor the culture that's evolving here quite closely.
The scenario that Philip describes in his paper closely resembled the way that ArsDigita ran during its "startup phase". Insane hours, put in by a small core of individuals. Were these people putting in 70+ hours a week? Absolutely. Is this an unbalanced lifestyle? In my opinion, Yes.
ArsDigita has now cracked the 230 employee mark, and I can assure you that we _don't_ force people to work 70 hour weeks. Many people will put in a significant amount of time here at work, because they _love_ their jobs. It's their choice.
Our CEO stresses a healthy mix of work + play. I have yet to receive any bad reviews or cat-calls for walking out of the office at 6:00pm, nor have I seen anyone tagged as "lazy" who does the same. It's not about the time you spend at the office, it's about results. Period.
Hope this helps. Adam.
While Imedix is a cool product, I don't think it will meet his needs for a general purpose EMR.
The ACS (or OpenACS) can be customized to suit a variety of tasks, but no EMR module yet exists. So be prepared to do a little bit of hacking/data model extension. Drop me mail if you are interested in taking this route.
A better bet for what you're trying to do (at this point) is probably GNUmed. It uses Postgresql for its database layer (passes the ACID test). Dr. Horst Herb and his crew have built the software in a very thoughtful fashion -- they've clearly used lots of commercial products before.
One final thing to remember for those who wish to go it alone & code their own product is the importance of security.
Good security is critical for all EMR software, but is of particular concern in the USA, where HIPAA rules are starting to be implemented.
Because of these rules, the task of developing an EMR for use as a permanent medical record has become more time consuming, and complex. The law is, ultimately, a consumer protection act, and should lead to higher-quality, standards-driven EMRs in the future. Be sure to examine the rules before setting out on any healthcare project.
hope it helps.
The chairman of the company that I work for released his book free online, and as a dead-trees book.
Apparently, the online version has not hurt the sales of the print edition. The two versions of the book offer a profoundly different reading experience.
The print version adds value by being printed on easy-to-read glossy paper, and by having interesting photographs scattered throughout. No monitor is as easy on the eyes.
On the other hand, the online version is frequently updated, and provides people with an easy way to reference passages via online searches. Many people who start reading the book online eventually buy the print version. In that sense, it could be considered an effective marketing tool. (Though convincing a publishing house that this is the case may be problematic.)
docwolf
No 1.0 release without testing and quality assurance! A set of applications that Wine "must" run should be defined,
and regression tests should be done regularly.
Kudos to the wine team for getting this far. [Seeing Office fire up under wine never fails to amaze]
IMHO, the first target for QA testing should be popular e-mail clients, like Eudora, Agent and (ugh.. Outlook.)
E-mail is still the most frequently used app in business, and many users are forced to work with a particular client,
thus dooming them to a life of Windows [or, in more open-minded shops, Macs.]
Giving these users one less reason to dual boot into Windows would go a long way to driving adoption
of Linux in a corporate environment.
Of course, getting Office to run reliably would put the nail in the coffin. But is this realistic? The day it happens,
you can expect a "service pack" release from Redmond. Sigh.
docwolf