Urgent.News

What's breaking now, across thousands of outlets.

Tech

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 planned-sessions registry contained 118 sessions, none of which had a categoria (category) field. This field had grown the most during the afternoon of September 25, when 89 sessions were added. The registry was created by loading a loose numbered list of work ideas into the system, without any pre-defined sprints, roadmap, or deadlines.

The classification axes were added on a batch-by-batch basis, with each new batch bringing one new field. The categoria field emerged from the need to improve performance and answer multiple questions with a single field. However, as new values were added to categoria each time, it began to sort improperly and lose its intended purpose.

When blocked sessions were grouped with other topics, the need for a new field, lote (batch), arose. The process of reclassifying 83 sessions required only one run instead of 81 edits. Despite the growth in sessions, 26 of the 83 sessions still lacked a category. The trade-off was that while discovering the axes as they were added allowed for faster loading times, it also introduced a field that answered multiple questions simultaneously.

The decision was made to replace categoria with a type field, which was removed from the schema as a breaking change and moved its values to tags with no loss. Today, there are 118 sessions, 8 completed, and none with a categoria field. The first sprint began with 6 sessions and has since grown to 32. The issue lay in the fields that answered a single question, as they grew with every batch, ultimately causing confusion and the need for a reclassification.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

More from Friday 2 October →