3 ms·
To play devil's advocate, a software craftsperson would ideally use the right tools for the job. You could fire up Groovy and Spring for a REST API that essenti
by lllr_finger 8y ago
To play devil's advocate, a software craftsperson would ideally use the right tools for the job. You could fire up Groovy and Spring for a REST API that essentially takes JSON from a source/sources, transforms, and returns... but there are easier languages and frameworks and much more performant ones.
The developers I've met with this argument have usually been doing one stack for many years and don't want to do anything new or uncomfortable. It's like watching someone try to cut brush with a butter knife.
- dave_sid 8y agoI agree with you that being comfortable with a stack is not a good reason to use it. Developers need to keep up with emerging languages. Team leads also need to be doing this and provide direction. But as I said, there is more to the success of a project that the language and I think people get hung up on this. Yes look at all the options, but agree on a language/stack and move on. Also, give just a tiny thought as to whether you will be able to hire any developers to support the thing in 3 years. Boring yes, but kind of useful.