The field that grew with every batch was the wrong one
Today the planned-sessions registry has 118 sessions and none of them has categoria (category), the classification field that grew the most the afternoon I loaded it, a week ago. I didn't delete it by accident: I replaced it, and the session where I created it already warned me why. 89 sessions in one afternoon On September 25, between 1:51 p.m. and 5:28 p.m., I turned a loose numbered list of…
The Dev.to aggregator report discusses a developer's experience with building a registry for work ideas, where the categorization system proved challenging. The developer created the registry over the course of a week, adding sessions in eight passes, with the final count reaching 89 sessions in one afternoon. The categorization field, categoria, was introduced as a closed vocabulary field, but it turned out to be problematic as it grew with every batch, mixing three different aspects of the work.
This led to the removal of the categoria field and the introduction of a new type field. The developer concludes that when a closed field asks for a new value on every load, it's better to widen it rather than keep adding new values, as this can lead to confusion and issues with sorting and searching.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
