Probably because there are services (AKA web services, software listening on a network port, etc.) out there which accept arbitrary Parquet files. This seems like a safe assumption given lots of organizations use micro-services or cloud venders use the same software on the same machine to process requests from different customers. This is a bad bug and if you use the affected code, you should update immediately.
I suspect that an MCP is just a rebranded API. We have also seen these sorts of extensibility mechanisms before. Browser extensions, Object Linking and Embedding, Dynamic Data Exchange, and Visual Studio Code extensions are all examples of having a standard API which allows lots of different things to plug into it.
My last iPhone’s battery lasted about 5.5 years before it needed to be replaced. Replacing it cost about $90 + tax at the Apple store. The bottom line is Apple products do last and if you need a new battery, you can get one.
I suspect the moral of the story is devops and operations staff need to keep all payments, secret rotations, certificate expirations, etc. on a calendar so no one forgets to pay the bills. I hope the employee who forgot to pay the bill learns from this.
Ops is an interesting domain, nobody knows what they do until they don't do it; so everyone wants the jobs to disappear, and when they do it's fun what happens.
I'm beyond certain that someone will reply "use a cloud provider", which is ironic, as cloud providers just concentrate these kinds of ops people and charge you through the nose (often an order of magnitude more in my experience) than having people responsible.
Unpopular opinion, probably, because people seem to like dehumanising operations issues on this site- sure, things can be automated, but at some point there's got to be some responsibility.
If a technical person is even close to involved with paying for a SaaS Discourse forum hosting something is extremely wrong. This is part of business operations or finance. This is already a "cloud provider". It's the same as paying for Google Workspace or an HR platform.
I would expect more professional operations considering the very high salaries of Mozilla foundation management and I would not blame any particular employee for this problem.
More likely no-one "forgot" to pay. Typically administration optimizes payments. Getting a large corp to pay a small contractor or service provider at all let alone on time can prove to be a nightmare.
You do know most companies in the world have a department specifically for handling financial matters, right? (Hint: it's not the IT department)
Also, I don't know if you're aware of this, but technology has advanced sufficiently that nobody needs to manually pay a monthly bill anymore. I know it sounds crazy, but there's these things called "bill pay", and "recurring credit card changes", that have existed for 20ish years now. Might want to read up on the latest trends!
Netflix is very profitable. Its net income for 2022 was $4.4 billion; for 2023 it was $5.4 billion; and in 2024 it was $8.7 billion. For more information, go to https://ir.netflix.net/financials/quarterly-earnings/default... . The 2024 Q4 earning announcement has a spread sheet with Netflix's financial results for the last 3 years.
A Computer Science degree does not teach you to be a good software engineer. In fact, you don't even need a degree to be a good software engineer. For 99% of the software engineering jobs, employers are not looking people who know the theory of computation, algorithmic complexity, operating systems, compilers, or even how a database works. What they want is the following:
0. A strong desire to solve the user's problem and the organization's problem.
1. Knowledge of a major programming language like JavaScript, Java, Python, C/C++, C#, etc.
2. Knowledge of how to use an SQL database or maybe a no SQL database.
3. Knowledge of how to debug the build process and write scripts in Bash, PowerShell, etc.
4. Knowledge of at least 1 major framework.
5. Knowledge of Linux, MacOS, or Windows.
6. An ability to read documentation and learn.
7. An ability to debug large programs and fix bugs without introducing more bugs.
8. A desire to think critically and choose the appropriate technology for the problem (very hard, takes a lot of experience).
9. An ability to write clear code which others will understand.
10. The ability to write, argue, and persuade others.
11. A good person who works well with others, puts the product before himself, and is honest.
Almost all of these things are not taught to computer science majors. At best, a person will learn 1 to 2 languages and maybe Linux. Expecting computer science programs to produce good software engineers is crazy because software engineering and computer science are two different things.
I uses the business version of Office 365 for e-mail. It works well. I never have a problem with e-mails not being delivered or going into a SPAM folder. I am not saying your family did anything wrong. What I am saying is e-mail works well for some people.
Yeah, unfortunately that seems to be the best way to handle this kind of thing but unfortunately that costs $6/person/month so our ~50 person casual email list for organizing fantasy football and family reunions would cost almost $4k/year.
I have never ever seen this. If your "friends" treat you badly because of your phone choice, they are not really your friends. Also, iMessage is not that great. It's nice but it is not amazing like some people make it out to be.
I totally agree with you, but it's pretty obvious why this behaviour exists. At the end of the day, a cell phone is as much a status symbol, something akin to the clothes you wear, as much as it is an actual phone. Would you potentially lower your opinion of someone wearing a strange piece of clothing? The principle is exactly the same.
reply