This is a great haiku. Sakura remind me of many things as well.

You mean from imgur? Yes.
Fancy seeing you here.

I love my volunteer tomato plants.

The ones that bloom from fruit that fell to the wayside from the bunnies brave enough to make their way through the marigold and catnip.

As a federal worker, I am beyond pissed that the past 40 days are for nothing.

Way to make our sacrifices mean nothing.

To paraphrase Martin Luther King Jr., I am beyond disgusted with the moderate who says that now is not the time to fight.

to do a (.contains any) for each set of roles for each possible view. That way if a user has any role in each possible view, that view unlocks. This is straight linear time. If I use a hash, it becomes constant time, but what real world savings does this have, if any. Plus the typing. Ugh. 😅

I didn't explain it well enough. There are multiple user roles with various levels of access and two super user roles. A given person can have any combination of roles. Each role allows access to a different view. So, my initial algo was to assign each view to an array of roles then use LINQ (1/2)

I'm coming into this app as a fresh set of eyes. It was written about ten years ago by contract and it's a mess. If I had my druthers, I'd tear it down and rebuild it, but I can't.

Also, this is the only page that has this visibility issue. The original devs were...special.

So just a lot of ctrl-c, ctrl-v, then change a couple of variables. Rinse/repeat. I hate it. Lol.

Thought about using a set of hashes, maybe I'll do that. XD. I wonder how much that would improve runtime.

It's a page load function for displaying certain items depending on a user's role which can be any combination of 10 roles. So it's like

if (userRoles.Any(x => role.Contains(x))) then display y.

But there are 15 possible display combinations, so I get to iterate each one to flip visibility.