Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Thursday November 12 2015, @07:21PM   Printer-friendly
from the schadenfreude dept.

There are many ways to gauge satisfaction with a new computer system, but when the people who have to use it show up for work wearing red and declare it "Code Red" day, you probably don't need to bother with a survey.

That's exactly what's scheduled to happen this Thursday in the city of Hamilton, Ontario, where government workers plan to protest the one-year anniversary of a controversial new computer system.

Ontario's Social Assistance Management System (SAMS), installed a year ago this week by the province's Ministry of Community and Social Services, was supposed be a more efficient replacement for its outdated case management system.

It hasn't quite turned out that way.

Several tales of woe, but no deeper dive on causes, like scope creep.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by LoRdTAW on Thursday November 12 2015, @08:06PM

    by LoRdTAW (3755) on Thursday November 12 2015, @08:06PM (#262326) Journal

    I wouldn't consider .net terrible. But unsupported black box libraries and ancient frameworks are. .net isn't your problem. And moving to another language, runtime or platform would not solve it either.

    Starting Score:    1  point
    Moderation   +2  
       Insightful=2, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4  
  • (Score: 2, Insightful) by Anonymous Coward on Thursday November 12 2015, @09:00PM

    by Anonymous Coward on Thursday November 12 2015, @09:00PM (#262355)

    .net isn't your problem

    This exactly. I have a multimillion per year revenue project that runs on .net. But we are stuck on libraries that are 5+ years old. Not because .net is 'hard'. But because no one in the org wants to upgrade. Never mind the 15 or so bugs the NEWER frameworks fixed and were fixed years ago for the case 10 customers a pissed off about. Getting them to even look at visual studio 2015 much less use and to stop supporting 2008 is a challenge. But somehow they think if they re-write the whole stack in java all the issues will go away. No, you just moved the problem to a different language.

    It is an organizational problem. Not a language one. And that is on a *very* successful project.