Read the previous episode here:
Software has a strange way of rewarding patience.
When Marta first introduced TPF into the project, some of her colleagues quietly wondered if the pipeline would become just another obstacle everyone would have to avoid. A few months later, those worries faded. The framework became background noise, the business continued to develop, and people only discussed the architecture when they really needed to.
Marta thought that was probably a good sign.
In the meantime, the application had evolved. A second developer joined the team, another carrier integrated, customer support got a small dashboard to check failed orders, and finance requested a daily reconciliation process. None of these changes altered the application's core function. They simply made it more useful.
Looking back, Marta realized this was exactly the evolution she had hoped for. The pipeline lengthened in some areas, new operators appeared, the generated contracts changed with the business, yet the application felt reassuringly familiar. Reading the pipeline from top to bottom still felt a lot like reading a business process. The architecture remained mostly hidden.
At least, that’s what she thought.
Daniel spent most of the previous week adding support for another shipping provider. The implementation went smoothly, but during the code review, he hesitated over a change that seemed harmless at first.
“I changed the pipeline here,” he said, pointing at the screen, “but I’m not sure the business has changed.”
Marta leaned in.
The modification was exactly what she expected. One integration replaced another. The tests passed. The contracts still matched. It was technically sound.
“What’s bothering you?”
Daniel took a moment before he replied.
“I’m not sure yet.”
He closed the pull request without merging it.
Later that afternoon, Marta found herself at the coffee machine with Elena. Elena had a knack for listening just enough to ask the right question.
“You look like you’re debugging something that isn’t broken,” Elena said.
Marta smiled. “Daniel changed a pipeline step. Everything works. But he thinks the business didn’t change.”
“And you think?”
“I think he’s right. I just don’t know why.”
Elena leaned against the counter. “Walk me through it.”
Marta hesitated for a moment but then began.
“Orders come in. We validate them. We reserve inventory. We authorize payment. Then we hand things off to the warehouse.”
“Sounds like a business,” Elena said.
“It does. But in between, there are steps that don’t feel like that. We wait for a payment provider. We publish messages. We react to callbacks.”
Elena nodded slowly. “So?”
“If I read the pipeline as ‘this is how our business works’, some parts feel... different.”
Elena picked up her cup. “Different how?”
Marta thought for a moment. “If we stopped validating orders, the business wouldn’t exist. The same goes for inventory or payment decisions.”
“What about the other parts?”
“If we changed how orders arrive, or how the warehouse gets notified, the business wouldn’t describe itself any differently.”
Elena smiled. “So some steps are the business. Others are just how the business talks to the world.”
Marta blinked. “Yes. Exactly.”
They stood there for a moment.
“So what will you do about it?” Elena asked.
Marta shrugged lightly. “Nothing dramatic. Just… stop pretending they’re the same thing.”
Elena laughed. “That’s usually a good start.”
Back at her desk, Marta reopened the pipeline and read it again, this time thinking of Elena’s words; some steps showed decisions the business cared about, and others showed conversations the application needed to have.
They were all necessary, but they were not the same.
She leaned back, thinking how right had Daniel been to hesitate and point out the new code hadn’t changed the business, and revealed where the business actually was.
SOCIAL SHARE CARD GENERATOR