Please log in to watch this conference skillscast.
Not taking into account what a piece of software represents in real life can lead to higher complexity, additional development costs, difficult refactorings, and ultimately, a software that no longer scales. If it gets far enough out of hand, at some point, new features cannot be implemented if they’re not compatible with the current architecture, because they would be too expensive to implement. In this session, we’ll look at some real-life examples and at some of the things to keep in mind in order to avoid the above-mentioned issues.
YOU MAY ALSO LIKE:
Why Software Should Reflect Real Life
Freelance; Consultant; Full-Stack Software Engineer