I think it’s more useful to look at the tasks models haven’t gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are:
- Deep familiarity with the codebase
- Technical communication
I think it’s more useful to look at the tasks models haven’t gotten better at over time, and the tasks that are hard for them get better at in principle. The two best examples of these are:
- Deep familiarity with the codebase
- Technical communication
One of the biggest issues I see is the overcomplication of minor things. OP’s link has examples. It wants to write every piece of code as if it is a user facing API. It will try to triple check every piece of memory that enters a function, even if the function that called it had it hard coded. It’s really insane when it decides that due to all the error checking, it should create a helper function just to hold all of the error checking code for something that was spun up with the class default values.