Because this isn't just converting HTML to markdown. I'd recommend taking another look at the website and particularly read the recipe example as it demonstrates the goal of the project pretty well.
I'm glad you shared your experience because I've dealt with this for decades. It's usually a small snippet, 15 seconds or less, of a song that just loops over and over for me.
What I do to combat this, and other "brain noise", is also to listen to music but I use headphones with high volume. I also listen to the same playlist repeatedly so it's not distracting and instead quiets that loud part of my brain to allow me to focus.
I agree that not everyone wants to be. I think OPs point though is the market will make “not being a prompt engineer” a niche like being a COBOL programmer in 2025.
I’m not sure I entirely agree but I do think the paradigm is shifting enough that I feel bad for my coworkers who intentionally don’t use AI. I can see a new skill developing in myself that augments my ability to perform and they are still taking ages doing the same old thing. Frankly, now is the sweet spot because the expectation hasn’t raised enough to meet the output so you can either squeeze time to tackle that tech debt or find time to kick up your feet until the industry catches up.
If you think of FE web development as just HTML, CSS, JS and the framework de jour then I could see that. However, the most skilled FE engineers I know aren’t just doing that. It involves handling CI/CD, performance profiling/enhancements, CDNs, debugging node environments, asset management, caching strategies and the list goes on. I’m not necessarily arguing that it should be included in CS degrees but all of that is surely not a designers job.
I’m no climate scientist but I would think it’s similar to toxicity/poisoning. You can die from water intoxication but certainly you need it to live as well. So no, I don’t think it’s subjective. It seems to me that if something is capable of causing harm in a certain amount, it’s poisonous/pollution/toxic.