I will keep this chapter short. Whilst looking at many Blogs, I have noticed that nearly everyone but the most successful Blogs are either a) too short or b) too long. I feel that too shorter an entry all it really shows is that you are linking to something or don’t have too much to say. The longer Blog posts are mostly to long winded and I get bored halfway through. There is only so much I can read about a cats eating habits.
Therefore I hope to have a mixture of both, the short entries will have a bit of a critique in and the longer ones such as my "Success and failures" will be more articley, but keep on subject and hopefully be useful and interesting.For instance, I am posting this chapter as a series of more manageable set of entries.
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.
I love to learn about what you are building, and how I can help with Chrome or Web development in general, so if you want to chat with me directly, please feel free to book a consultation.
I'm trialing a newsletter, you can subscribe below (thank you!)
