Oh that’s really interesting; I hadn’t considered racing games as a genre to benefit from this type of machine learning. I guess I figured there’s not so much to AI there that it’s necessary, at least when we already know the “ideal lap line” for cars to follow, but yeah it gets a lot harder when considering other drivers on the track and a huge array of unique car models with their own handling and performance characteristics.
I wouldn’t mind an AI using unorthodox strategies, but yeah that’s a good point that fine tuning it to be fun is a big challenge. Speaking of “non-player-like behavior”, I wonder if AI could be used to find multiplayer exploits sooner, though the problem there is you don’t really have much training data besides QA and playtesters before a full release.
I’m not into fighting games, but that’s pretty neat! I hope the industry follows suit if people like how it works in Street Fighter 6.
Yeah management is totally backwards there; it’s like the building manager on a construction project going “all electrical needs to be done in X weeks”, but realistically they have no direct control over that deadline being met by declaring an arbitrary deadline. The unfortunate difference is that if you do a shitty job wiring a building, you’ll fail inspection and have to spend more time and money fixing it. Software can often hobble along; there aren’t strict enforcements for quality that the business can legally ignore, so you’ll always have sad defeated devs go “okay boss, we’ll skip the things we need to get this done faster for you (I hate this job and don’t care about the product’s long term success)”. Having a steady supply of those people will slowly kill a software company.
In the past, I’ve dealt with estimate pushback not by explaining what necessary work can be removed like tests, documentation, or refactoring, but by talking through ways to divide the project more effectively to get more people involved (up to a point, a la mythical man month). That seems to go more proactively. Then we look at nixing optional requirements. But, I’ve also usually dealt with mostly competent engineering management.
The thing that frustrates me about developers who feel powerless over technical debt is…who is actually stopping them from dealing with it? They way I see it, as a software engineer, your customer is sales/marketing/product/etc. They don’t care about the details or maintenance, they just want the thing. And that’s okay. But you have to include the cost of managing technical debt into the line items the customer wants. That is, estimate based on doing the right things, not taking shortcuts. Your customer isn’t reading your commits. If they were, they wouldn’t need you.
It would be bizarre if your quote for getting your house siding redone included line items for changing the oil on the work truck, organizing the shop, or training new crew members. But those costs of business are already factored into what you pay at the end of the day.
Yep typical ratings are oriented relative to the “average” consumer. But no person is actually THE average.
It’s a useful place to find out if something totally sucks though. That’s how I use it. 60+? Probably good, at least for some audiences. Less than that? Only if you’re already hyped or a fan of whatever thing it’s related to.
Slappers only, no oddjob
They probably wanted to use Rust but got frustrated by its struct and impl paradigm.
Yep. You do need at least a sound bar, or a stereo system with these. But most inbuilt TV audio is pretty terrible to begin with, at least on low to mid end tvs.
Actually he got a good deal. Those screens are more expensive because they don’t come bundled with ad riddled toiletware, and they often have a longer lifespan to accomodate being on for so long every day. Depends on how much it got used already though.
On the gender controversy…the Olympics pool from so many humans that for many years now, you can tell just visually that top contenders are those naturally selected with genetic traits lending them unusual prowess in their sport. For strength based sports, more women with male traits rise to the top and vice-versa for men in more physiologically female dominated areas.
Which is faster, getting a squiggle instantly or discovering a silly bug at runtime later? So happy I could write code in Typescript and be confident it would do what I expected when it ran without digging out the debugger.
The language and its standard libraries lead developers towards common patterns. Javascript’s standard library is pretty sparse excluding browser-only web apis, so there are tons of external libraries to fill the gap for better or worse.
How many open source projects have 50 million lines of code like Windows, or legal agreements related to backwards compatibility and version support guarantees?
A for-profit company is going to focus on whatever generates revenue, sure. But crappy software will lose customers in a non-monopoly scenario. They’re not exactly incentivized to make broken things nobody wants.
That’s…a gross oversimplification. Super popular open source projects tend to have few bugs from the sheer number of contributors available to fix them, but active proprietary software has dedicated teams working fulltime every week to deal woth issues. Proprietary stuff is often way wider in scope than open source, so more surface for bugs to creep in. Scope and team size have a lot more to do with bug density than open vs closed source.
All i read is “Damn, they’re a super capable team.”
No, dont waste your time. Apple products are not repairable by end users.
Oh yeah, I read about that! Not really ML, but pretty much what I’d like more games to have.