If the price I saw when I picked an item is different to what I pay at the counter, I’ll never be back at that place again, even if it means I’m paying less.

My experience with maintaining open source projects (though mine are very much smaller) is that it’s quite similar to a business: you just have to deal with stakeholders and people who think they are stakeholders.

I had all the same experience at work:

• Some unknown person from an unrelated team contacted me because something that my team does not manage broke. I tried to help a few times and I suddenly became their personal IT support team.

• Another time someone not even working at my company demanded that I drop everything and fix their problem, because my name appeared in 3rd parties libraries.

It’s sad that open source authors don’t always receive the recognition that they deserve.

Auth0 has “development keys” for you to test integration with social logins. For production environment, you should still use your own keys.

Thank you for your compliment. I love it. The floppy disk is 1.44 non-freedom MB, not 0.015264 miles of CD drives.

I would suggest:

• 1KB = storage capacity of 1 kg of 1.44 floppy disks.
• 1MB = storage capacity of 0.0106 mile of CD drives.
• 1GB = storage capacity of 1 good computer in the 2000s.
• 1TB = storage capacity of 1 truck of GB (see above)

PS: just to be clear, I meant CD drives, not CD discs.

RoR is too much magic for me. Getting started with any new code base is such a pain that I never want to do again. As a manager, I’ll avoid any job post that mentions Ruby. I have maintained projects written in Delphi, Centura, Java, C#, PHP and none of them even come close to the pain of RoR. Java and C# are notorious for ceremonial interfaces but that’s nothing compared to trying to figure out RoR automagics.

RoR is very… specific. Some love it because it comes with magic. Many hate it for the same reason.

You either knows the magic and love it, or you hate it with a passion. You never really know when (not if) your change will break the system because it’s supposed to name in a very specific way that work by, again, magic.

Any good encryption should make data looks random. Looking for patterns in encrypted data is one of the most basic steps to break an encryption. Therefore, good encryption should make data almost uncompressable, as in it’s so random that compression does not reduce the size.

Encrypt then sign. Verification is often much faster than (or at worst as fast as) decryption. Signature can also be verified without decryption key, making it possible to verify the data along the way.

After many failed attempts at TDD, I realized/settled on test driven design, which is as simple as making sure what you’re writing can be tested. I don’t see writing the test first as a must, only good to have, but testable code is definitely a must.

This approach is so much easier and useful in real situations, which is anything more complicated than foo/bar. Most of the time, just asking an engineer how they plan to test it will make all the difference. I don’t have to enforce my preference on anyone. I’m not restricting the team. I’m not creating a knowledge vacuum where only the seniors know how yo code and the juniors feel like they know nothing.

Just think how you plan to test it, anyone can do that.

Not sure if they’re different now. I tried YouTube Music one year ago and it’s very hard to find new music. On Spotify, I can navigate from one song to a related song and another and so on. On YouTube Music, it keeps taking me back to artists and songs that I have liked before, making it very hard to find new music.

PSA: Since his finger and the reflection touches, he’s likely looking into a one way mirror. There’s someone behind the glass.

There are already some attempts but I don’t think it will work, harmful even. Best case scenario, the AI can understand the code as well as a senior engineer from another company. All they can know without the context is what was changed, which is useless. We need the reason why the commit was made, not what was changed. The info is not there in the first place for the AI to try to extract.

Let’s say YouTube has a video and 2 ads:

1. The video is served from videos.example.tld/video.mp4.
2. The first ads is served from videos.example.tld/ads/ads1.mp4.
3. The second ads is served from ads.company.tld/ads2.mp4.

PiHole will be able to block only (3) because DNS applies at domain level, as in videos.example.tld. DNS requests only send the domain part and re-use the response for all addresses using that domain.

Browser extension, on the other hand, sees a request to .../ads... and block it since it handled each HTTP/S request and know the full URL.

No FactoryFatoryFactory? I’m disappointed. (Typo is intentional)

Plex login system is such a nightmare. There’s a mix of something that is local, some that are online but displayed as local, and some that are completely online. I gave up on Plex when I can’t figure out how to remove an old Plex instance that somehow the clients still connecting to instead of the new server.

Reddit declined to comment

That means what The Verge says is 100% correct. Reddit will speak when there’s corrections to make. :-)

Think of it as GMail and Yahoo! Mail. It’s still emails at the end of the day but the UI looks different and their servers are definitely different.

Lemmy advantage is that it’s both open source and federated. Someone can make a version with accessibility feature (which will likely be integrated into main version) and deploy an instance for blind users. Blind users will then have access to the whole fediverse.

CEOs tends to think they’re special. They do not think they are there because of right time right place.

I work in tech and I have seen how a small change in organization structure, such as a Product Manager leaving, or adjusting how Product, Engineering and Marketing working together, having a huge impact on how the business operates. Yet most CEOs think the company is where they are because of their own decisions. It’s quite the other way around: CEOs suggesting stupid policies and other people cleaning up the shit, like “let’s all go back to office because I’m lonely here”, despite majority of employees work remotely from another fricking country.