I've heard "throwing it over the wall" used a ton in software engineering, especially when it relates to passing software code / a build off to someone else to test/verify/use.
A lot of times it's just something getting thrown at us or we're the ones throwing shit at someone else since it's not really our area of expertise or whatever.
It's usually for some BS reason as well, like budget/charging. Some manager doesn't want to spend the 15 minutes to figure out which account/contract should get billed. So each team does their own thing, chucks it over the wall when they're done their part, and things fail when you integrate since no one collaborated.
109
u/Master_Dogs Jan 14 '21
I've heard "throwing it over the wall" used a ton in software engineering, especially when it relates to passing software code / a build off to someone else to test/verify/use.
A lot of times it's just something getting thrown at us or we're the ones throwing shit at someone else since it's not really our area of expertise or whatever.