3 ms·
//would it be a good ROI? I am only a haskell beginner but i think we can break down this question a little more specific by talking about exact timespan of th
by aangjie 15y ago
//would it be a good ROI?
I am only a haskell beginner but i think we can break down this question a little more specific by talking about exact timespan of the projects. From what i understand haskell's maintainability is a huge advantage in some projects with never ending specification changes and feature requests.(ERP??)
Anyone has tried haskell for something like that? or were stopped by the chicken-egg problem of finding ppl to maintain the code?? Would be good to have some data points.
- pnathan 15y agoThe key reason I am looking at this kind of technology is because I have a large block of code in a situation where it is very difficult to do functional or unit tests due to system design. Being able to write in a language that statically analyzes my code for all the errors it can before my poor customers encounter it sounds like a huge win. The maintenance goal is being able to catch my fat-fingers and design flaws prior to rollout. * I suppose if I had to quantify the maintenance timespan, I'd make a WAG of 5-7 years, possibly 10. * It's also probable that after its solid now, in 5-7 years I will be doing other things and unable to be reassigned to work on this full-time. So it has to be other-people-hackable.
- aangjie 15y agoIt sounds like other-people-hackability is the real problem for you then. i guess it's hard to convince someone from other programming paradigms to spend the effort and time required to get proficient in haskell.