This is a write-up about how we built a core part of our product, which is the workflow engine.
Workflows are more complex than most of our features, powered by something akin to a small programming language designed to help model things like users, teams, PagerDuty services, etc. on behalf of our customers.
The post is a behind-the-scenes view of both how the feature works and insight into our goals and methodology as a team, including an evaluation of whether the up-front investment was worthwhile.
I think it's rare that people go into both the technical and human side of building a feature, and hope this can be a case study of how engineering projects get done at a start-up like ours!
1 comment
[ 1.7 ms ] story [ 7.6 ms ] threadThis is a write-up about how we built a core part of our product, which is the workflow engine.
Workflows are more complex than most of our features, powered by something akin to a small programming language designed to help model things like users, teams, PagerDuty services, etc. on behalf of our customers.
The post is a behind-the-scenes view of both how the feature works and insight into our goals and methodology as a team, including an evaluation of whether the up-front investment was worthwhile.
I think it's rare that people go into both the technical and human side of building a feature, and hope this can be a case study of how engineering projects get done at a start-up like ours!