zegerjan

The EU Banning inefficient vacuum cleaners had a similar effect. Though I'm not aware who is responsible for the policy.

I'd not be surprised if that would lead to job with REMOTE (US EXCEPT WA) soon.

Whats wrong with the Slack version? It's on-par UX for me for recording, and wins just because it's already in Slack?

Thanks for calling this out, I've updated this in the article.

What’s not quite clear from the wiki page: was Yahoo too early? With the related tools on the page being so successful it seems that way.

Azure to GCP was right after GV became an investor. Again, credits was the reason to change over. Not the poor Azure performance.

Interesting take, especially if you factor in action on climate change. The US is unable to get anything done, while the EU has a track record of getting results.

As retail investor there's great downsides to market makers too. The prime example; the true price of the underlying is obscure when executing an order. Where the whole point of the market is to create price efficiency. When anyone creates a limit order in the middle of the spread it's often filled instantly, but not market moving. Other investors now do not have the same information as the market makers have who filled the order. So either they should publicly log each trade so all brokers can show what the true last price was and change in positions with that, or PFOF creates information dissymmetry. Markets should be transparent, and if you make money through obscurity that's against what the market is for.

Another problem is that market makers tend not to provide liquidity when it's most needed; when markets are most volatile and unpredictable. The GME spreads for example were very wide. When the market is very volatile they tend to increase the spreads until the market is predictable (as far as they can be) again. Effectively they're like bad insurance companies: When you need them they're nowhere to be found, when you don't they'll gladly take your money.

It's for everyone involved, except ones that make money of PFOF plus the market makers, probably better to have transparent inefficiency in pricing, then have defuse pricing which in some cases might be in your favour.

The issue tracker I think is a better place for such a feature request.

Last time I worked on the attachment code, there wasn't a persistent database relationship for uploads and notes. Which would make this feature hard to implement, it would be a great feature though!

As a hiring manager at GitLab, I'll tell you that these questions are surprisingly effective in filtering candidates. I'm sorry it feels painful to you, however, it's for good reason.

I'm saying the blob was in a new repository, you had no control over. You couldn't have removed it, you could only make sure it doesn't get referenced in _your_ repository. Which is what you did.

The reason you couldn't delete the blob, is because someone forked your repository and GitHub uses git alternates for deduplication of fork networks.

I think you could ask GitHub if you can recreate your repository without the offending blob, and you should be good again.

Adyen not even getting mentioned, very surprising as it handles most payments for Netflix and Spotify.