Ruby Smells

0 0

Writing good object-oriented code is hard: object boundaries are not always as clear-cut as we’d like, their responsibilities and reasons to change tend to grow over time, inter-object coupling makes isolated testing complicated – and emergency refactorings are tiresome, gnarly and seem to always happen too late. At the same time it’s often hard to see the exact moment when a simple refactoring would save a given class from taking the wrong turn, and real-life projects tend to have real-life sadlines with their tireless chants of ‘let’s refactor this in the next sprint’.

WRUG grudniowy o problemach z OOP i o Rubym 2.3

W następną środę, 9 grudnia, zapraszamy na ostatnie w tym roku spotkanie WRUG, tradycyjnie w Państwomieście, tradycyjnie o 18:30. Tym razem Piotr Szotkowski z Rebased opowie nam o znajdywaniu w ko...