• 0 Posts
  • 45 Comments
Joined 1 year ago
cake
Cake day: August 3rd, 2023

help-circle
  • You now need to remember his velocity, his position on the map, the direction of his flight, his altitude, his plane’s weight and who knows what else, I’m not a pilot.

    You’re not wrong per se, but I’m having trouble fathoming gigabytes of data being consumed by these types of parameters. You could probably track hundreds of thousands of airplanes with that much space. The only thing that I could imagine taking up that much memory is extremely detailed airflow simulation.

    However, as a rule of thumb, the vast majority of memory data for video games is in most cases textures and geometry, and not so much the simulation. Based on the article, it seems this game streams high resolution geometry data based on your current location on earth, which I would say is the most probable reason it asks for so much memory.








  • Laura Chambers, who stepped into an interim CEO role at Mozilla in February, says the company is reinvesting in Firefox after letting it languish in recent years,

    It’s sort of amusing to me that Mozilla would let the Firefox browser languish. Is that not the raison d’etre of your entire organization? What are you doing with your time and effort if you are allowing your core product to languish? What would people say if Microsoft said “yeah, we’ve allowed windows to languish in recent years.” What an insane notion.




  • Yeah I agree I hate this kind of obstructive customer service

    I work as a software engineer on automated customer service systems like these, and boy let me tell you, obstruction is the name of the game. For example: don’t make the phone number too easy to find on the website because it will lead to too many calls. We nudge people toward the FAQ and such first so they can hopefully find their answer there. Then, we have chatbots like this which contain exactly the same information as the FAQ again. And only then might we offer you contact with a human.

    The essential problem is that support is a cost center, so cost savings is the name of the game. We optimize for metrics like:

    • “deflection” (number of calls averted because we pushed the user into automated tools instead)
    • “first call resolution” (percentage of issues resolved in one contact. How do we know if your issue is resolved? Simple, if you don’t contact us again we assume the issue is fixed)
    • “Average contact time” (pretty obvious, get the customer off the phone ASAP)

    If you manage to get on text chat with a human, typically they are handling two other conversations at the same time, that’s why they seem so absent all the time (and why companies love chat. Much cheaper than calling).

    I’m not saying we’re all diabolical here. There is a general agreement among everyone in the industry that we should help the customer as well as we possibly can. Indeed every CS manager will tell you how important we are to our brand image and NPS, how we strive to be the most customer-friendly company etc. etc.

    But the numbers don’t lie. If you look at the metrics that everyone actually optimizes for, it’s cost cost cost.


  • VW is good at making cars, but bad at software. They’ve had to delay the introduction of new models (Golf, ID.3) because of software issues. Rivian has sort of the opposite problem: their production lines sit still often because of problems in the supply chain.

    Volkswagen has the expertise to solve Rivian’s production and supplier problems, and the cash they will need to survive and develop some cheaper models (the EV market is stagnating right now for a lack of budget options, and Rivian only sells trucks and SUVs). And they’re hoping Rivian software engineers can help them fix their software woes.




  • Honestly, I think it may be possible to build entire roads with enough crushed metal elements in the asphalt/concrete and a slight low power charge throughout the entire surface would be able to keep any vehicle battery at a steady charge.

    You might be underestimating how much power a car consumes while driving. For example, a Tesla model 3 has an efficiency of about 130 Wh/km in mild weather at highway speeds. Assuming that on the highway you’ll travel 100 km/h, that means you’ll use 130*100 = 13.000 Wh/h, a constant power draw of 13kW. That’s enough to power perhaps 8-12 houses on average.

    A km of road could have, let’s say, 200 cars on it (4 lanes, 20m per car). That means you’d need to pump about 2.6 megawatts of power into every kilometer of road to keep them all topped up.

    EDIT: fucked up math


  • I don’t really care about the declarative/imperative thing, to me how many commands you “really need” is beside the point. This is essentially the same argument as the people who say “git is not complex because you only really need checkout/commit/push, just ignore all the other commands.” This doesn’t matter when the official documentation and web resources keep talking about the other billion commands. Even home-manager has this warning at the very top of the page that basically tells you “you need to understand all the other commands first before you use this,” and “if your directory gets messed up you have to fix it yourself.”

    These are exactly the same kinds of problems people have with git.


  • The confusion arises because there are 5 different ways to do the same thing, the non-experimental methods shouldn’t be used even though they’re recommended in the official docs

    I appreciate what you’re trying to say, but you’re kind of illustrating exactly the point I was making about conceptual simplicity and atrocious UX.