The rough rule of thumb I would offer is to use an attribute for data that can be used as stored, and a function for data that needs to have something done to it before it's returned. In your example, .shape just returns the tuple as it is stored by the system. It's a straightforward attribute.

Understanding the Context

By comparison, .info () and .describe () both apply filtering/formatting etc to the data before it ... These days I use emoji for "info" ℹ️ or "documentation" 📄 or "source" 📚 Previously, I would put the ⓘ inside superscript ⓘ because it reflects that it is a footnote to the text. Is there an HTML entity for an info icon? - Stack Overflow What is the difference between logger.debug and logger.info ?

Key Insights

When will logger.debug be printed? 188 Each time I want to see the phpinfo(); I have to: Create a info.php file; Write phpinfo(); in it. Go to the browser and type my "thisproject.dev/info.php" I'm on Ubuntu. Isn't there a more practical way to see phpinfo in the browser? Is there an easy way of seeing PHP info?

Final Thoughts

- Stack Overflow Info - Generally useful information to log (service start/stop, configuration assumptions, etc). Info I want to always have available but usually don't care about under normal circumstances. This is my out-of-the-box config level. Warn - Anything that can potentially cause application oddities, but for which I am automatically recovering. Since dotnet core moved back to the .csproj format, there is a new autogenerated MyProject.AssemblyInfo.cs which contains, among others: [assembly: AssemblyCompany("MyProject")] [assembly: