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.

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.

Snap is what finally forced me to explore the vast selection of distros. Mint Linux is working well for me. I do miss Plasma Desktop though.

I’m at the level called “never bothered to try”.

It could have been the other way around if global positioning systems were either not developed or used only by the military. In that case, detecting scenery of a park could be easier than trying to figure out the position on the map.

Or it could just be that maps data are not shared. You’ll need to hire boats and hire people to go and draw the map.

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.

Making education so expensive that the only way for some to pursue education is to die for their country is a crime. If majority of your citizen view being part of army is only for poor people, your country does not deserve to be protected because obviously not enough people willing to fight for it. Turning your citizens into slaves and sending them into the meat grinder makes you a monster.

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.

Others have given excellent advices. I’ll approach it from management point of view:

• If there’s management oversight, such as tech lead/engineering manager, talk to them. Don’t make any accusation. Approach it from the direction of you feeling uncomfortable with how the team is working. They will know how to solve the issue. However, any tech lead/engineering manager should have already dectected the problem and at a minimum acknowledge the issue.

• If there’s no tech management oversight, I’d suggest you approach the senior engineer directly. I’d want to emphasize here that it has to be tech management. Non tech management won’t understand the problem and they won’t be able to solve the problem. Sometimes the senior engineer maybe under pressure to deliver and there’s nobody to split the tasks to other team members. I did this a few times in my career before I developed my skill to lead a team.

• If it’s neither because the senior is under pressure to deliver, nor there’s management oversight, your next best bet is to seek consultantion with another senior, either in your team or another team. They maybe able help to talk to the senior.

• Your last resort would be non tech management, or saying it another way: express that you’re not happy with your job. This won’t be much help unless others in your team doing so as well.

If all these fail, consider finding another offer. There’s no oversight, there’s no willing to inprove from the senior and there’s no chance to improve the situation from other seniors, you won’t learn much there.

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.

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

Please please please, God, Allah, Buddha, any god or non god out there, please don’t let any engineer bringing up branchless programming for a AWS lambda function in our one-function-per-micro-service f*ckitechture.

I’d much prefer merging across instances to avoid one instance going down from bringing with it the community. It would also avoid the problem of people posting the same thing in multiple instances as well.