10 ms·
What I'm supposed to suggest is more applicable to relatively more complex and B2B applications but: As a backend engineer, what you create is basically the co
by emilsedgh 8y ago
What I'm supposed to suggest is more applicable to relatively more complex and B2B applications but:
As a backend engineer, what you create is basically the core of the product. Data structures and relations you define will be the limitations of your product.
Coming up with intuitive and good data structures for a complex application can actually be a very challenging task and as a backend engineer most of my time is not spent on writing js or sql, but on product design and specs, so I can create something that is stable and scalable, yet not too rigid, considering that iteration is part of the process and everything you create might be subject to change, specially in startup environments.
- 0xFACEFEED 8y agoMy experience as well. Data migrations make my palms sweaty (not schema migrations but the kind of migration that requires rewriting large amounts of existing data). Picking the wrong data structure is a fast path to data migrations.