SoylentNews is people
SoylentNews
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.
This discussion has been archived.
No new comments can be posted.
Think Your IT Project is a Disaster? These Will Make You Feel Better
|
Log In/Create an Account
| Top
| 37 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
sillema sillema nika su
(Score: 3, Insightful) by Anonymous Coward on Thursday November 12 2015, @07:56PM
I work for the US government and live in .net hell. The simpliest project must have dozens of references and blackbox third party libraries which no longer exist anymore and use ancient versions of the framework.
All to put wrappers of wrappers of CLR and then spit out acres of dlls that will be lost and un-reproducable.
Save the world, kill Microsoft.
(Score: 4, Insightful) by LoRdTAW on Thursday November 12 2015, @08:06PM
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.
(Score: 2, Insightful) by Anonymous Coward on Thursday November 12 2015, @09:00PM
.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.
(Score: 0) by Anonymous Coward on Thursday November 12 2015, @08:07PM
How about the project managers who chose the wrong tool for the job?
I know they may not have chosen the tool. But they could choose not to use it. Or write C/C++ and call it from .NET. The upside would be the C/C++ can be ported to any platform. The biggest upside would be that sub-par, dim-light dot-netters would not be allowed to ruin projects as they do now.
And by the way, fire the MBAs.
(Score: 3, Funny) by Anonymous Coward on Thursday November 12 2015, @09:17PM
Fire all MBA's. Into the Sun.
(Score: 4, Funny) by Thexalon on Thursday November 12 2015, @10:54PM
I knew there was a use for that old Sun workstation lying around over there!
The only thing that stops a bad guy with a compiler is a good guy with a compiler.
(Score: 2) by Gaaark on Thursday November 12 2015, @08:18PM
I'm trying, man... if they didn't have so much money in the bank, they'd have hanged themselves looooooonng ago. It just takes time! :)
--- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
(Score: 2) by tibman on Thursday November 12 2015, @10:02PM
Blaming the tool may be a sign of a poor craftsman. Though the tool could be be shit too. But "acres of dlls that will be lost and un-reproducable" sounds like you don't have version control. Which tells me that the problems you're having are not the fault of the tools.
SN won't survive on lurkers alone. Write comments.
(Score: 2) by M. Baranczak on Friday November 13 2015, @05:47AM