Maxi Contierimaximilianocontieri.com·an hour agoCode Smell 267 - Objects AliasingTL;DR: Use immutable objects to prevent unexpected changes caused by aliasing. Problems Unexpected mutations Difficult bug tracking Unpredictable code behavior Reduced code predictability Increased coupling Compromised thread safety Solutions Use...DiscussCode Smellsclean code
Maxi ContieriforClean Code Cookbookcleancodecookbook.com·Aug 29, 2024Bulgarian Version AvailableTL;DR: You can read Clean Code cookbok in Bulgarian Софтуерните инженери и архитекти, работещи с големи и сложни кодови бази, трябва да могат да ги поддържат и разширяват ефективно. Книгата с рецепти на Максимилиано Контиери ви отвежда отвъд концепц...Discussbulgarian
Maxi Contierimaximilianocontieri.com·Aug 29, 2024Code Smell 266 - Collection AliasingTL;DR: Use immutable collections to prevent unintended side effects. Problems Unpredictable behavior Debugging challenges Data corruption Violation of the Principle of Least Astonishment Premature optimization Unexpected Mutations Concurrency probl...DiscussCode Smellsclean code
VivekProheyvivek.com·Aug 23, 2024🚀 Refactoring Legacy Code: Strategies for Modernizing Old Projects 🛠️Working with legacy code is a challenge that most developers will face at some point in their careers. Whether you’re maintaining an old project, integrating new features, or improving performance, refactoring legacy code is often necessary to ensure...Discuss·13 likes·146 readsrefactoring
Steve SewellforBuilder.iobuilderio.hashnode.dev·Aug 23, 2024Good Refactoring vs Bad RefactoringI've hired a lot of developers over the years. More than a few of them have come in with a strong belief that our code needed heavy refactoring. But here's the thing: in almost every case, their newly refactored code was found by the other developers...Discussrefactoring
Maxi Contierimaximilianocontieri.com·Aug 23, 2024Code Smell 265 - Linguistic ConfusionTL;DR: Naming is hard, don't make it harder with unnecessary accidental complexity. Problems Unclear, misleading, vague, and ambiguous names Redundant terminology Confusing abstractions Cryptic abbreviations Solutions Simplify naming conven...DiscussCode Smellsclean code
Maxi Contierimaximilianocontieri.com·Aug 17, 2024Code Smell 264 - Hanlon's RazorTL;DR: Overdefensive code leads to unnecessary complexity. Problems Unnecessary complexity Confusing logic Hidden bugs Harder maintenance Slower performance Cluttered Code Solutions Simplify checks Trust your logic Focus on essentials Fo...DiscussCode Smellsclean code
Maxi ContieriforClean Code Cookbookcleancodecookbook.com·Aug 11, 2024Clean Code ShortcutsTL;DR: New recipes every two weeks To complement my Clean Code Cookbook, you can now explore new shortcuts on the O'Reilly platform. These concise articles focus on specific coding techniques. The first five shortcuts are available for you to read...Discuss·54 readsclean code
Christian Bonzeletcremich.cloud·Aug 9, 2024Don't let Technical Debt sabotage your product roadmap - Part 2Introduction In the first part of this blog series, we explored the hidden costs of technical debt, revealing its impact on development teams, businesses, and customers. We saw how low code quality leads to slower development, increased defects, and ...Discuss·10 likes·122 readsTechnical Debtrefactoring
Krzysztof Kamil Piotrowskiimp2n.hashnode.dev·Aug 6, 2024The Business Value of Refactoring and TestingOver the years I had to deal with applications and system that have a long history of already being "legacy". On top of that I met with clients/product owners that never want you to spend time refactoring. Some of them will even be aware that things ...Discuss·109 readsRuby