That's dark! I am glad that I work in a team that doesn't allow such situations.
Often times deadlines are just arbitrary dates coming out of random decisions. There is no reason at all to suffer from this.

At work, I deal with backends with limited extensibility.
The frontend should provide structured form input. After submission, a transformation step should format the data to a single data field as required.
In this case the frontend seems to have limited extensibility too. 🫠

I am far too busy clicking on all the things on the page. Awesome!

That is great! Would you keep them in the final version of your tests?

a few words that I think are important to say on diversity, equity and inclusion in open source (and more generally)

much love ❤️

roe.dev/blog/diversity

To me, a switch toggles between on and off and most likely does something immediately. The latter I would not expect from a checkbox.
I find that radio groups, button groups and segment controls are often difficult to distinguish.
What do you think this one is?
www.giffgaff.design/components/f...

This example code base is minimal and insightful at the same time. Good job!
I love that there is just enough setup, data loading, data handling and testing to make it realistic and give me an idea how it can evolve.

Yes and I generally prefer this version to the others.

Imho bold labels come with several advantages:
* more robust against future design changes by bsky
* easy to distinguish from one other
* text improves comprehension
* almost works like a heading

Your work is inspiring ✨
I enjoyed your UI/UX tips in the past and also your openness to ask for feedback.
It is intriguing and encourages valuable interaction.

hey, how about taze? github.com/antfu-collec...
'npx taze@latest' for regular repos
'-r' flag for monorepos
'-I' flag for interactive mode
there is even support for config files 👀