News for hackers. Stuff that matters.
Re:Lessons Learned from Software Rewrites by cmdkeen on Monday September 05, 2016 @04:27AM (#12428901)
This is my life. Replacing software that was written a decade+ ago so that the software has become the process. Users find is down right difficult to think in terms of what is going on a business process rather than the steps they have to do to force the computer to say yes. Many find it genuinely tricky to even describe in even real world terms what is going on without slipping into jargon that is actually just describing the existing system.
Re:Lessons Learned from Software Rewrites by was_boring on Monday September 05, 2016 @07:40AM (#12429592)
I'm currently doing the same and have found a lot of my time is spent interviewing managers and their reports to devine what problem they are solving with the software.

In general they are completely unable to describe the job and problems they solve for the company, only how they use the software day to day, with out significant coaching and reframing.

Re:Lessons Learned from Software Rewrites by Terr_ on Monday September 05, 2016 @10:04PM (#12433253)
It's a vicious cycle: Nobody knows the vision, so they just iterate on the process, and the process is inscrutable, so nobody can extract a vision for it.