Writing prose in two languages (or how I coded some bits in application code, other bits in database code)

I didn't code it. But I'm part of the team in charge of completing the project and maintaining it.

Oh yeah. The project consists of an integration layer between different systems; it is implemented on top of Oracle's SOA Suite. There are many BPEL processes, ESBs, web services, etc.

Since it's Oracle's SOA Suite, we use JDeveloper (dear god, don't get me started) and Oracle Database. We color-coordinated everything - we're cool like that. The only other caveat is that there are a few stored procedures here and there, as well as some triggers. Triggers. Containing business logic. Like, if this new row in table X has the "status" column set to 123, then update tables A, B, C, D and E with status 456.

It's pretty much guaranteed that you will fail to pin point this mechanism in a reasonable amount of time the first time you come across such a scenario. It's a pretty big context switch and will surely be the last thing that you will check.

This post on StackExchange reminded me of all this while I lay cool sipping on a cold beer at my home.