i don't understand why people would ever want to read this kind of article. The information is ok, but it's a regurgitation of many sources, some of it incorrect, covered in ai slop prose.
Please share the cool thing you're doing in a blog post, but don't have AI write it for you; it's hard to read and doesn't respect the reader
I mean...if you read the github readme it literally describes what it does in the next line: "Uses CSS selectors to extract bits content from HTML files".
I build an RC (with the goal of making it autonomous) car. I got as far as giving it edge detection: https://www.youtube.com/watch?v=r-o8Uzi5o1k but haven't continued the project. It's a great platform for exploring controlling hardware and prototyping ideas!
I think there's a lot of value in balancing this approach with smaller sized tests, especially around complex code.
The problem that the article doesn't address is if your test fails finding the failure point isn't as straightforward as it is with smaller units.
However the points made here and in the discussions linked are valid and I think this is the right approach to testing. But I think that there's still lots of value in writing and maintaining tests around smaller units of code. Balancing the two approaches brings us solid test coverage along with easy to debug test failures.
I like the approach to this article, and the demos it provided. I think there's a place for both, but I don't think that the "more" in the basement navigation is anywhere near as good as an actual menu. The problem is still that many people don't know that the hamburger icon is a menu icon, but with it's growing use I think that will change quickly.
Unrelated, but did anyone else think the title was related to food? That's the first thing that popped into my mind when I read "hamburger menu"
Please share the cool thing you're doing in a blog post, but don't have AI write it for you; it's hard to read and doesn't respect the reader