That’s click bait for me. There was only one performance tip in here — inlining CSS. Otherwise it’s mostly basic HTML authoring advice, or if there are performance benefits to some of the style suggestions, they’re not discussed.
I wasn’t aware that li tags don’t require being closed though.
The original source code for jQuery. Including annotations from Jon Resig:
I want to just take a moment to note how little has changed in how these functions work, at an API level. There’s a strong chance that you could take circa-2006 jQuery-using code and drop in a modern version and have it still work. Granted much more was added later on, as it increased in scope beyond my simple use cases, but almost all of the API that we see here was left intact. I’m definitely proud of the fact that the API was “good enough” to last over the next decade — and beyond.
It’s kind of amazing that the original version of jQuery wasn’t even 700 lines of code — a good reminder that even really big projects start out small. Via Jeremy Kieth.
Software development has a gender balance problem. Our internal stats suggest the imbalance isn’t quite as severe as the survey results would make it seem, but there’s no doubt everyone who codes needs to be more proactive welcoming women into the field.
From over 25,000 web developer survey respondents, 91% identified as male. I’m interested to see how much this differs from their internal stats because it seems in line with my own personal observations — which is a shame.
Useful for getting your head around semver, or double checking your logic for more complicated version dependencies.
Even though my authoring style doesn’t match Harry’s one-to-one, there’s a lot of overlap and definitely some sound recommendations for front-end folks looking to write more maintainable CSS.
Lot’s of useful information here for anyone concerned about performance — which if you’re not, you should be. The tl;dr sections are great too if you’re pinched for time.
Michael Riethmuller:
It appears that by using calc() and vw we can get responsive typography that scales perfectly between specific pixel values within a specific viewport range. This means you can have perfect smooth scaling between any 2 font sizes over any viewport range. The font will start scaling and stop scaling exactly where you want.
Incredibly useful.
(Via Chris Coyier)
Really cool visual SVG optimizer from Jake Archibald built on the Node.js SVGO module.
Love the design. This kind of approach is definitely the future of info graphics.
A good follow up to Rebecca Murphy’s 2012 recommendations for baseline skills for front-end web developers. It’s always tough to pin down what the essential skills of the field are or should be as it seems like acquiring new knowledge on a daily bases is a job requirement for front-end web developers.
The main point I took away from this is that on top of understanding JavaScript, we should all be using the tools we have available to us (build tools, versioning, dependency management, the shell, etc) and know how to use them well to in order to automate repetitive tasks, eliminate errors, and ultimately be more productive.
Presented in Tucson, AZ on November, 7 2012
Presented at Spoke6 in Tucson, AZ on Oct, 26 2011
Presented at Spoke6 in Tucson, AZ on September, 07 2011
Presented at Spoke6 in Tucson, AZ on June, 22 2010
Presented at Spoke6 in Tucson, AZ on June, 10 2010
