185 karma · joined December 15, 2018
Most of us do not remember the exact syntax for everything despite having coded in that language/framework for years.
[0]: https://sachinjain.substack.com/p/ai-coding-assistant-gemini...
Did your daughter face this problem?
Remote work has many challenges. We're a startup (16 employees) so the challenges differ from the challenges faced by big tech companies.
I think there’s no right or wrong answer here. Either option has pros and cons. With In-person office work, it is hard to go into a focussed more, there are many distractions, commute takes away a lot of time & energy, etc.
While remote working requires a lot of self-discipline, it is very easy to get dragged into many work chores, hard to communicate with fellow teammates, and some folks also do moonlighting which is against many company policies.
We follow certain practices to make our remote setup work and it has worked beautifully so far So I think remote work is here to stay and many startups can adopt remote work to be more efficient, and move fast.
Although Requestly is a freemium product, the free plan offers unlimited HTTP header modifications. You can get Requestly here[2]
[0]: https://requestly.io/blog/modify-headers-in-https-requests-a...
[1]: https://github.com/requestly/requestly/
[2]: https://chrome.google.com/webstore/detail/requestly-redirect...
Your bet is to use a browser extension to override the response of that specific API and sort of change the response.
PS - Why do you think this is an overkill solution?
At Requestly, We're trying to build an open-source platform to make frontend devs more productive. Having been a frontend dev myself, I often found inefficiencies like being blocked on backend devs for development & testing. Another problem that I faced very regularly was testing my JS changes directly on production sites.
We're trying to solve this with Requestly being an on-device proxy (Chrome extension as well as standalone app) that helps you capture network requests and reroute and mock responses easily.
Traditionally, people used Charles Proxy or Fiddler for this but many companies have moved to Requestly now for easy use & being present in browser makes it fast to use and without VPN Issues.
Requestly is an open-source [1] Chrome & Firefox extension [2] that I started to help me in faster web development by capturing & modifying network requests directly in the browser without using any external tools. It eventually replaced Charles & Fiddler for many companies but now we are building a desktop version[3] too.
On a side note, Side Projects are a long-term game but the good part is you can do multiple along with your job and pick the one getting more traction. For example - I did many other side projects but continued with Requestly for 2 reasons - I was using it myself almost everyday and It was gaining organic traction.
Good luck in finding the project of your calling.
[1]: https://github.com/requestly/requestly
[2]: https://chrome.google.com/webstore/detail/requestly-redirect...
Although Chrome DevTools lack the capability of modifying HTTP requests & responses - Rerouting URLs, Modifying Headers, Modifying API responses on the fly for quick prototyping & testing use cases.
Requestly an Open-Source browser extension - https://github.com/requestly/requestly fills this void. It leverages chrome webRequest API (MV2) [0] & chrome declarativeNetRequest API (MV3) [1] to provide support for most of the modifications. To override API request payload & response body, Requestly overrides native XHR & fetch objects' prototype, and registers its own interceptor.
Requestly desktop app [2] runs a local server (aka proxy) on localhost:8171 and provides options to connect installed browsers & mobile devices to the local proxy. The proxy module is a simple node-based MITM proxy available here [3]. A separate rule processor module applies the modifications defined by the user.
Listed down a few problems that HTTP modifications can solve in this article [4]
[0]: https://developer.chrome.com/docs/extensions/reference/webRe...
[1]: https://developer.chrome.com/docs/extensions/reference/decla...
[2]: https://requestly.io/desktop
[3]: https://github.com/requestly/requestly-proxy
[4]: https://sachinjain.hashnode.dev/the-missing-piece-in-chrome-...
This looks promising! We were also considering to build tunnelling support in our desktop app. Definitely going to explore your DIY tool, thanks for sharing.
Out of curiosity do you need ability to support sessions locally for privacy reasons?
We are primarily solving within team collaboration for faster debugging. For example - When QA/customer report share issues with developers, instead of sharing the screenshot/har files they can share sessions and developers can use the session recording to get complete picture of the issue and avoid follow up questions.
Another one was similar when redirect chain got broken because of an intermediate redirect (https -> https -> http -> https)
I guess Chrome & Firefox automatically upgrades the protocol now but Safari doesn't and it broke the chain and it was also not showing the broken redirected chain in the Safari developer tool.
Like you said you usually test with the latest version of Chrome/Firefox you are partly agreeing to the statement I made.
I am trying to find someone who's strongly in favour of testing their apps across browsers and multiple versions.
One line of thought could be if we have already invested in automation testing then why not run in 80 browsers too when we can. Its just additional hardware cost or cost of platforms like BrowserStack/Lambdatest.