apek
306 posts

apek
@apekshik
ai eng @fal / prev @xai / yt @ apek++


Expectation: the age of the IDE is over Reality: we’re going to need a bigger IDE (imo). It just looks very different because humans now move upwards and program at a higher level - the basic unit of interest is not one file but one agent. It’s still programming.



NVIDIA has presented DLSS 5 AI now adds photorealistic lighting and materials directly to pixels

running 5-6 agents in parallel isn’t the real bottleneck it’s managing them. so i built anvil to better manage 3+ agent contexts and windows be able to jump back and forth between them easily.


呪術廻戦 「#死滅回游 前編」 第48・第49話、ご視聴ありがとうございました! この度、LO・原画を担当させていただきました。 Thank you for watching Jujutsu Kaisen: The Culling Game Part 1, Ep.48 & 49! I participated as a Key Animator. *Got permission to post #呪術廻戦 #JujutsuKaisen

It's my honor to handle the ending sequence of ep56 of JJK! I hope you had fun watching it! 🙇 #呪術廻戦 #JujutsuKaisen

很荣幸受到御所圆导演的邀请,参与了56集的部分lo,这对我来说是一次很宝贵的经验,非常感谢这次机会。

Some clarification here: "no green screen" doesn’t mean "no VFX”. There were, in fact, thousands of VFX shots in the film (2018!) Green screen is sometimes used in lieu of building sets or figuring out locations/lighting in advance, which can be noticeable if not done carefully, and is something we didn’t want to do. We built the entire interior of the Hail Mary ship - but within the ship, there were still wire and puppeteer removals and ceiling replacements, etc. When Ryan is outside on the hull of the ship, we shot him in front of a black background for space and a shifting hue background when he was up against the aurora of a planet which allowed for truer interactive light on him than a green screen would. The wide space exteriors and spaceship shots were entirely digital and beautifully done by ILM. Rocky was a seamless blend of puppetry and animation from Framestore. And other great work from many more. It really does take a village and we had the best of the best on our side.







An engineer at Anthropic wrote a spec, pointed Claude at an Asana board, and went home. Claude broke the spec into tickets, spawned agents for each one, and they started building independently. When the agent is confused it runs git-blame and messages the right engineers in Slack. By Monday the agents finished the plugin feature. That's one example of how the best engineers are shipping software right now. Developers will soon orchestrate 50 AI agents in parallel and the difference between a good engineer & a great one would come down to specs. You can't write a spec that holds up at that scale without genuinely understanding what you're building at a deeper level. The next-gen developer who understands the fundamentals, can architect well and orchestrate agent is going to be a 1000x developer!



