martijndwars

Picking stocks based on "everyone uses..." is a great example of a bubble. What about all the companies that are not consumer facing?

To be honest, I agree with the parent that the question is wrong. No company wants employees that are bad at interviewing. No company wants employees that are bad at anything, in fact.

Maybe it helps to contact the company that rejected you and ask them why they rejected you. This would allow you to narrow down your weaknesses and improve these skills. I've never tried this myself, so I'm not sure how common such a request is, but it seems like a sensible thing to do.

Whether parsing XML is easy or hard, how often do you actually write an XML parser? If I'm digesting a JSON/XML document, I resort to a parser library for the language that I'm using at that point, so the complexity of writing such a parser is pretty much non-existent. Definitely not a compelling reason to switch to JSON.

I have no clue about the security implications. What can go wrong if I use ngrok for my development environment that receives development webooks? Please enlighten me.

Abstracted further and further, up to the point where someone without programming experience can tell a computer to do the thing it should do, making "coding" (or at least how we know it now) redundant. Have you thought about it this way?

To answer the "how do I work around this during development": non-HTTPS is permitted on localhost (this is at least the case in Chrome). The spec also hints at this (https://w3c.github.io/push-api/#security-and-privacy-conside...). But, as has already been mentioned, this is about desktop notifications and not web push.