To me this is a valuable write-up because it (a) clearly describes paper cuts accumulated when building with unfamiliar tech and (b) showcases how much nonsense developers are willing to tolerate in the name of "new" or maybe "speed".
Some of the paper cuts described include:
- Inexplicable interaction between the data layer and a hosting service's environment variable
- Migrations that don't work reliably
- Cron jobs that don't work reliably
- Inexplicable caching behavior for serverless functions, requiring an obtuse workaround
- An auth library that makes it hard to... get the ID of the logged-in user, apparently
I dunno, I suppose I'm happy to stick with boring old tech.
Some of the paper cuts described include:
- Inexplicable interaction between the data layer and a hosting service's environment variable
- Migrations that don't work reliably
- Cron jobs that don't work reliably
- Inexplicable caching behavior for serverless functions, requiring an obtuse workaround
- An auth library that makes it hard to... get the ID of the logged-in user, apparently
I dunno, I suppose I'm happy to stick with boring old tech.