As Alan mentioned, I tend to also rely on the official developer site.
I find sometimes though as with anything just relying on reading documentation to learn can be very dry.
I mentioned in an earlier response above a gentleman called Umar Hansa (Dev Tips - Developer Tips by Umar Hansa) .I like to follow him as he messages out often about cool new tools being released within Chrome DevTools. I find when I see some of the cool new tools which are getting released within Chrome I start to gain an understanding of how they could be of use to my day to day activities, that then gives me a starting point to know what to dig deeper for within the official documentation.
So many extensions I havenāt used So much more to learn and experiment with The only one Iāve tried there was BugMagnet, I also found the source for that useful when I was writing my own Chrome extensions.
Iām looking forward to the LTG workshop so that Viv can show me how to use the overrides properly - Iāve never managed to get that working and simulate it with proxy tools.
I also need to try the Coverage tool. Iāve never noticed that or used it But I need it.
I know right, I use just a handful currently but there are so many great add-ons and extensions out there. Iām currently really liking the āPage Monitorā extension you showed me.
Like you I also used the āBug Magnetā extension to get an idea how to get started when I tried to dive in to extension creation a year or so back - itās a fantastic extension.
I can see now that āwatchingā this page would have removed the need for the Page Monitor - sometimes knowing tools and code means I miss obvious functionality at first glanceā¦ my excuse is that I wasnāt logged in to the forum when I was browsing the questions.
And, if possible, any unit tests used for JavaScript, if they are using an HTML framework to trigger the tests. If they can be run cross browser then that can help mitigate JavaScript issues.
One thing I try to . do, and I havenāt done this for javascript though. is run the code through a validator - e.g. Total Validator Pro will validate the HTML and CSS - and Charles proxy can do this too by sending the files to the W3C validators.
In theory, if there was a good linter, we could pass the JavaScript through that.
Anything that doesnāt validate, I view as a risk.
JavaScript is harder though because it is dynamic and the different engines change.
A lot of people rely on the āframeworkā being compatible cross browser e.g. React, or Angular, and may not test cross browser as much because they think it has been mitigated.
Itās been a pleasure, thanks for taking part. Without people like yourself getting involved and asking great questions it wouldnāt have been so much fun.
So much more to learn and experiment with 
- looking forward to the workshop next month. I hope some of you can join us.
, itās been good fun.