4 ms·
I think there is a fallacy that people can pick up a new language in short time. If you know C, you will write C code in the new language for a while. It takes
by Ididntdothis 6y ago
I think there is a fallacy that people can pick up a new language in short time. If you know C, you will write C code in the new language for a while. It takes quite a while to pick up the new concepts. Good documentation geared towards experienced developers would be very helpful.
- rileymat2 6y agoIt depends on your approach, if you try to learn the idioms as part of the learning process as opposed to just syntax, you can prevent this.
- bsder 6y agoYes and no. Learning Rust is a good example. Sure, you can learn the borrow checker and other stuff fairly easily. Patterns are fine. Error checking was a bit more iffy before "?". And then you try to build a doubly linked list and the language fights you at every single turn. (for good reason, but it fights you nonetheless). Nobody expects that. That's the kind of thing that languages often aren't good at documenting.
- Royalaid 6y agoPersonally I see this a lot in normal interview style questions. They are geared towards an imperative approach, find this thing in a 2d matrix based on some way of manipulating the indexes is a common example. If you try a functional approach it is possible but often times akward or super dense looking code much like the double linked list example above. I feel like this comes from the fact that while languages are extremely easy to bend into a shape that fits the problem and take a long time to learn so it's often easier for programmers to put out a bad solution instead trying to get the problem and the language to meet in the middle.