With the first widgets for opentaps 2 are some big changes: Not just a new look and feel or a new technical framework, but a whole new philosophy for building better software with open communities. This philosophy could be summed up as: Make opentaps Benefit the Maximum Number of People Simple as it sounds, but unfortunately this is not how most business software is built: Most business software is very targeted to a small group of users, and their creators and consumers often focus more on features lists than actual usefulness. For us, this philosophy required fundamental re-thinking about how we did things and three goals for opentaps: open source ERP CRM BI opentaps ofbiz pentaho jasper reports enterprise software — Open Source Strategies, Inc.
The following document is the actual text — carefully redacted — of a memo I wrote some time back [i.e., several years ago] after performing an IT project review; names and identifying concepts have been changed to preserve confidentiality (and protect the guilty). The project in question was a major IT re-engineering effort for a mission-critical system; at the time I did this review, the project had been going on for several years and had cost millions of dollars; it would eventually be canceled and the work products abandoned. The memo itself provides an interesting glimpse into just how a major IT project can go so far off the tracks that nothing useful is ever delivered. Anatomy of a runaway IT project : Bruce F. Webster
IT Tutorials and Interview questions
Relevance -- elevate. advance. deliver. Ruby/Rails We built our business with Rails. It is definitely in our sweet spot. Clojure We work on and with Clojure, support the community, and help developers use Clojure effectively.