They teach us to break a big file into smaller files for dominance over code and to increase maintainability. Yet they are the first people who throw it out of the window. A wise programmer never accepts things without contemplation.

The worst casing is one in which only intelligence can differentiate between parts. It can be all-lowercased joint words, or it can be all-uppercased joint words.

One aspect of correct semantics is the correspondence of the word plurality with its value. Imagine creating a variable called "student" and then storing the student list in it. Or vice versa, imagine creating a variable called "cars" which holds only one car in it.

I deleted a bunch of resource groups in Azure. They were not being used anymore. I didn't see them in the Resource Group list. But after a while when I wanted to filter the cost analysis base on the resource group, I saw them again.

The base unit for length is the meter. But for weight, the base unit is the kilogram, not the gram. A magnitude prefix is applied for the base unit of weight, while it's not applied for the base unit of length.

While the message shows that the memory is full, ChatGPT claims that its memory is disabled and only works for the current session. What is a session? Sign out and sign in? A single chat? Closing and re-opening the browser? Memory did not get deleted until I deleted it manually from the settings.

Consistency is a must for any team to succeed. However, even a giant like Google can not guarantee it 100%. No matter how big we are, the complex world is bigger. That's why we shift towards progression over perfection.

Even a giant like GitHub can not guarantee that its site content will appear appropriately on all devices. Progression over perfection is the key here.

Event a giant like Google can not make 100% perfect products. It's not clear why they have not used a dynamic height. But we know they've come to a hard situation when they had to choose and sacrifice the dynamic height to gain some advantage in another place.

Even VS Code with Microsoft behind it can not deliver a perfect solution. And we should note that at the time of this post, VS Code has more than 162K stars on GitHub, 28K forks, 2K contributors, 172K issues closed, and over 124K commits. Yet its context menu for deletion has a layout-shift on my screen. Do not aim at perfection. Aim at delivering a good-enough solution.

I believe that someday in the future, we should be able to see that our IDEs and compilers become more intelligent and will support context-awareness for some language constructors, like imports in JavaScript.