Post pobrano z: Front-End Challenges
My favorite way to level up as a front-end developer is to do the work. Literally just build websites. If you can do it for money, great, you should. If the websites you make can help yourself or anyone else you care about, then that’s also great. In lieu of that, you can also make things simply for the sake of making them, and you’ll still level up. It’s certainly better than just reading about things!
Here’s some resources that encourage you to level up by building things for the sake of leveling up, if you’re up to it.
It looks like this recently launched, and it’s what inspired this post. This idea of giving people front-end work to do is enough to build a business around! Some of them are free, and some of them are not.
Other businesses have centered themselves around this too. HackerRank is all about getting jobs and hiring, so they’ve got a very strong agenda, but part of the way they do that is putting you through these skill tests (solving challenges) which are meant to asses you, but you can certainly learn from them too.
Coderbyte has paid plans too, and they’re designed to leveling up your job interviewing skills with challenges.
Classic situation: sometimes the site is the product and you’re the customer, and sometimes hiring companies are the customer and you’re the product.
Here’s the classic move: find something you like on Dribbble, rebuild it. The @keyframers often do it. Tim Evko’s Practice site used to pick a shot for you (along with random GitHub issues and random coding challenges), but the Dribbble part appears broken at the moment. The other stuff still works!
Andy Bell did a Front-End Challenges Club for a while, and while I think it’s on break, you can view the archives.
CodePen Challenges run every week are are a prompt (along with ideas and resources) for building whatever you like. Low key.
Frontloops charges $19 for 30 challenges, which includes information, advice, assets, and a solution.
I just happened to notice that the first challenge is a drop down navigation menu, and it doesn’t handle things like
aria-expanded. I’m not entirely sure how big of a problem that is and I don’t mean to pick on Ace Front End — it’s just a reminder that there could be problems with any of these challenges. But that doesn’t mean you can’t learn something from them.
Codier has public challenges that include solutions posted by other users.
Cassidy’s weekly newsletter includes a challenge in every issue.
Rina Diane Caballar quoting Tim Carry in Extending the Limits of CSS:
Carry’s advice is to start with a real-world object—the interface of a gaming console or a calculator, for example—and to try to recreate it using only CSS. “A great way to push the boundaries with a language is to make something that the language wasn’t meant to be doing in the first place,” he says.