Slashdot Mirror


America's Cities Are Running on Software From the '80s (bloomberg.com)

Even San Francisco's tech chops can't save it from relying on computers that belong in a museum. From a report: The only place in San Francisco still pricing real estate like it's the 1980s is the city assessor's office. Its property tax system dates back to the dawn of the floppy disk. City employees appraising the market work with software that runs on a dead programming language and can't be used with a mouse. Assessors are prone to make mistakes when using the vintage software because it can't display all the basic information for a given property on one screen. The staffers have to open and exit several menus to input stuff as simple as addresses. To put it mildly, the setup "doesn't reflect business needs now," says the city's assessor, Carmen Chu.

San Francisco rarely conjures images of creaky, decades-old technology, but that's what's running a key swath of its government, as well as those of cities across the U.S. Politicians can often score relatively easy wins with constituents by borrowing money to pay for new roads and bridges, but the digital equivalents of such infrastructure projects generally don't draw the same enthusiasm. "Modernizing technology is not a top issue that typically comes to mind when you talk to taxpayers and constituents on the street," Chu says. It took her office almost four years to secure $36 million for updated assessors' hardware and software that can, among other things, give priority to cases in which delays may prove costly. The design requirements are due to be finalized this summer.

15 of 211 comments (clear)

  1. That's because their programmers were skilled by Anonymous Coward · · Score: 5, Insightful

    You can read the headline as a denigration of governments (which is always valid, because they get paid regardless of their performance), but you can also read it as proving that the programmers of the 1980s produces some pretty solid work.

    1. Re:That's because their programmers were skilled by thereddaikon · · Score: 5, Insightful

      The average professional developer of the 80's was probably better at their job than the average one today. For one, they actually had a working understand of the hardware on a conceptual level and could relate how their code would interact with the system. Ask your average JS coder how a computer works and grab some popcorn. Due to the limitations of distribution methods and storage media of the time software was also far less bloated and much more stable at launch. You couldn't easily patch something post launch like you can now so you had to get it mostly right the first time. There is no such thing as bug free code but there is code with some bugs and then there is code that is mostly bugs.

    2. Re:That's because their programmers were skilled by Darinbob · · Score: 3, Insightful

      You can read that as some people just are dumb, criticizing governments for spending money in the first place and then simultaneously criticizing governments for not spending money to upgrade old systems. This is an age old problem that if you get the budget once you can spend it to buy useful stuff and then you have to deal with the same thing for years or decades before you'll get budget to properly improve or maintain it. The fact that slashdotters are still surprised and amazed that governments use outdated equipment and software just proves that they've been stuck too long in the basement and need to get out more.

    3. Re:That's because their programmers were skilled by Livius · · Score: 3, Insightful

      A lot of software reach a level of being essentially feature-complete and mostly bug-free, and then could only go downhill from there. Some software was at that point in the '80s, and most of the rest reached that level in the '90s.

      If you have software that
      1) works, and
      2) physically cannot connect to the Internet (which seems to be the only way to genuinely guarantee something is secure)
      then replacing it would have costs risks that outweigh the benefits.

  2. Because it works... by TWX · · Score: 4, Insightful

    ...and is optimized to run on extremely slow hardware. It was often written by people that were extremely talented at optimizing their code because hardware limitations forced them to do this.

    I won't deny that advances in computer language have made it possible to write programs better than they used to be written when machines were extremely procedural and single threaded, but at the same time, the amount of bloat in modern programming afforded by modern hardware has more than made up for it.

    I've seen the progression of software for simple things like workorder systems and asset management and audit get worse over time. The only 'improvement' is access, in that going from an 80x25 text console on a remote system with terminal emulation, to a a full-fledged program running on a specific architecture in a text mode, to a GUI program on a specific architecture, to 'applet' type programs using runtime libraries cross-platform, to web-based access that theoretically are entirely platform independent presuming a minimum browser version, and in just about all cases the further they've gone, the slower clunkier for actual experienced users that frequently use the system. It might not be any better for inexperienced users either if the vendor hasn't taken the time to look at workflow from an outside point of view.

    --
    Do not look into laser with remaining eye.
  3. Awesome! by DogDude · · Score: 5, Insightful

    I think this is awesome. It was good software that hasn't needed to be "updated" every other day like modern software is.

    --
    I don't respond to AC's.
    1. Re:Awesome! by Anonymous Coward · · Score: 2, Insightful

      Oh noes! The software has be running since (some_random_date_in_the_past). We must update now!

      One second there, pardner. This isn't a case of wooden sewer pipes or gas still operating streetlights. Hell, this isn't even a case of two cylinder cars running on super-highways. This stuff has been running since the 1980s, and as old as that sounds to many of you youngsters out there, that was only 25 to 30 years ago.

      My point here is that this is the very first iteration of the modern software cycle. We really have no concrete guide post on how long this stuff can run.

      Is the hardware failing? Replace it.
      Is the software inherently insecure? Upgrade it.
      Are we running out of people with IQs above room temperature so these old languages would be lost? Get more H1-Bs.

      Otherwise I'd say leave it alone.

  4. Re:Dead Programming Language? by juniorkindergarten · · Score: 5, Insightful

    Cobol.

    --
    "Every security scheme that is based on secrets eventually fails." - Steve Jobs
  5. Was it ever acceptable? by rickb928 · · Score: 3, Insightful

    'can't be used with a mouse'

    Which describes an entire era of software. Was ti useful before a mouse was considered so vital, actually before it was even used, or existed? Well, back then it was specified, purchased, and used. Same as now, this is a specious argument.

    'Assessors are prone to make mistakes when using the vintage software because it can't display all the basic information for a given property on one screen'

    Dear, it seems as if either this software was NEVER usable, or are users able to take the necessary care to do their work accurately...?

    'The staffers have to open and exit several menus to input stuff as simple as addresses'

    Ah, the slings and arrows.

    'To put it mildly, the setup "doesn't reflect business needs now'

    As in ease of use, etc, sure. As in it has always worked like this, why do I seem to read this as 'it's old and clunky, and it's the fault of the software that I make so many mistakes'. Where I work, we do have a lot of this. Because we care, and work in private industry, we understand the software, make the necessary adjustments to our habits, and take the time to do it right.

    'It took her office almost four years to secure $36 million for updated assessors' hardware and software...'
    'The design requirements are due to be finalized this summer.'

    What comes first, the chicken, the egg, the funding, or the requirements?

    After all that, has no one in San Francisco government made a CBA case for replacing it? I'm betting they are leaving revenue on the table by not having accurate data. And I'm betting they need to build reasonable, achievable requirements. So many government IT projects fail because the project was designed so poorly from the start.. Examples abound.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
  6. A mouse? by Hugh+Jorgen · · Score: 5, Insightful

    A mouse would not increase efficiencies, look at the horrid inefficiencies of web applications. The lost productivity when IBM forced one of their large financial clients to move from a 3270 green screen app for change management to web app caused outrage. Most UI/UX people do not use the tools they design. Is there "technical debt" here, likely. Does the new app need to support a mouse or be web based? Likely not.

  7. Quote by Anonymous Coward · · Score: 2, Insightful

    "We’re dealing with an irrational public who wants greater and greater service delivery at the same time they want their taxes to be lower." That's not irrational. That's optimistic. Improved service should decrease costs. If the cost of improved traffic management is less than the savings of improved road maintenance than the solution works. City planners work on long term solutions with tech that likely won't change for decades. Saying something was made in the 80s makes it sound old, but doesn't mean it is obsolete.

  8. Re:Dead Programming Language? by Anonymous Coward · · Score: 4, Insightful

    There are probably millions of retired COBOL programmers out there who wouldn't mine working again for a little while. But they don't have "current" experience.

  9. Re:Dead Programming Language? by spudnic · · Score: 4, Insightful

    That still doesn't mean you couldn't put a web based front end that talks back to the cobol running on the AS/400 (iSeries). We do this all of the time. The cobol is probably very fast and efficient. It just needs a better user interface.

    --
    load "linux",8,1
  10. Re:Dead Programming Language? by bferrell · · Score: 2, Insightful

    Yes, but that needs to have monew, SCARCE TAX DOLLARS, allocated. And it's next to impossible to OBTAIN enough to do the basics... Like public transit, house the homeless, pay teachers etc, etc, etc.

    The comment reminds of when my three year old sister was told there was no money to buy what she wanted. She told our parent to just "write some" (write a check). We all laughed.

    How about if we make Apple, Google, Facebook et al pay what they should have instead of stashing it overseas accounts?

  11. Re:It kind of works by cayenne8 · · Score: 3, Insightful

    ...so a huge amount of training is required and employees clearly aren't getting it.

    Have you seen the average worker at the DMV? They're not exactly the sharpest knives in the drawer.

    --
    Light travels faster than sound. This is why some people appear bright until you hear them speak.........