Thread replies: 4
Thread images: 1
Thread images: 1
File: sdfoiwrehwdsqoemrlkwnjlkds.jpg (57KB, 800x732px) Image search:
[Google]
57KB, 800x732px
How important is it for a programmer to understand the huge amount of jargon on the fly?
take this website for example:
https://www.rust-lang.org/en-US/
>zero-cost abstractions
>move semantics
>guaranteed memory safety
>threads without data races
>trait-based generics
>pattern matching
>type inference
>minimal runtime
>efficient C bindings
At first look, I have no clue what half of the "features" mean. Will professional developers think im retarded if i cant hold a conversation using terms like that?
>>
>>56071099
Only bro-grammers talk like this. Good developers who aren't insecure about their skills talk more casually about programming. You might hear the odd technical term here and there, but don't worry about it too much. Don't be afraid to ask "what does that mean?"
>>
>>56071099
These terms come mostly from programming language theory and have clear, well-defined meanings. If you have no specific interest in that and you don't have enough experience to have already learned multiple languages with different paradigms, is not surprising that you don't know what these things mean. It will come naturally with time.
>>
>>56071099
been programming for years. and years.
nobody needs phrases like that to program.
hipster coders might but they are constantly making stuff up desperately trying to sound knowledgeable.
Thread posts: 4
Thread images: 1
Thread images: 1