3 ms·
Coding is translation as much as translation is translation. That is to say, it isn't. People who translate are trying to convey meaning. They are not just con
by lordnacho 11y ago
Coding is translation as much as translation is translation. That is to say, it isn't.
People who translate are trying to convey meaning. They are not just converting instructions from one language to another. There is intent, emotion, connotation. And you have to do this elegantly. (Everyone who grew up bilingual has spotted clumsy translations.)
I think this article takes a very narrow view of coding. Yet also a fairly common one. If you're one of the people who just wants a machine to do as you tell it, you'll be about as good as coding as someone who cooks in order to not die of starvation.
In order to really master it, just like in any other walk of life, you need passion. You need to have an aesthetic experience, an appreciation for both function and elegance.
You need to find yourself interested in topics that are not directly to hand. You may never need a Bloom Filter or Erlang, but you'll have heard of them and at least placed them on your map of the field.
Getting back to the article and the cooking analogy, better tools will not replace chefs. We have better cooking utensils and machines than 100 years ago. And yes, you need less effort than before to microwave a meal. But chefs still serve a purpose, and you would never mistake a meal made by a guy at home with what a professional chef makes.
- vegabook 11y ago+1 on the idea that you may never use something but you will at least have heard about it, know it exists and know where to look, in the future if/when you suspect you might need it. Wasn't a huge fan of applied maths during my CS degree more than a decade ago, but am very thankful these days that I had an inkling of an idea about FFTs, PCA, and stochastic calculus, all of which I have had to brush up on and use in recent years.