2 ms·
It really depends on what team you're on. When I worked at a bank, I worked on a pretty competent team. We didn't do anything that important, but it did work
by jrockway 13y ago
It really depends on what team you're on. When I worked at a bank, I worked on a pretty competent team. We didn't do anything that important, but it did work pretty well... we had automated tests, continuous builds, and all that good stuff. Most people could open up someone else's code and work on it. (This was largely due to the efforts of one engineer on the team, but you have to give credit to the management for letting him do it :)
At the same time, I would work with other teams, and it just amazed me the kinds of problems they caused. One team worked on streaming data from spreadsheets to other spreadsheets. (Don't ask me why all market data was calculated using spreadsheets.) This was implemented as a set of servers that read from and wrote to a proprietary multicast network that was usually down. It didn't matter, though, because the servers themselves "health checked" each other, and if it detected one was responding too slowly, it would kill and restart it. Except sometimes the killing and restarting caused that server to fail to respond to health checks, so the system basically consisted of servers killing each other all the time. (No, it didn't actually work despite all this. It was a constant source of problems, and was over a million lines of C++! It couldn't even quit without core-dumping because of memory corruption!)
Another team I worked with wrote their application on Java. The company had a policy of only allowing developers to develop on Windows machines, but this team needed to deploy to Solaris. Their solution was to develop and test it on Windows, copy it to the Solaris machines on launch day, and turn it on. But a Windows-only library crept into the core. If this were rocket science, we would not have gone to space that day.
But, there were some pretty good initiatives. One was for a single team to rewrite all software at the bank, in their own C++/C#/Python hybrid, with their own IDE, making all other software engineers obsolete. And despite how crazy that sounds, they actually did a good job! They gave every obscure system at the company a unified API, so a normal user could stitch it all together with a tiny Python program. And write tests for it. It was rough around the edges while I was there, but obviously the way forward. (The big advantage: middle managers had no control over technology, only making a product. So there were no debates ... or rather, horrifyingly bad decisions ... over what servers to buy, what language to use, who would pay for the sysadmins... all they needed to do was design and implement. It was brilliant, and I wish them the best of luck.)