4 ms·
When I read that kinds of comments I always immediately wonder what people are writing that needs so much scaffolding. And then I remember my workplace's offic
by marcosdumay 4y ago
When I read that kinds of comments I always immediately wonder what people are writing that needs so much scaffolding.
And then I remember my workplace's official architecture... that made my team a huge success case by refusing to follow it.
Of those things you listed that you use it on, only test data need to take some non-trivial amount of time.
- larve 4y agoI work in e-commerce/retail. So it’s things like: - storybook stories to cover all cases of ui configuration - tooling to create reports/import/export of different csv formats - api endpoints, validating incoming data, instrumentation for monitoring - every action and error gets logged as an event for auditing Overall the part of the codebase that is not some kind of scaffolding is like, computing taxes on an order item or something like that. The rest is just shuffling data around and ensuring it is tracked and validated properly. It’s tempting to be clever and devise a killer tool that allows you to write a single data declaration and derive all the rest but that rarely survives an encounter with the real world.