information literacy

Whataboutism and both-sides as information manipulation

concepts

Additional interface nuance

The big pieces of the interface – the ones users will focus on and likely conceptualize as the key experience – are further supported. These are objects that support the logic, but users are less likely to key into as characterizing the interface.

concepts

Offer as a substitute interface

People are used to advanced searches. In some sectors, it’s so expected that not having one is tantamount to hanging a sign, “we’re not serious or knowledgable”.

concepts

Focus inclusion to current use

The boxed sets are more information, which means a higher cognitive load. They also require more of a footprint.

concepts

Enable any available metadata

Once the logic for shifting from “Include” to “Prioritizable” is available, it’s another stemming search to add an unexposed filter.

concepts

More than just dropdown

There is absolutely nothing in the dropdown object that says it’s the only viable use case.

concepts

Non-dev interface management

One thing that has become very clear to me is that how we code to interface with data has patterns. They are complex. They have patterns based on broad use, and patterns tailored to specific use, and patterns to signal and help, and design patterns, all of which can be

concepts

Behind the user-facing artifacts

The logic shifts in here might feel intense, but: they are all explicable, none of them are new, and there's a good chance the team could reuse code and actually be able to touch it for optimization/update as part of the sprint. 🥰

concepts

Looping

Where this truly shines is where people are being creative about what they are looking for. My aha use case was fabric. This is a system that is useful for any product set where your customer base knows what they are looking for, knows how a shift is going to

concepts

LBLD: Layers, Binaries, Loops, & Dynamics

Here's where I have to caveat that I do not code (I'm an angry dev; I enjoy smiling). I understand how the information needs to function, not how the code will manage it.

concepts

Three piece suit

A piece of fabric doesn't become a suit vest just for wrapping around a body. It needs buttons, it probably has lining, maybe pockets. It's the whole form, altogether, that will look like a vest whether it's on a body or a hanger.

concepts

Filter management

Filter management is three prongs long term.  My gut reaction is that 1 & 2 could be swapped and are probably built at the same time. The third can come down the roadmap.