• Blake [he/him]
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Haha, it’s a fair comment - it’s a team I inherited, it wasn’t my hiring decision. I don’t know what the interview process was like before me, but I’m guessing it was a very old fashioned “where do you see yourself in 5 years” affair.

    I’m pretty sure that they just muddled through by copy/pasting stuff seemingly at random and tinkering until it worked. Which can be a good way to learn, for sure, but it’s not really what you want from a professional developer, full time.

    The guy who managed the team before me didn’t believe in object oriented design, and not in a cool Haskell way, in a really old fashioned “I can do everything with batch scripts” way. The team was using a programming language that was so old that they were using dosbox to compile it because the compiler was a 16-bit application.

    • theshatterstone54
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Because the compiler was a 16-bit application

      Name the language, mate. This sounds a bit too insane to be true.

      • Blake [he/him]
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Yeah, it was called DataFlex. The vendor has released new versions of it called Visual DataFlex (VDF) and then renamed VDF back to DataFlex, but this language was what we called “character mode” DataFlex. It’s still used by the company as their main data entry application even today and a lot of their processes still are written in DataFlex. A lot of the work that my team did was rewriting a lot of the old crap in C#, but there was just so much of it built up over the decades.