When i first started as a Java Programmer - or trainee programmer more like - knew jack about programming. I only realise this now. Then i thought that because i could program an algorithm and get my head around recursion, i could program. But the whole process of setting up an environment, managing dependencies, picking the right components and
(
Read more... )
Comments 3
As I'm sure you know, the software architecture will depend on the kind of usage you expect (will a million people be using it or just a group of 5?) and also things like the locality of the systems (are they all behind the same firewall? are they in the same country?!).
A clean separation between the database accessing/processing layer and the display layer seems a good plan ;-)
Hope all is well!
Reply
SVN logs of who made the check ins that day often showed who'd broken things ;-)
Reply
I'm building a business intelligence app for a hospital. In addition to showing trends (number of treatments), the validity of data is a recurring theme. The hospital gets paid per treatment category (which has little to do with the actual medical treatment). The department i work for and the financial department have been disagreeing over the monthly numbers for years as they are always a few treatments off.
I think redefining queries will be an ongoing process, finding where the discrepancies in numbers come from. This is also where complex logic is required, while the trends can easily be retrieved from the data.
The number of users will be somewhere around 5, who may occasionally want to access the app from outside this hospital.
hehe svn blame
Reply
Leave a comment