IT’S TIME.
Download FIFA Heroes now and check out iShowSpeed’s power moves on the pitch!
Get it on the App Store & Google Play today, and PC and consoles later this summer.
https://t.co/634jFYXsix
@FIFAWorldCup@ishowspeedsui
A new tier of celebrities incoming 🤖
Robots with personalities have been and will continue to take over the internet.
Ordering a wrap today! Thanks for making it easy 🙏
I built 90% of a game in 5 days.
Not a prototype. A real game releasing soon.
Just started at @ENVERhq as Principal AI Engineer. They're behind MotoX and Scary Baboon on Quest.
I designed an AI system and pointed it at the game design doc. It ran for 2 days straight and gave me a playable and tuned game.
Game dev is splitting into two camps right now. Engineers who are learning to manage compute. And engineers still writing every line by hand.
One group runs studios. The other gets left behind.
We're hiring for the first camp. Unity devs who are deep in AI.
DM me if that's you.
Use of libraries and packages will definitely go down, when I once went to search for something open source or even a package on the Unity asset store it’s now I dont even need to do that
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
Every small business is about to hire their first software engineer.
Not to build software. To manage the AI that replaced the software.
The plumber, the dentist, the local retailer. None of them needed an engineer before. Now they all do.
VR is in the palm pilot phase. Some people are getting a lot of value out of it, but it’s not for everyone and it’s not a must have for most.
The first palm pilot launched about a decade before the iPhone, which was the breakout moment for smart phones.
Quest 1 launched in 2019 and I think there’s a decent chance 2029 will be our breakout year for VR.