well, ish. See, here’s my issue with that approach. Are you simply trying to get the certifications, or are you thinking longer-term?
I see this often in the JS track, and it gets annoying. Yay, I’ve blown through all the challenges, got six certifications in as many days!! Yay! Sure, and you’ve built a prototype, and you’ve wired it up to answer the tests, and it passed. Great. And it isn’t necessarily PRETTY, but it passed.
But the problem is, if you are doing this with the end-game of becoming a designer/developer/programmer, you need to think about this longer-term. That particular page, as you had it – would YOU hire a developer with something like that in their portfolio? I’ve seen some REALLY ugly spaghetti code, things nested partially, unclosed block tags, scripts spilling over… Having been on that side of the table, I’ll tell you: I won’t waste my time.
If you are going for all the certs because you hate your day job and want to be a developer by the weekend, I wish you luck. You’ve got a LONG uphill battle. If you are trying to build a solid foundation as a developer and a firm reputation for quality, slow down. Take the time to break things down to small steps, simplify as much as possible, and write code of which you can be proud.
It’s the difference between Ikea furniture and a custom-built cabinet – do you want to be another Ikea man, or do you want to be known as a fine crafter in your own right?