Sometimes it's hard to know how often and in what situations it's best to use any particular technology. How many integration tests do I need? When can I not write them, when can I do without them? When is it better to use vanilla JS and CSS, and when to get into all that post- and preprocessor stuff?
In these cases, it helps me to bring the situation to the point of overuse. I don't know how many integration tests I need? For the next two weeks, I write only integration tests. In all cases, no matter what the internet says. Period. I don't know when enough vanilla JS and CSS will suffice? I'm building a page only with bare JS and CSS.
This approach gives quick feedback in the form of pain in places where the technology definitely doesn't fit. Oops, integration tests slow down and prevent quick refactoring of the module - I'd rather have unit tests here. Oops, with vanilla JS it's painful to keep track of form state - I'd rather have something reactive and product-ready.
Top comments (0)