Anti-Patterns: An Overused Development Term

Anti-pattern is term that gets thrown around a lot but I don't see too many explaining how or why they're using it so I thought it'd be worth taking some time to explain what they are and why they're not always a bad thing.

==========Support The Channel==========

=========Video Platforms==========

==========Social Media==========

==========Time Stamps==========
0:00 What Is An Anti-Pattern
1:04 Anti-Pattern Examples
4:08 Not All Anti-Patterns Are Bad
5:29 Depends On The Context
6:57 Code Smells
8:04 Outro

==========Credits==========
🎨 Channel Art:
All my art has was created by Supercozman

#AntiPattern #BrodieRobertson #SoftwareEngineering

🎵 Ending music

DISCLOSURE: Wherever possible I use referral links, which means if you click one of the links in this video or description and make a purchase I may receive a small commission or other compensation.

[wilfridtaylor]

Anything I don't like is an anti-pattern :p.

[dczoekj]

Anti-patterns are problems that need to be fixed (keeping single database connection in multithreaded environment), code smells are potential problems and they may need to be fixed (mailing code copied multiple times OR using javascript to fix CSS). Code smells are often not problematic, and don't reduce readability, and the problem usually spans across multiple modules or classes, so they're harder to identify and fix.
Also having dependencies is not a problem. The problem is when you fit your dependencies in order to get things done. For example MVC models that store dates as strings, because casting and null checking can be annoying.

[akarimarisa]

The mainly reason I hate Java is, use Java basically is using spring framework or Android libs. And the only reason I use Java is back end service build. If I want to write some tools, there's Python or shell script. I still don't know why people keep using it.