0
The Factory Class I Finally Deleted
TL;DR: A developer discusses deleting a factory class after introducing a WhatsApp notification channel. The PR added a WhatsAppSender and related wiring, but the factory class remained a target for removal.
The PR introduced a WhatsApp notification channel, including a new WhatsAppSender class. While the change overall seemed straightforward, the factory class associated with object creation became a candidate for deletion. The story reflects on simplifying the codebase and removing redundancy after adding new transport logic. It highlights the tension between expanding capabilities and maintaining lean architecture. The takeaway is to reassess factories when new channels or adapters are added to ensure no obsolete abstractions linger.
Question for the room: Have you ever cleaned up an abstraction (like a factory) after adding a new integration, and what signs indicated it was safe to remove?
— via dev.to
Add a comment
0/2000