agoldis

Thanks for sharing your concerns, Jessica, we tried to be fully transparent and share our findings with the interested audience. I have added a disclaimer that explicitly mentions the owners of the packages to avoid confusion.

- The article clearly states what entities are affected - Currents, Sorry Cypress and Deploy Sentinel; it doesn't claim those are random package authors.

- Not all the listed packages are written by the dude or written and _THEN_ forked, we provided a detailed breakdown of each package origin. For example, @deploysentinel/cypress-debugger is a completely standalone, innovative software released more than a year before Cypress Test Replay and cypress-debugger

- The article lists all the blocked packages we were able to discover. We published the full list to be totally transparent. Obviously, we create and work on cypress-related packages - e.g. a vscode extension for cypress. There was also a rename from Cypress Dashboard to Cypress Cloud. NPM lists ~1.6K packages with "cypress-" prefix. Another example: we ran a survey on a community Slack channel with ~500 members to pick a name for cypress-debugger - the options were: cypress-debugger, cypress-debug, cypress-tracer; cypress-debugger won.

An interesting experiment would be to rename those packages. Do you believe they will be unblocked?

Very nice, congrats on the launch!

A free plugin to record everything that’s happening during Cypress test runs - browser logs, network events, DOM changes and replaying in a web player. It’s like Playwright Traces but for Cypress - convenient for debugging failed CI runs.

tl;dr

To build a $10k/mo software startup:

- Revenue: get 150 customers paying at least $66/mo RECURRING - Market: choose a BIG market, build a product that people need and is naturally recurring - Customer acquisition: ads > content. It's more reliable

It's much more affordable than cypress dashboard

How would Google engineers with all the crazy interviews and RSUs explain 500 error and country switch hack

Arguing with my boss

Go to GitHub and start contributing to open source projects that use the same stack.

It's your choice to interview for 4-5 positions, moreover, you will have those interviews whatsoever, so it can't be an argument :) Most chances you are applying for a high paying job and do that once in 2-3 years on average, aren't you ready to invest a week of intense effort for that? If not, you could choose to apply to a FAANG and spend 2-3 weeks studying craking the code interview-style books. How much time do you think is reasonable to invest for candidate and a company to make a decision? As a company I don't see a point in giving home excercise after an offer, but why are you asking? I will spend 12 hoirs if I consider a company better than one that offerer.