• 0 Posts
  • 47 Comments
Joined 1 year ago
cake
Cake day: July 23rd, 2023

help-circle





  • Absolutely (re: theming and tuning)! My actual work scheme is a slightly off white and a lighter transparent black, which is closer to the theming you’re talking about. I’m also just really happy with simple stuff, possibly because I did have that old CRT experience? Your point about size is well-taken. I read this article on my phone (which is my travel ereader) and wasn’t bothered. I hadn’t considered size there.




  • I’ve skimmed these and I’m not convinced they’re worth the purchase. Every time there’s a Packt bundle it’s a mixed bag. I don’t think these are great for a beginner because of the usual Packt concerns and I don’t think they’re great for an expert because of the usual Packt concerns. For the midtier unless you need these right now and have no other resources, it’s a better bet to wait for a similar bundle, even in other languages, from Manning or O’Reilly.






  • Developer productivity can definitely increase with codegen tools. The example of a stadium (or player animations) is also feasible assuming they move from developing a stadium rig + code to building something that builds a stadium rig + code. Most of this shit is gluing boilerplate together with minimal thought until you need to do things like optimize, solve new problems, or refactor the codegen spaghetti a few levels deep.

    The more you rely on codegen, the more talented your engineers have to be because the easy shit goes away. That means it’s not necessarily cheaper because you shift your problem domain. You can definitely get a boost. 30% seems way too fucking high without serious in-house tool development, which doesn’t sound like their plan. Tabnine trained on EA’s shit code isn’t going to make them that much more efficient.

    Also 50% more gamers? Yeah, bullshit. Sports games are going the way of streaming services. Everyone wants to do their own thing. Your audience there can’t go up much unless you improve access to consoles for your games or increase fans that like games of the sport they’re a fan of. We’re 30+ years into that; not really sure there’s much of a market with current tech. On the other end, shooters like CoD are also probably saturated. I just don’t see how the next Star Wars or Sim City flop could bring in 300mil net new users much less, say, a new Fortnite. I find it very hard to believe there are that many more users in the total addressable market that don’t touch EA games that would touch a new one.




  • I feel like there’s a total lack of grokking period. Using reductive phrasing like “social API” suggests that there are actual rules to human interaction we understand and can currently define. While there might be a semblance of provincial rules (take the notion of justice, imo tightly coupled with apologies, and see how it differs across the world), there’s nothing universal and certainly nothing that rises to the level of a fucking application programming interface.



  • I don’t give a shit about the title. I think it’s a joke. The analysis you’ve given suggests you don’t understand both software and engineering.

    • Bandwidth is much more than what data centers put out. There’s a constant question of request/response size and the factors that go into scaling. If your idea of web development is just code minification, your idea is wrong.
    • Engineers can’t pass the design buck. If you wouldn’t tell a hardware engineer, “the design of the circuit board doesn’t matter; don’t worry about size or crossed circuits,” then you can’t tell an engineer the use of the systems they design is just the realm of the designer. I know a few industrial engineers that would be annoyed by your ignorance of an entire branch of engineering.
    • Why does everyone want to be an engineer? I’m really missing that point.

  • I think this is a terribly naive view of the impact the physical world has on software development. Most web development is actively concerned with throughput which is governed by bandwidth limitations and API construction. The user experience concerns that go into, say, the design of medical interfaces is no different from the design considerations of physical switches in a cockpit. Alert fatigue is just as much a consideration for monitoring in software as it is for industrial controls.

    I also disagree that engineering is applying physics for user experience concerns I brought up. If your industrial controller makes it impossible to understand what’s going on when shit hits the fan (eg Three Mile Island), I would argue you as an engineer have failed. That’s not applying physics unless we’re stretching “applied physics” to cover the movement of subatomic particles through brains as psychology.