Pivoted with research being prominent new addition.

would love technical details around this feat. ex: how you even crawl to begin with, storage, etc

Nice! I too have written an article on UT recently - https://medium.com/@lodestar97/your-unit-tests-suck-58d0f6fc...

>Actually I'd suggest people don't just accept all feedback

If you read the whole para :)

What I suggest: listen to everyone and everything, but internally filter what’s actionable versus what should be addressed. More importantly, after receiving feedback, thank the provider regardless of whether they were right or wrong. Then share recent instances where you made corrections based on their suggestions.

Which, to me, heavily implies that you should be taking all feedback as being valid with your best interests in mind. My point is that feedback isn't always valid and sometimes you need to reject it, as accepting it can also mean that you're also accepting something that you don't want (usually blame for someone else's mistake).

So for example, you get feedback from someone that your API to delete users was badly designed because a bug in their untested script called it on 100 high profile users accounts and it deleted them. You don't accept that feedback, you push back and ask why their script called an API to delete users for 100 users that they didn't want to delete - if you just accept the feedback without pushing back then they can legitimately say to their manager that you've admitted that the fault was with your API and not with their development practices.

I am always fascinated by companies experiments. It would be great to understand the rational and results of such experiments

Make sure you don't an extension enabled that might be messing up with CORS headers.

Beginner’s Guide to the Gym

Pardon my ignorance but why does it matter that you're using RPC/graphQL or REST based service, isn't the underlying protocol still HTTP? So this spec would still be applicable, right?

AFAIK, in Google's case the end application doesn't really see the "GRPC HTTP headers" but instead they convert an incoming HTTP request to one of their frontends and route it to multiple backends (sending effectively the HTTP body serialized via GRPC), and then the frontends will simply re-create the response by unifying them.

Not a Googler, this is what I understood from reading similar things over multiple posts. Feel free to correct me.

The underlying protocol is not necessarily HTTP.

I think it is necessarily HTTP/2, but would be happy to learn I'm mistaken - it's not something I'm overly confident about.

https://developers.googleblog.com/2015/02/introducing-grpc-n...

gRPC uses HTTP/2.0 yes, so headers are a concept, but imagine taking it one step further, for instance using WebSockets. There is no concept of headers within an individual WebSocket message, so it would need to be encapsulated in an application-specific way anyway.