virtualcoffee.io VS lighthouse

I've been learning how to code for the past five months and let me tell you, it really is a whirlwind of emotions! After an amazing mentorship that ended too soon, I realized something: I thrive when I learn with others. That's when I found Virtual Coffee, a tech community that uplifts and celebrates wins of all kinds! Just one virtual coffee in, Chris Nowicki, a generous full stack developer in the community, already dropped a goldmine with us--learning and building in public!

I joined an online developer community called Virtual Coffee last year and saw Klesta’s post about Web Dev Path on their Slack channel. I remember I read her interview to know better about it. I was familiar with building something on my own but I didn’t have much experience to develop within a team. Web Dev Path sounded like a good place to improve skills to work in a team.

Next month at Virtual Coffee, we're doing a monthly challenge for public speaking. What are your favorite tips or resources?

VC Link

Since last September, I have had the opportunity to be an open source project maintainer. I help maintain some project repositories at Virtual Coffee, OpenSauced, and SheSharp communities. And now, I can see the view from a different perspective.

I'm part of some tech communities and love documentation. Together with the core team of the Virtual Coffee Community, I actively discuss ideas and contribute to creating and shaping the community documentation. From there, I was trusted to be the Documentation Team Lead.

Virtual Coffee

Update monthly challenge page to Hacktoberfest — Virtual Coffee

Virtual Coffee: In this project, you add your name and a list of open source projects you recommend for Hacktoberfest. They provide specific steps to look out for in open source projects. It’s a great way to learn the traits of a healthy open source project. Since I’ve been contributing to open-source projects a bit before Preptember, I decided to list projects that have been helpful in my journey. (note: you have to join their group in order to contribute. Here’s a link: https://virtualcoffee.io/).

I will guide and answer open-source questions for anyone who needs one. And I'm volunteering in some tech communities — Virtual Coffee, OpenSauced and SheSharp — to be a mentor, a Hacktoberfest support, and a maintainer during the event.

Google Core Vitals now represent the most important metrics to focus on when it comes to technical SEO. Google Core Vitals are a set of standardized metrics that Google uses to evaluate the user experience offered by a web page and assign it a technical SEO grade. Several tools exist to measure and report technical SEO performance, but the most reliable is Google Lighthouse.

- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,

There has been discussion about adding a visual indicator to make the mode more obvious, but it has not made it into Chrome devtools!

I haven't tried it, but you might be able to control throttling by using lighthouse to get performance data: https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md

When we implemented the MVP of the fintech app, we had a quite complicated form. At that time, I was still young and inexperienced. And eventually, we realized that our project was slowing down. We had to spend additional hours figuring out the reason. We had many unnecessary re-renders because we ignored basic rules related to props in React. I wanted to do everything possible to avoid such situations in the future. So, I added to the project linters like this and an additional starting configuration to package.json to run why-did-you-render. In short, this plugin issues a warning if something is re-rendered unnecessarily and suggests how to avoid it. Also, we included running Lighthouse in headless mode. Some people say that premature optimizations are bad, but for me, it's a principle: do it right from the start.

You can run a Lighthouse audit in two ways: either on the command line or in a browser. If you want to run audits on the command line, you will first need to install the Lighthouse command:

i wanted to run the lighthouse(lh) docker container on multiple EC2 instances in different regions. I'm thinking of triggering the EC2 instance with the lambda function once the lh container has audited the URL the results will be sent "SUB rest API" which will further update the UI

There's a link to what they mean by mobile network there (https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md) and it says:

Here's the non-psuedo code equivalent that can leverage CompressionStream rather than using a browserified-gzip-library: https://github.com/GoogleChrome/lighthouse/blob/437eb4d757c5...

We use it in Lighthouse for the exact same purpose, a URL #hash full of state. We found that modern browsers support 10mb of data in the hash. https://github.com/GoogleChrome/lighthouse/pull/12509#discus...

Lighthouse: This is an open-source tool developed by Google that allows you to audit the performance of your website. You can use Lighthouse to get a detailed report on your website's Core Web Vitals, as well as other performance metrics. You can run Lighthouse in Chrome DevTools or as a command-line tool.