Is a boolean parameter a sign of a deeper problem? Learn to spot common code smells before they lead to technical debt.
#1about 3 minutes
Defining code smells and their importance in development
A code smell is a surface indication of a deeper problem, and identifying them improves communication, testability, and reduces technical debt.
#2about 6 minutes
Identifying bloaters, code that has grown too large
Bloaters are classes or methods that are too large, such as long methods, large classes, primitive obsession, long parameter lists, and data clumps.
#3about 5 minutes
Recognizing OOP abusers that misuse object-oriented principles
OOP abusers are code smells that incorrectly apply object-oriented concepts, including switch statements, temporary fields, refused bequest, and different interfaces.
#4about 4 minutes
Understanding change preventers that hinder future development
Change preventers are code structures that make modifications difficult, such as divergent change, shotgun surgery, and parallel hierarchies.
#5about 4 minutes
Spotting dispensables, the unnecessary parts of your code
Dispensable code smells are unnecessary elements that can be removed, including lazy classes, data classes, duplicate code, dead code, and speculative generality.
#6about 4 minutes
Analyzing couplers and issues with class relationships
Couplers are code smells related to excessive or improper coupling between classes, such as feature envy, inappropriate intimacy, message chains, and the middle man.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
02:26 MIN
Recognizing common code smells in your codebase
I will have to refactor ! And now ? Refactoring Techniques in Java
03:49 MIN
Identifying common code smells in test suites
Dirty Tests And How To Clean Them
02:11 MIN
Building a sustainable culture of clean code
Breaking the Bug Cycle: TDD for the Win
01:40 MIN
Differentiating good and bad reasons for refactoring
Product Managers' Eternal Battle with Refactoring
01:57 MIN
A summary of the clean code imperative
The Clean as You Code Imperative
01:54 MIN
Conclusion and key takeaways on refactoring
I will have to refactor ! And now ? Refactoring Techniques in Java
03:37 MIN
Preventing architectural decay and code structure issues
11 Tips to Make The Most Out of Your First World Congress The world’s most awesome event for developers is taking place in less than a month! It’s been far too long since the last time we met in person, but that’s only going to make this year’s WeAreDevelopers World Congress a truly special experience. Conf...
Anna Lysiuk
10 Coding Habits That Make You a Bad ProgrammerComputer programming is crucial in today’s automated world. It makes it possible for people to interact with machines more efficiently and accurately. Computer programmers use a variety of computer languages to create codes that make it possible for ...
Daniel Cranney
The real reason we document our codeThe world of software development moves fast. Technology is constantly changing, as are the tools we use with it, and even the role of a programmer is itself constantly in flux. However, some aspects of software engineering are so foundational that w...
From learning to earning
Jobs that call for the skills explored in this talk.