Gabriel Schenker

Gabriel Schenker

The work nobody clicks

Picture a bank that must send customers certain notices and statements. A background job is supposed to generate and send them. One day it quietly stops for some of them, and nobody notices. When someone finally does, thousands of letters have to be recreated and sent in batches, and the regulator is involved. It isn't a coding chore anymore. It's a compliance problem.

Continue Reading

One slice, end to end

When I analyse the code of a legacy application, or of an application built with hexagonal architecture, I have a hard time finding the logic that belongs to a business feature such as cancelling a policy. I have to open 14 files and I'm completely lost. A non-technical person has no chance of understanding the code.

Continue Reading

Proof beats permission

You can't ship without a human in the loop if you don't know what you're shipping. Continuous deployment is often sold as a pipeline problem. Write the tests, automate the stages, remove the approval button. But in a regulated environment, the approval button rarely exists because someone distrusts the tests. It exists because nobody can say, with evidence, what is inside the thing being deployed.

Continue Reading Proof beats permission