Get the latest tech news

In which five different paths lead to methods

y made a change in a codebase I've been working on which illustrated an interesting trade-off around modeling in software. The project was Taverner, an IRC server written in Fennel.

All the data for a channel is exposed in the table that gets passed around to other modules, and it isn't clear which fields are safe to use and which are implementation details which might change later on. I absolutely need the ability to fix bugs and add features while the server is running without disrupting the users, and that meant as nice as this code feels, it's not going to cut it. Even though the class-based approach is my least favorite, it could suit some projects if the people working on the codebase have a background in object-oriented languages and aren't comfortable changing their style.

Get the Android app