3 ms·
They (kind of) have a point though. I agree you should aim to be polyglot, but a particular project may not afford the learning curve if the dev doesn't already
by greenshackle2 10y ago
They (kind of) have a point though. I agree you should aim to be polyglot, but a particular project may not afford the learning curve if the dev doesn't already know the best stack.
For example, I'm working (part time) on a relatively simple backend server for a nonprofit with a tiny budget and short deadlines. I know I can do it cheap and fast in Python, and it will work "ok". Go would be better, and I'd like to learn it, but I'm uncertain I could pull it off in time.
EDIT: Then again, it looks like I could realistically learn enough Go for this project in a weekend. Only problem is there could be data analysis, I know good libs in Python, don't know how hard that would be in Go.
- tscs37 10y agoWell, it's certainly not something that needs to be avoided at all costs but in the long term it can be less efficient and more costly. It depends really, there is no single true language (except LISP) to solve all problems in the entire stack.
- greenshackle2 10y agoAll hail LISP. My main problem with LISP is that I stopped liking Python after learning it.
- deleted 10y ago[deleted]