Description: Yegor Bugayenko blogging about object-oriented programming, Java, project management, philosophy, and startup investments; at least one new post every week.
java (6329) programming blog (11) java blog (6) software blog (6) software development blog (2) high quality programming (1) quality of software (1) yegor bugayenko blog (1)
I don’t know what programming language you use, but my experience of recent coding in Java, Ruby, JavaScript, PHP, Python, C++, and Rust tells me that the principle, which I will try to convince you to adhere to — is universal for all languages. It’s about the naming of test files. It may look to you like a question of low importance, but let me try to demonstrate that it’s not. How do you name your files with test classes? How many of them do you create in the src/test/java directory? Where do you place a
Continue...
It often happens, especially in Java, that a few places in the method are potential exception originators. Usually, we make a large method-size try block with a single catch at the bottom. We catch all the exceptions, usually even using grouping . This helps us minimize the noise, which is the exception catching. However, such large try blocks jeopardize maintainability: we are unable to provide proper error context inside catch blocks.