3 ms·
I didn’t mean just any negative impact like getting tired from context switching or feeling exhausted because the workload is high. What I meant was: Will you
by geraneum 4y ago
I didn’t mean just any negative impact like getting tired from context switching or feeling exhausted because the workload is high.
What I meant was: Will you lose it if you don’t use it?
Maybe you won’t, I am not certain. Or maybe you will and you don’t see it now because the “net win for syntax recall just by giving it gentle nudges towards intent” relies on your hard earned ability to understand the code which is gained partly through exercise. You’ve already done your exercise.
I wouldn’t form an opinion just yet. For now we can ask the questions.
Edit: wording of the first sentence for clarity
- FeepingCreature 4y agoBut losing it may free up resources to gain other things. Like how "losing" assembly skills allowed people to dedicate more capability to higher-level approaches.
- geraneum 4y agoSure that could happen. Nothing against that. But I am not fully confident. As a counter example, we have ORMs. They bring value but I have seen enough devs who are too reliant on it and don’t develop a good understanding of how the underlying database behaves. This could be actually detrimental to the work. Maybe we will have a mixed result similar to ORM example. It can lower the barriers to entry, which is good, but won’t eliminate the need for deep expertise. At least initially.