493 karma · joined January 10, 2021
A very popular extension, Hoverzoom, does the same things I need to do so its author will need the same solution, or severely limit its functionality. ...and I doubt the author will be able to support a proxy service with the volume it would get.
• Block all traffic from AWS, Azure, etc. yeah, you'll loose some traffic from some VPNs and maybe you care and if so, this suggestion isn't for you.
• Verify the traffic saying it's GoogleBot, BingBot or DuckBot are really from those sources. All three provide a list of valid IPs accessible via a REST endpoint to match incoming IPs against. Block Yandex etc. There is likely no good for you coming from a Russian or Chinese search engine indexing you.
• Make sure the browser versions in the User Agent aren't like 5 years old. That's a great indicator of a bot.
Also take note of the menu options you need to select so when you call back you can bypass all the blah, blah, blah in most cases.
I just don't understand how whoever approves this thinks it's a good idea. It seems to be this way across almost all Mazda models. There used to be a way to turn that off but Mazda removed that. So there are indeed people actively making this moronic behavior a thing.
class Foo { #ImPrivate = true; #meToo() { if(this.#ImPrivate) cantTouchThis(); } }
new Foo().#meToo() === BOOM
Also with using closures for "classes" takes up a whole lot more memory because new instances off all the closures are created for each instance of the class.
...also remember 45 minute builds when a header file changed.
JetBrains IDEs have this problem all the time and its not consistent across all platforms. i.e. some people see it, some don't.
At this point I wish I could switch off JetBrains but I'm so familiar with it and using VS Code my productivity just screeches to a halt.
A debugger is as much "help" to an engineer as a hammer is to a carpenter. In my experience, engineers who don't use one are a detriment to the entire engineering organization wasting time and money.
Anyway, yeah I dodged a bullet on that but it's such a pain in the ass that I went though a two month interview process only to be vetoed at the end like that. During that time I spent about two weeks to learn an esoteric API that I'll never use again. Oh and it would have been highly unlikely that I would have even used that API in the job. It was just a requirement that I learned it for this particular interview. ...and no I'm not going to commit it to memory just so I can pass a coding interview and if that was the expectation then this whole situation is even more ridiculous.
I recently went through a series of interviews with a company that were dragged out over two months. Each went very well. My last interview was with a "Senior Engineer" who graduated in 2020 and had a little over a year of experience at Google before joining the company in question.
He vetoed me because I used a debugger in a pair programming interview. Not because I didn't complete the task well.
So yeah, it's a bitch out there.
Sci-Fi or Fact or somewhere in the middle?