When I think of bows, my mind auto points to Sailor Moon, but there must be more variety I've never noticed. In Sailor Moon, each of the girls had a bow that reflected their personality and matched the rest of their outfit. As a set, they're pretty iconic, and the bows were functional (for transformation, ofc). Arguably, Kiki's bow from Kiki's delivery service is lively, but I'd also say the magic comes from the Miyazaki's animation. Would a big bow even move like that? I like the costuming details on the Sailor Moon bows, but the volume in Kiki's is undeniably cuter.

Web devs: what's up with this trend? For enterprise apps, I get it…single sign-on needs to detect what your email domain is to send you to your identity provider. For consumers, I feel like it's gotta be one of these reasons:

• Users don't know about the tab key being able to move to other fields on a page
• Mobile users don't really have a tab key, despite there being "previous/next field" arrows on the stock iOS keyboard since its inception (Android users, help me out please)
• Users tend to hit Enter after typing in their username, leading to a form submission with a blank password
• Security, maybe? In the past I have sent a link and a password in separate emails or separate communication methods entirely. Are you hashing/salting these separately for better MITM mitigation?

Did your UX team make a decision? Are my password managers forever doomed to need a "keyboard combo" value for every entry from now on?

Non-devs: do you prefer one method over the other? If so, why?

Tildes maintainers: selfishly, thanks for keeping these together :)

I suspect many don’t write anything down and do this largely by intuition/experience but I want to tease out some ideas.

when it comes to describing and designing a system from a blank piece of paper, what are the parameters you think of?

I’m thinking napkin sketch level of software design.

So things like:
Number of users, are they concurrent users, what load dimensions there are (disk IO, network IO etc.), target platform (everything is a web app these days), how do you design/visualise the data model?

Any decisions or constraints that impact what and how you build a proof of concept / MVP? How do you document this? How do you test it against the finished software?

My buddy and I grew up in the 80's and 90's together in a mostly analog world, so we spent a bunch of time outside on bikes and getting dirty. We played board games a lot with each other and our family, but as the turn of the century hit we were more engrossed in technology.

We both ended up in careers around creative design and technology, but still have that nostalgia from our past. We have been hanging out this past year and started streaming on Twitch so we can put our skills to use in a fun hobby.

Since January we had the idea to see how far we could push AI to help us create a board game! It's been a fun time starting from nothing and producing something. While the AI craze and controversy are out there. We realized that going all AI to make a fun game wasn't going to work. We've been using it as a tool but adding a lot of ourselves to it.

We hope to give a free downloadable and 3d printable version out. We are excited to get where we are and have an actual fun game. We figured we'd share our progress of the game. Frostbite: The Curse of Doctor Frost

Does anybody know of communities that would be into downloading, printing, and playing board games?