developerjackG’day!
What a wonderfully rainbow week its been! Wednesday was a long and fantastic day with the YES 🏳️🌈 result announcement, Thursday was packed full of startups at TechCrunch Battlefield, and Friday we wrapped up our internal hackathon (I was one of the judges!).
This weekend has been quiet as I re-spoon between busy weeks which means some light reading about JavaScript Performance, developer experience and API deprecation! Enjoy reading!
The Cost Of JavaScript
Addy’s own conclusion sums this article up quite well: ‘Transmission size is critical for low end networks. Parse time is important for CPU bound devices. Keeping these low matters.’ My favourite contrast Addy paints is the resource consumption between 170kb of JavaScript and a 170kb JPEG and the impact that has on page performance.
Read the post.The 7 Sins of Developer Experience
Cristiano has some excellent things to say about developer experience and this is a write up of some of them! One of my favourite things Cristiano highlights is field naming and giving the user the right balance of information to achieve their goals. Useful UX as much as its DX!
Read the post.Google’s Extremely Shortsighted and Bizarre New Restrictions on Accessibility Services
When you design an API for a particular use case, it doesn’t prevent people from building weird, wonderful and fantastically useful things with it that were completely unintended. It seems Google is working on the issues with LastPass (et. al) after this post – but its an important reminder to consider deprecation and usage for all things that we build and publish.
Read the post.This week you’ll find me in Wellington, New Zealand for #bsideswlg conference! If you’re there, say hi!
See you next week!
@developerjack
