AI in production: RAG, evals and prompt injection
Anybody can build a demo that impresses. What separates the demo from the product is three disciplines, and most teams have none of them.
Software engineering and applied AI
I am Gabriel Dias. I work on payment infrastructure and production AI systems at Woovi. Here I write about the boring decisions nobody covers in tutorials: the ones that show up at 3am, with users waiting.
Library
Reading path
22 articles in learning order.
Anybody can build a demo that impresses. What separates the demo from the product is three disciplines, and most teams have none of them.
Two questions come up in every company: why did the report take down production, and why is the number on my dashboard different from yours. Both have the same root cause.
The demo works in five minutes. What nobody shows is the evaluation, cost and failure layer that separates a prototype from something a real user can survive.
Three techniques that let you safely change a system you did not write, do not understand, and cannot stop.
Tests do not exist to prove the code is right. They exist so you can change it tomorrow without fear. That change of goal reorganises everything.
Talk to me
No form and no mailing list. If you disagree with something I wrote, or want to tell me how you solved it, the conversation goes straight to me.