hanse dent
908 posts


@AnthonyHagi @arktypeio That’s how the JSON Schema spec says it should be
English

@arktypeio Is there a reason why you didn’t do “required: true” rather than the array?
English

the best engineers in the world have no idea how to make a navbar like this today
it's like roman concrete - a lost art that we can never get back

Web Design Museum@WebDesignMuseum
The diversity of horizontal navigation in 2004 #WebDesignHistory
English

@t3dotgg I’d love a programming language with first class SQL syntax support. No string manipulation.
English

@housecor Don’t throw. If your app has actual users you are bound to struggle during deployments where an old client is incompatible with new server code.
Even worse if this is not a web app
English

@ChShersh `git commit -m` should finish before i hit enter
use editor onsave hooks and/or autofix on explicit demand locally. ci will yell if forgotten
English

@bradgessler None that needs auth. Mostly search.
Anyway, my issue is only sites where I know upfront that I use a PW, and then it is just an annoyance. Worsened by the fact that my non-mainstream manager most often can’t handle it.
English

@hanse So you don’t use any Google sites?
Also, who said it’s going to ask for a password? OAuth and email link login flows don’t ask for passwords.
Finally, password managers can handle multi-screen flows.
English

You’re doing it wrong if you ask for a username and password on one screen.
It should be two:
1. Ask for the identity
1.5 Check how the identity wants to authenticate. Could be SAML, OAuth, Email link, or password.
2. If password, show on the second screen.
Theo - t3.gg@theo
Quote tweet this with your spiciest web dev take
English


















