DevGex Search

This article delves into the historical controversies and practical value of Hungarian Notation, distinguishing between Systems Hungarian and Apps Hungarian. By analyzing Joel Spolsky's key insights in 'Making Wrong Code Look Wrong' and integrating modern type system design principles, it argues for the rationality of semantic prefixes in specific contexts while advocating type system enforcement as the ultimate solution. With code examples illustrating both approaches and multilingual practical advice, it guides developers in making informed naming decisions.

This article explores the origins, purposes, and controversies of the m_ variable prefix in programming. Originating from Hungarian Notation, the m_ prefix identifies member variables to enhance code readability and IDE support. It analyzes its necessity in languages like C++, while presenting opposing views from Clean Code, which advocates against prefixes. Through comparative examples, the article evaluates different naming styles and discusses modern best practices for when to use the m_ prefix or alternatives.

This article explores the design philosophy behind Java's decision to omit the I prefix in interface naming, analyzing its impact on code readability and object-oriented programming principles. By comparing traditional naming practices with Java's approach, it explains how interface-first programming is reflected in naming conventions and discusses best practices in modern frameworks like Spring. With concrete code examples illustrating patterns such as DefaultUser and UserImpl, the article helps developers understand the deeper logic of Java's naming conventions.

This article delves into Java interface and implementation class naming conventions, critically analyzing the redundancy of traditional prefix-based naming (e.g., ITruck, TruckImpl) and advocating for semantic naming strategies. By examining real-world cases from the Java standard library, it explains that interfaces should be named after the types they represent (e.g., Truck), while implementation classes should be distinguished by describing their specific characteristics (e.g., DumpTruck, TransferTruck). The discussion also covers exceptions for abstract class naming, conditions for interface necessity, and the role of package namespaces in reducing redundant suffixes, emphasizing adherence to the DRY principle and the essence of type systems.

This paper focuses on the controversial coding standard of prohibiting multiple return statements, systematically analyzing its theoretical basis, practical impacts, and alternatives. Through multiple real-world case studies and rigorous academic methodology, it examines how unreasonable coding standards negatively affect development efficiency and code quality, providing theoretical support and practical guidance for establishing scientific coding conventions.

This article provides an in-depth exploration of the dollar sign ($) prefix convention in JavaScript variable naming, with particular focus on its practical applications in jQuery development. Through detailed code examples and comparative analysis, it explains the advantages of using the $ prefix to distinguish jQuery objects from regular DOM variables, including improved code readability, maintainability, and team collaboration efficiency. The article also discusses the scope and best practices of this convention, offering practical naming guidelines for JavaScript developers.

This article provides an in-depth exploration of various methods for iterating through DataTable rows in VB.NET, with focus on DataRow collection iteration mechanisms. Through comparative analysis of traditional For Each loops and simplified syntax, it thoroughly examines performance optimization in data access and code standardization. The discussion extends to table-level iteration concepts, demonstrating efficient handling of large datasets through practical examples while adhering to Microsoft's latest coding guidelines.

This paper provides an in-depth examination of three primary methods for retrieving column names in SQL Server 2008 and later versions: using the INFORMATION_SCHEMA.COLUMNS system view, the sys.columns system view, and the sp_columns stored procedure. Through detailed code examples and performance comparison analysis, it elaborates on the applicable scenarios, advantages, disadvantages, and best practices for each method. Combined with database metadata management principles, it discusses the impact of column naming conventions on development efficiency, offering comprehensive technical guidance for database developers.