4 ms·
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
by davepeck 3y ago
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.
- isaacsultan 3y agoThanks Dave! That's a great summary of my experience. Most of my experience has been with a more "boring" stack, so I was interested in trying some of the more "hyped" technology choices, to see if I was missing out on anything.
- davepeck 3y agoYeah, makes sense. I’m also in a phase where I get to start a lot of new low-stakes web projects, so I’ve made a point of adopting at least one new-to-me tool for each. I love typescript, and am generally happy with modern front-end tooling, but the node back-end ecosystem drives me bonkers — too many paper-cuts from too many tools along the lines you’ve documented here — and has me regularly retreating back to Python or Ruby land.