I mostly disagree with the article.
> Is the code readable?
Readable code may not be good code. More readable code almost always means less efficient code. Readability is a trade off.
> Is it easy to extend?
Changing requirements are a thing for sure. But in almost every cases I came across, planning for shifting requirements always misses the point. It is much better to stick to your current requirements and keep your code simple, than introduce things that complicate your code for requirements that may or may not happen. Extending simple code is simpler than undoing code and replace.
> Is your code efficient?
It's very hard to self determine whether one own's code is efficient. Almost every one will think their code is efficient.
> can you write it quickly?
Again people tend to think that they are fast at writing code whatever their actual speed.
-- the reality is that it's really hard to qualify good or bad code. Self assession is particularly useless.
> Is the code readable?
Readable code may not be good code. More readable code almost always means less efficient code. Readability is a trade off.
> Is it easy to extend?
Changing requirements are a thing for sure. But in almost every cases I came across, planning for shifting requirements always misses the point. It is much better to stick to your current requirements and keep your code simple, than introduce things that complicate your code for requirements that may or may not happen. Extending simple code is simpler than undoing code and replace.
> Is your code efficient?
It's very hard to self determine whether one own's code is efficient. Almost every one will think their code is efficient.
> can you write it quickly?
Again people tend to think that they are fast at writing code whatever their actual speed.
-- the reality is that it's really hard to qualify good or bad code. Self assession is particularly useless.