ca.2009, I was assigned to the most deranged software task of my life. Our lab machines that ran testcases had a small program that polled a server to see what tasks the machine should do (run a test, install suchandsuch software, etc)
Comments
Log in with your Bluesky account to leave a comment
This application was *ancient*, probably older than a lot of you reading this post. It was written in Visual Basic (pre-.NET), but the new OS images didn't have the VB runtime anymore, so machines could no longer bootstrap
This is, objectively speaking, a doomed endeavor. This app had to run for weeks at a time. VB has a garbage collector, and C++ does not, so a single memory leak here will eventually brick a lab machine and require human intervention
Regardless, they hired a contractor team to do the port, but the contractors were "done" when the project compiled, not when it worked. Making it actually work (at all!) was our job
The app crashed immediately on startup, and leaked like a sieve after we fixed the crashes. We eventually found all allocating paths and got the leaks fixed, but the best bug remained
Comments
Figure out what was doing
Use modern techniques to duplicate
But instead of rewriting it (look at the code, determine what it does, write a new app), they decided to *line-for-line port* the VB6 code to C++
"hines available."
"etwork response"
"ost:8000/getTasks.aspx"
"pected"
These were recognizable as strings from the other parts of the UI. WTF?