Antipatterns are common but ineffective solutions to recurring problems, representing the opposite of best practices or design patterns.
Organizational antipatterns like analysis paralysis, bicycle-shedding, and design by committee lead to overthinking trivial issues and lacking a unified vision.
Antipatterns like adopting bleeding-edge tech prematurely, neglecting cash-cow products, or escalating commitment to bad decisions can derail projects.
Harmful management styles like micromanagement, seagull management, and fostering silos or groupthink can destroy team morale and productivity.
Project failure antipatterns include the death march, ignoring Brooks's Law by adding people to a late project, and allowing uncontrolled scope creep.
Developers should avoid antipatterns like overengineering solutions, gold plating tasks beyond requirements, and using smoke and mirrors to fake progress.
Architectural antipatterns like the big ball of mud, spaghetti code, and lasagna code result from a lack of structure and consistent refactoring.
Common code-level antipatterns include circular dependencies, god objects that know too much, and inefficient busy waiting loops.
Poor coding habits include handling every edge case individually, hiding errors, hard-coding values, and cargo cult programming without understanding the 'why'.
Antipatterns like copy-paste programming, the golden hammer mindset, and dependency hell arise from misusing code, tools, and libraries without proper strategy.
21:39Johannes Hansen
46:48Stefan Priebsch
28:13Erick Wendel
40:17Luca Mezzalira
42:02Simon Lasselsberger
28:40Reka Horvath
47:05Luca Mezzalira
24:38Carola Lilienthal
.jpg?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
IKEA
Amsterdam, Netherlands
Speech Processing Solutions
Vienna, Austria
Saby New Compy
Karlsruhe, Germany
Antal International
Antal International
Antal International