1,867 karma · joined July 1, 2016
I think that many fast-growing start-ups have decided that it's cheaper and safer to work from home, so maybe WeWork needs to start working and look for other sources of revenue. or do nothing and implode.
I understand that, from economic perspective at least. "Is it worth it?" is a phrase I hear (often also saying myself) a lot when talking about investing time=money in something. I am afraid talent is absolutely worth it, and it's up to the hiring company, not the applicants, to solve that problem.
On the applicants side, especially those who are well aware of their talents, they also think "Is it worth it all? Getting a degree just to be able to apply for positions in big-time companies? I don't think so."
It seems to me that instead of putting more effort into "sorting through the absolute flood of applications", or perhaps even finding a solution for that problem, HR just ramps the qualification bar even higher disregarding the possibility that higher education is not actually needed, and that talent is not necessarily reflected in any sort of degree. At the same time, it de-values higher education.
You absolutely expect employees having the "best" education, giving 100% and going the extra mile without actually willing to put up the work on hiring talent based on reality.
Ergo: AAA studios are setting up to fail finding talent themselves. Talent without university/college degrees rarely get a chance, so, with enough energy, they start doing stuff by themselves.
Why?
Why are you using Github then?
Does that also include console copies I wonder?
I have blacklisted EA/Origin and Konami already, now Ubisoft is entering the list. Do not support money-milkers.
Why are there code paths nobody uses, that have to be maintained, in the first place?
> Optional telemetry, of course, but again - this creates a selective and unpredictable reality. Ordinary people don't care either way, and nerds will always make deliberate choices that often have nothing to do with product or profit or anything else entirely.
So, by that logic, users who opt out of telemetry are aware of why they are doing it. People who don't care share their chaotic usage patterns. This creates a false picture of usage reality, and makes software worse. In conclusion, there are only two remaining choices: 1. Make telemetry non-optional 2. Ditch telemetry and rely on QA studies
Restaurant management wanted to compare different soup offerings by counting orders from each soup to determine which ones were more popular. They have selected the most popular two offerings, the rest were scrapped in order to safe money on ingredients. Soon after, not only did the order numbers of those two soup offerings drop, the total number of soup orders dropped. How come? Well, maybe nobody has asked the customers if the offered soup was tasty at all. A quick survey revealed that customers make the popular choice, find out it's crap, and then do not ever order soup again in that restaurant, or in rarer cases give the other one a shot. It turned out, the most popular offer was basically cheap crap nobody wanted to eat, and when there's nothing else, they keep ordering the same, or never visit that restaurant again.
Telemetry does not tell anything about user preferences. Who ever is selling you that idea, does not either.
Looking at the current developments in AI, I am concerned that AI models can easily de-anonymize and guess end point users when being fed with "telemetry data" of hundreds of thousands clients.
I hear a lot and read a lot of software and hardware vendors saying that "telemetry" is supposed to somehow magically improve the user experience in the long run, but in actuality software tends to get worse, unstable and less useful.
So, I would like to know how exactly any telemetry data from Fedora Linux clients is going to help them, or how is it going to improve anything.
OpenSuse Tumbleweed should be renamed to OpenSuse Testing.