granos

Crazy issues like that definitely do happen. But, this speaker output power issue being due to a file transfer error doesn't feel right. Do the perform any kind of integrity checking on the fw before installing it? Even an md5sum on the package seems like it would almost certainly have caught this. Either this wasn't caused by a file transfer problem, or their fw update process has some serious design issues.

If the SDK in question is just a thin wrapper on REST then sure, it isn't providing very much value. But most of the SDKs I've used implement higher level logical operations -- things that require understanding the intent of the API/data model and how things are supposed to fit together. By being able to write my code against that higher level abstraction I'm able to save time and offload some of the responsibility for knowing how the pieces all fit together to the people who know that best. Ultimately my goal is not to make REST requests, it's to provide value to my customers, and the APIs I call are means to that end.

If you haven't done so already, you REALLY should look into setting up an LLC for contract work in the US. Legally separating your business assets from your personal assets is very important. It doesn't cost a ton -- varies by state and whether you involve a lawyer or not. It will make your taxes a bit more complicated, but consider that the cost of insurance against somebody trying to sue you and take your house.

It somehow feels wrong to tell Apple that they can't sell Apps in their own App Store.

It's always cheaper to add one more patch, or bring in the contractor one more time than it is to rebuild the entire system from scratch. In aggregate this stops being true eventually, but I imagine this isn't a part of the system that may people are even aware of until it breaks -- and at that point you need a fix yesterday.

I'm currently living this. About a year ago I inherited a large codebase that has been allowed to accumulate tech debt for the past 5 years. This was all done in the name of adding new features and keeping the business competitive. But it's time to pay down the debt.

I've had MANY frank conversations with both product and engineering leadership about the current state of the world. The VP of engineering is onboard and understands the pain of what we're going through. Product is a bit harder to convince, but just as important -- probably more important. They understand that my team is having to spend 20%+ of our time just bringing the code into this decade, because I set that expectation early and reinforce it often.

I argued AGAINST a from-scratch rewrite because I knew it would never be ok to stop shipping. But I have been able to convince them that slowing down now will let us move faster later.

I may be wrong, but I'm fairly sure that FF licenses Widevine.

Hypothetically, if you could cause earthquakes in a controlled way, it may be possible to perform periodic small stress relief quakes rather than allowing one big one to occur naturally. We can't stop it moving, but maybe we can make it move on our terms.

Imagine a giant cube around the entire earth that touches in 6 places -- one on each cube face. Pick 3 faces and place a detector where each touches the earth -- on the surface. You can rotate the detectors around on the surface so that you get an arm in each axis relative to the center of the earth.

I used to work for a company with a very large user base. On 2 separate occasions we found code with GPL2 notices. One was in a header file and the other was in a monitoring script (we were technically distributing this script because of our corporate structure and who was running the servers).

Management took the issue very seriously -- in both cases the code was pulled and the features rebuilt. Annual trainings were introduced to make sure people were aware of licenses and that they can't just pull in code without looking. The company actually contributes quite a bit to open source.

You're absolutely correct that most companies wouldn't take the risk. I've seen this taken so far as to need Legal approval for including any new libraries. Unfortunately a lot of developers don't understand what they are doing regarding licenses. They don't understand that they are taking a risk on behalf of the company when they include code with a copyleft license.

Every place I've ever worked for has used code in production with licenses requiring attribution, but it's very rare that I've seen it actually done.

I wouldn't say that playing WoW costs your dearly or is detrimental or toxic to people. I will say that all of the people I've known who played games to their own detriment or in a way that was toxic to their lives were playing WoW. It is attractive to people who want to escape from their problems and not solve them. Because of this, it has somehow come to be seen as a cause of that escapism. It definitely becomes part of a vicious circle -- I play too much WoW because I'm stressed -- I'm not more stressed because I play too much WoW -- but that's the fault of the player, not the game.

Revoking all tokens and probably unpublishing anything published since eslint-scope 3.7.2 was released (maybe limit it to things published with a token that was issued after 3.7.2 was published) is the only way to really be sure

Seriously. I've been on a deployment that failed because China blocked access to Github for a little while over some piece of code in some repository. Make sure your dependencies are available.

Linus or the contributor? I can see an argument for either.

I've lived in areas where the pedestrian walk buttons are non-functional and also in areas where they extend the length of the green light in your direction. It's way too much effort to determine if they work or not, so I'll just continue mindlessly mashing them until the light changes anyway :)