The concept of schemas in database design is being discussed in the context of software development, specifically with regards to handling schema-free and document-oriented databases. The author argues that while it may be possible to go without schemas, doing so can lead to unnecessary difficulties and scalability issues. A comparison is made between having a standardized language within an organization versus no standardization, highlighting the benefits of standardization in communication and data representation. An example of a smartphone app collecting temperature data and sending it back to HQ is used to illustrate how the lack of schemas can cause problems for downstream consumers. The author concludes that using schemas provides a self-contained and enforceable contract between writers and readers of data, making testing compatibility simpler and preventing corrupt or incompatible data from being published.