Timeline for Advice on designing web application with a 40+ year lifetime
Current License: CC BY-SA 3.0
36 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2017 at 11:10 | review | Close votes | |||
| May 21, 2017 at 3:01 | |||||
| Apr 29, 2015 at 21:00 | history | edited | durron597 |
Removed [learning] tag, added [project-management]
|
|
| Jun 23, 2014 at 20:39 | comment | added | Lucas Soares | I guess lots of people already said that, but: Smart data structures and dumb code works a lot better than the other way around. (from Eric S. Raymond) And god help you if you forget the Audit Tables and logs. And PDF\A. Regarding data entry, KISS. | |
| Jun 23, 2014 at 3:01 | history | protected | Telastyn | ||
| Jun 22, 2014 at 10:50 | answer | added | phlogisticfugu | timeline score: 7 | |
| Jun 22, 2014 at 4:27 | answer | added | Bush Al | timeline score: 3 | |
| Jun 22, 2014 at 0:32 | answer | added | Alex S | timeline score: 3 | |
| Jun 21, 2014 at 23:08 | answer | added | Richard Connamacher | timeline score: 13 | |
| Jun 21, 2014 at 22:02 | answer | added | mrdenny | timeline score: 4 | |
| Nov 6, 2013 at 1:31 | answer | added | Pedro Werneck | timeline score: 10 | |
| Nov 5, 2013 at 22:01 | comment | added | Pete | LOL! No... but it probably should be! | |
| Nov 5, 2013 at 18:12 | comment | added | mclark1129 | Does this project happen to be healthcare.gov? | |
| Nov 5, 2013 at 16:00 | comment | added | Pete | I haven't even begun to think about encryption... Auditing is currently non-existent. My client started to roll out this application before it was done and is promising all these features. Started to look for work already - one start-up offered me 20k over. It's in the same field dealing with Health care systems. Their system looks in rough shape as well. They're entire dev team left and they have only 2 employees left as well. | |
| Nov 4, 2013 at 20:15 | comment | added | HLGEM | The data is what needs to last for over 40 years, hire a database specialist to design it. Preferabley someone with HIPAA experience. This is not easy stuff (you are likely going to need encrypting and auditing of both table changes and data changes for instance)and is critical if you are storing any kind of patient records. | |
| Nov 4, 2013 at 17:30 | comment | added | dsw88 | 6 months for 2 people to architect and implement an application that needs to last 40+ years? Doesn't matter how good you are, that sounds like a setup for failure. If you can't convince your organization how unreasonable that is, then I would suggest you start looking for other employment ASAP. | |
| Nov 4, 2013 at 15:07 | answer | added | SpaceTrucker | timeline score: 2 | |
| Nov 4, 2013 at 14:50 | answer | added | kaiser | timeline score: 9 | |
| Nov 3, 2013 at 9:50 | history | tweeted | twitter.com/#!/StackProgrammer/status/396937383381192706 | ||
| Nov 1, 2013 at 10:51 | comment | added | Ben Thurley | I'll never understand why companies get contractors in to architect like this. They take their money and run and the rest of us spend years sorting out the mess. | |
| Oct 28, 2013 at 22:57 | comment | added | Sean McSomething | They're giving two contract developers 6 months to build this system? Collecting years of legacy data AND anticipating new requirements decades into the future? If you're not already walking away from the project, start running. This is way bigger than two people can handle in anything close to the time frame alotted. The client has completely unreasonable expectations and is unwilling to commit proper resources to the project. | |
| Oct 28, 2013 at 21:25 | answer | added | Tangurena | timeline score: 40 | |
| Oct 28, 2013 at 16:36 | comment | added | Pete | @maple_shaft yup.. I've been given the green light to rebuild and we've got the data backed up here now so we don't have to worry about him deleting our data maliciously. | |
| Oct 28, 2013 at 16:32 | comment | added | maple_shaft♦ | Is this the same architect that you are talking about in this question? workplace.stackexchange.com/questions/15243/… | |
| Oct 28, 2013 at 16:30 | history | edited | maple_shaft♦ | CC BY-SA 3.0 |
Removing the part of the question that is polling for opinions
|
| Oct 28, 2013 at 16:26 | vote | accept | Pete | ||
| Oct 28, 2013 at 16:25 | comment | added | Pete | So true, with all the data integrity issues we've been having the client has been writing everything down on paper. This has been time consuming, but they trust paper much more than the digital system. | |
| Oct 28, 2013 at 15:50 | answer | added | GrandmasterB | timeline score: 132 | |
| Oct 28, 2013 at 15:47 | comment | added | Pieter B | To fullfill the requirement of a database being usefull for the next 40 years I would put it all on paper. Paper has proven itself, whereas digital storage mostly has proven how to lose lots of data fast. (but ofcourse preserve all data which should be destroyed) | |
| Oct 28, 2013 at 15:42 | review | Close votes | |||
| Oct 28, 2013 at 22:51 | |||||
| Oct 28, 2013 at 15:37 | comment | added | Pete | @ShivanDragon I was hoping that we could use a reporting database to reduce the slow down in the system. | |
| Oct 28, 2013 at 15:28 | comment | added | Pete | Should the shift in design be a focus on being able to move the data from the database easily to future technologies? | |
| Oct 28, 2013 at 15:27 | comment | added | Shivan Dragon | @MichaelT: +1. user2708395: why are you so dead set on normalizing the whole database? Especially for something which clearly has a lot of data (last 40 years of it) and will probably accumulate a lot more data (next 40 years). Your main problem with all this data is how can you search through it in a decent amount of time. Normalization will not help with that, in fact it will make it slower to search through it. Same goes for using a CMS. I recommend using a schemaless database, which comes with easy deployment of same db on multiple machines, like Mongo DB. | |
| Oct 28, 2013 at 15:26 | answer | added | Robert Harvey | timeline score: 29 | |
| Oct 28, 2013 at 15:21 | comment | added | whatsisname | designing to be 40+ year 'future proof' sounds like an exercise in futility. | |
| Oct 28, 2013 at 15:17 | comment | added | user40980 | Future proofing is one thing, but I believe that a client to ask for software that is expected to have a lifespan that is 10x-20x longer than the current history of mobile/tablet computing or 5x-8x longer than the current history of the language in use is... unreasonably optimistic about the stability of a given model of computing. | |
| Oct 28, 2013 at 15:11 | history | asked | Pete | CC BY-SA 3.0 |