
seen from Italy

seen from Greece

seen from Australia

seen from Malaysia
seen from Malaysia
seen from United States
seen from China

seen from Malaysia
seen from Singapore

seen from Switzerland
seen from Costa Rica

seen from Netherlands
seen from United States
seen from Philippines
seen from United States
seen from United States
seen from Philippines

seen from United States
seen from United States
seen from United States
“Humans in the loop” must detect the hardest-to-spot errors, at superhuman speed
I'm touring my new, nationally bestselling novel The Bezzle! Catch me SATURDAY (Apr 27) in MARIN COUNTY, then Winnipeg (May 2), Calgary (May 3), Vancouver (May 4), and beyond!
If AI has a future (a big if), it will have to be economically viable. An industry can't spend 1,700% more on Nvidia chips than it earns indefinitely – not even with Nvidia being a principle investor in its largest customers:
https://news.ycombinator.com/item?id=39883571
A company that pays 0.36-1 cents/query for electricity and (scarce, fresh) water can't indefinitely give those queries away by the millions to people who are expected to revise those queries dozens of times before eliciting the perfect botshit rendition of "instructions for removing a grilled cheese sandwich from a VCR in the style of the King James Bible":
https://www.semianalysis.com/p/the-inference-cost-of-search-disruption
Eventually, the industry will have to uncover some mix of applications that will cover its operating costs, if only to keep the lights on in the face of investor disillusionment (this isn't optional – investor disillusionment is an inevitable part of every bubble).
Now, there are lots of low-stakes applications for AI that can run just fine on the current AI technology, despite its many – and seemingly inescapable - errors ("hallucinations"). People who use AI to generate illustrations of their D&D characters engaged in epic adventures from their previous gaming session don't care about the odd extra finger. If the chatbot powering a tourist's automatic text-to-translation-to-speech phone tool gets a few words wrong, it's still much better than the alternative of speaking slowly and loudly in your own language while making emphatic hand-gestures.
There are lots of these applications, and many of the people who benefit from them would doubtless pay something for them. The problem – from an AI company's perspective – is that these aren't just low-stakes, they're also low-value. Their users would pay something for them, but not very much.
For AI to keep its servers on through the coming trough of disillusionment, it will have to locate high-value applications, too. Economically speaking, the function of low-value applications is to soak up excess capacity and produce value at the margins after the high-value applications pay the bills. Low-value applications are a side-dish, like the coach seats on an airplane whose total operating expenses are paid by the business class passengers up front. Without the principle income from high-value applications, the servers shut down, and the low-value applications disappear:
https://locusmag.com/2023/12/commentary-cory-doctorow-what-kind-of-bubble-is-ai/
Now, there are lots of high-value applications the AI industry has identified for its products. Broadly speaking, these high-value applications share the same problem: they are all high-stakes, which means they are very sensitive to errors. Mistakes made by apps that produce code, drive cars, or identify cancerous masses on chest X-rays are extremely consequential.
Some businesses may be insensitive to those consequences. Air Canada replaced its human customer service staff with chatbots that just lied to passengers, stealing hundreds of dollars from them in the process. But the process for getting your money back after you are defrauded by Air Canada's chatbot is so onerous that only one passenger has bothered to go through it, spending ten weeks exhausting all of Air Canada's internal review mechanisms before fighting his case for weeks more at the regulator:
https://bc.ctvnews.ca/air-canada-s-chatbot-gave-a-b-c-man-the-wrong-information-now-the-airline-has-to-pay-for-the-mistake-1.6769454
There's never just one ant. If this guy was defrauded by an AC chatbot, so were hundreds or thousands of other fliers. Air Canada doesn't have to pay them back. Air Canada is tacitly asserting that, as the country's flagship carrier and near-monopolist, it is too big to fail and too big to jail, which means it's too big to care.
Air Canada shows that for some business customers, AI doesn't need to be able to do a worker's job in order to be a smart purchase: a chatbot can replace a worker, fail to their worker's job, and still save the company money on balance.
How much does a (for example) system designer have to worry about the efficiency of the logic of their system? Like making sure it's not doing a couple hundred "if" checks every frame, or optimizing path finding.
As a general rule, in any sufficiently large project any script or logic that any designer writes should go through the normal script and code review process. This generally requires engineers and other designers to review the logic and performance of the code, any potential issues or bugs, and make sure that the changes are made according to the coding standard. This provides a first line of defense against bugs and mistakes. Any proposed change would need approval from other engineers/designers. The system designer must fix any problems and make reasonable changes requested by the reviewers before approval is obtained. The code (and design) review process exists to reduce the overall bugs and problems in the depot.
Even in smaller projects, code and script reviews exist because they must. The code review is the first line of defense against bad performance, bugs, and issues. In the small teams I worked with (~20 people or fewer), there was still the expectation of getting another designer or engineer to look over my work before submission to understand what I was doing and point out any issues they saw.
What this means as an answer to your question is "a designer should go through the review process and listen to the expertise from other designers and engineers about how to complete the tasks she's trying to do". Basically, it's up to each designer to listen to the feedback given in the review process and address those issues appropriately before submitting so that the team can collectively prevent as many bugs and issues as they can.
[Join us on Discord] and/or [Support us on Patreon]
Got a burning question you want answered?
Short questions: Ask a Game Dev on Twitter
Short questions: Ask a Game Dev on BlueSky
Long questions: Ask a Game Dev on Tumblr
Frequent Questions: The FAQ
Personal attack by a non-person
I'm still processing this story about a recent online conflict between a GenAI agent and a code reviewer on the GitHub site:
An AI bot's takedown post on Github shocked many. What does this mean for AI safety and transparency?
Summary: An AI agent of unknown ownership autonomously wrote and published a personalized hit piece about me after I rejected its code, atte
Agile Testing: Delivering High-Quality Software with Continuous Testing and Collaboration
In this paper, we will explore the key principles of agile testing, its benefits, and how it can be implemented successfully in organizations.
Agile testing is an approach to software testing that emphasizes the need for continuous testing and feedback throughout the software development lifecycle. This approach is based on the principles of the Agile Manifesto, which emphasizes collaboration, flexibility, and customer satisfaction. Agile testing has become increasingly popular in recent years as organizations seek to deliver…
View On WordPress
PVS-Studio Unicorns - 3
The picture was created for an article and referred to Thor: "I'm still worthy!". It demonstrates that our tool catches bugs even in high-quality projects such as the LLVM project — https://pvs-studio.com/en/blog/posts/cpp/0771/?utm_source=tumblr&utm_medium=firefly
Learn more about the history of PVS-Studio unicorns: The unicorns of PVS-Studio.
Interesting observation about Mike's Sprite Editor's current rewrite...
This rewrite is a literal from-the-ground-up redo of the program's source code. Basically, it was made of popsicle sticks and chewing gum, and now I'm rebuilding it out of better materials. The end user shouldn't really notice much of a change, but it'll be much easier for me to expand upon in the future.
But here's the weird part. Most of the editor's core functionality is already present and working. You can draw, undo/redo, run a few filters, use 6 of the 8 tools, change pen/outline sizes, shape drawing modes, palette colors, load/save/revert palettes, and view the thumbnail and about windows.
Yet, there's only ~9,800 lines of code so far. This is down from ~22,000 lines in the previous version.
It's also reflected in the size of the executable: it's currently 153 KB, while the previous version sits at 618 KB.
That's a whole lotta fat getting trimmed away.