30 Days of JavaScript: Building a Portfolio Website, Day 30
You’ve spent 29 days writing JavaScript. This is where the series ends, and it’s the one day that pays the other
Embark on a 30-day learning journey, with daily lessons designed to quickly elevate your web development skills in various technologies.
You’ve spent 29 days writing JavaScript. This is where the series ends, and it’s the one day that pays the other
One unescaped string is all it takes. A comment box, a search field, a URL parameter, someone drops a <script> tag
You have hit this bug even if you never named it. Click a button, the page locks up for half a
Day 27 of the 30-day JavaScript journey. So far most of what we’ve built renders in the browser: the server ships
Load a chat app, type a message, and it shows up on someone else’s screen a fraction of a second later.
You have spent 24 days writing JavaScript that runs first and complains later. A typo in a property name, a number
You build a site, it works great, then someone opens it on a train that dives into a tunnel and the
You need a user’s name and email. The REST endpoint hands you back the whole user object: forty fields, three of
You’ve solved the same problem more than once. A global that everything reaches into and nobody owns. A settings object that
For 20 days you’ve written JavaScript that runs in a browser. Day 21 is where that changes. In our 30 Days
Tab through enough of the web and the cracks show fast. A menu that won’t open from the keyboard. A button
A page that snaps between states feels broken even when it works fine. Toggle a menu open instantly and people flinch.
Day 18. You’ve written a fair bit of JavaScript by now, and some of it has probably bitten you: a function
You’ve spent sixteen days on syntax and logic. Today you point JavaScript at the real world and ask it what the
You’ve probably copied the same dropdown, the same modal, the same star-rating widget into three projects, then watched each copy drift
You wrote the function. It works on your machine. Three weeks later someone refactors it, ships, and it quietly breaks in
By now you’ve written a fair bit of JavaScript in this 30 Days of JavaScript series, and your files are probably
Nobody writes everything from scratch. The moment you need to manipulate the DOM, wrangle a date, or build a screen that
You call an API, and back comes a wall of text. Before your code can do anything with it, that text
You’ve written code that works. Then you ship it, someone opens it on a mid-range phone, and it stutters. Closing that