Out of curiosity why is writing everything as a single element type more ergonomic? I’ve not done frontend web dev in a while and using <p> <h1> and so on seems like it would be more ergonomic to express intent.
We use ui tests specifically for testing accessibility, analytics and data passed along during navigation.
We use fixtures for all of this.
None of these tests really help with bugs. What they do help with is:
- Making sure the ui stays really decoupled from the business logic. This helps a lot with getting the data unit tested which does help a lot with bugs.
- Making sure that analytics and accessibility are not forgotten about. This helps a ton when refactoring.
- Making the intent of the code really clear during review.
It takes a bit of practice and being ruthless about removing/fixing stuff that’s not helping. I have found it makes it much easier for new developers to work, review code and understand how the code is organized. YMMV.
Buddy, if I knew the answer to the question "something people want to buy" I would be rich already
Indeed. As with almost everything else terrible about the world today, the root of the problem is targeted-advertising-based business models.
Aren't there enough tools already for OpenAPI to do this?
But it's a bit challenging to conclusively measure someone's level of "smartness", especially with the usual time constraints of most hiring processes. More importantly, it also depends on what "smart" means to you, the company, etc.