How do you sell what you did as “it just worked”? Rightaway? You lied to them. You have your coworkers on an unmanaged machine with a foreign OS on the guest WiFi with custom networking. Don’t oversell a workaround as a solution.
Simplifying the problem to “Windows” seems unfair, given how many problems you found. All of them still require a long-term solution for regular operation.
You don’t realize a 500km route you take once is shit. It’s when the software sends you on a shit route across town every single day when you measure quality.
Especially because TypeScript compiles down to JavaScript JS
SmegmaScript is just too close
Fake Amazon reviews is a service you can buy to boost your product. Using genAI is an obvious move for these providers. Makes it harder for Amazon to find the fakes, because they can generate more content variety.
When you run a botnet for such a service, you can’t only put 5 star reviews on your client’s products. You want a variety of usage pattern modifiers to stay below the radar. Putting reviews on semi-random products is one technique.
I’m just waiting for someone to lecture me how the speed record in wheelchair sprint beats feet’s ass…
They do. Reality is not going to change though. You can enable a handicapped developer to code with LLMs, but you can’t win a foot race by using a wheelchair.
In boomer times, phone calls were expensive and were transferred over landlines. It had an impact on the quality of the conversation.
Today people call you with 1% battery while at the register of the supermarket and instantly launch into a monologue about how they know it’s not a good time to call, and they might even cut off any moment, and they know you’re usually busy at 10am on a work day, but they really need to know if they can call you “later” to discuss something really important. And before you can tell them anything, they cut off. At least it’s over!
10 minutes later they call you from their car and it takes them a couple of minutes to get the audio working so they can repeat everything they said earlier. It’s what you have to do if a call was cut off! Then they drive into a tunnel.
Dealing with this shit is a dark art fr
Following along with the style of your own post: YAML doesn’t suck, because I feel so.
Thanks for asking.
I get that, I really do, and I honestly believe you have exactly the right idea.
But on the other hand, you have to realize that not all of the money purely goes to enabling knowledge sharing with Wikimedia. This is not an election, it’s a company, non-profit or for-profit doesn’t really matter. There are still people paying off business expenses from your donations.
I fully understand the necessity of this, but you might just feel better if your $5 literally bought someone a meal or if it paid for a fraction of a business flight to promote Wikimedia.
They increased to 25 to encourage media uploads to train their own models with. They now have collected enough metrics to realize, most valuable content is below 10MB. Now they are optimizing. They won’t lose anything valuable to them and the users who are impacted might even buy Nitro now. Win-win for them
Makes sense. If you’re contributing less than $1000 monthly to anything, you’re not making a difference. If you want dedicated people to be on the receiving end, who also do a great job, every single person will cost thousands each month. Wikimedia is literally spending millions each year.
Honestly, don’t try to hunt for the “best” spot to contribute your exact amount of spare money to, with the hope of having the largest possible impact. It won’t happen. Treat a good friend to some food instead.
If you really feel like you already got some value out of a service in the past, give what you can, without limiting yourself financially in the process. If you feel like you don’t have the $1 to spend for Wikipedia, don’t spend it. Don’t guilt trip yourself into donations ever. Your donation today will not prevent a service from turning into shit tomorrow. Pay for what you got
I’ve been a funding member of the Wikimedia Foundation for over a decade. I have looked at their finances several times before and during financing them.
As with a lot of similar non-profits, a considerable amount of donations does not go into “running the servers”. You have to judge this by yourself, but they don’t embezzle any money and there is a reasonable bottom line. Wikipedia continuously helps tons of people, and the people who run the operation enable that.
You can download a full dump of Wikipedia any day. Compared to other lying companies, they have been true on their promises for some time.
Of all the $1 I could spend in a year, the one I give to Wikipedia is probably the least wrong invested, and that $1 actually already makes a difference
Okay. But where’s the cost analysis for me giving them respect? I doubt it is worth a mere 53% performance increase in the common ranks.
Not sure if I could fully agree with the root cause analysis, but it sounds about right for Europe as a whole. Things are likely still mostly as their were, with additional steps and reduced demand
While that is true and reflected in the article data, it doesn’t contradict what I said. Just in case it was meant to 😄
Yes people still buy Russian energy, some countries more than ever, sometimes through third parties, but total consumption is down.
Because it’s clickbait framing. Total imports from Russia are at their lowest point ever. The USA just dropped below Russia in the rankings.
Depends on the product. It’s just something to think about when signaling errors. There is information for the API client developer, there is information for the client code, and there’s information for the user of the client. Remembering these distinct concerns, and providing distinct solutions, helps. I don’t think there is a single approach that is always correct.
I don’t necessarily disagree, but I have spent considerable time on this subject and can see merit in decoupling your own error signaling from the HTTP layer.
No matter how you design your API, if you’re passing through additional layers, like load balancers and CDNs, you no longer have full control over all responses your clients receive. At this point it may be viable to always signal a successful backend connection with a 200, even if the process resulted in a failure.
Going further, your API may include partial success scenarios, think batch processing, then the result could be a mix of success and failure that doesn’t translate to HTTP status.
You could even argue that there is really no reason to couple your API so tightly with a concept of the transport layer it uses.
Maybe I’m just old, but I thought a distribution is literally just a package delivery basically, just like you speculated. Making software work together nicely is actually already hard enough IMO. I don’t think anything is wrong. Valid question though