Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Adding some extra on to my previous reply.

"2. Rapidly changing business requirements. This is everything from state and federal reporting requirements to the expectations of end users. It's hard enough to maintain these core systems and keep folks around who are good enough to do it".

In mid 2011 our state passed some new laws as to how funding would be applied for virtual school enrollments across the state. We had a model in place, then code rolled out, within a few weeks - we had one bug that reared its head a few months later that was patched in a day and it's been fine since.

I'm not convinced the 'commercial player' that's taking everything over even understand the concept of our funding model, much less will be able to reliably integrate it with their existing systems, in the next 6 months. That's after handing over the code (with some, but certainly nowhere near complete, tests).

They may still pull it off, but I've yet to see them react quickly to 'changing business requirements'.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: