Discover real AI creators shaping the future. Track their latest blogs, X posts, YouTube videos, WeChat Official Account posts, and GitHub commits — all in one place.
Final judging today!!!
Today I look at the 25 finalists of the 2026 #Vibejam by @levelsio. It's a gamedev competition where 90%+ of the code must be written by AI. Excited to assess progress in the field. I will be fair, but uncompromising, as usual.
RT Intelligent Internet If Ghost in the Shell changed your brain, this is for you. For one night only we're screening the 1995 masterpiece on the big screen. Come watch and discuss AI, memory, identity, and the soul.
Every enterprise organization receives and generates a massive volume of contracts. Each contract oftentimes follows a non-standardized template. The difficulty extends beyond simply digitalizing the document (OCR) to actually semantically interpreting the meaning of each term and clause. There are references between sections and to amendments. It is non-trivial to use LLMs to make sense of this information both at high accuracy and also in a cost-effective manner (e.g. you can't run Fable/Opus on every page). We see a massive opportunity to provide well-tuned document extraction workflows that can both digitalize and reason across contracts to power production systems at scale. This is courtesy of our Extract feature in LlamaParse. Check out our blog: https://www.llamaindex.ai/blog/extract-contract-metadata?utm_medium=socials&utm_source=twitter&utm_campaign=2026-jun- If you have Extract use cases, come chat: https://cloud.llamaindex.ai/
Contracts are where business commitments live, but most organizations still manage them manually, searching PDFs for renewal dates, chasing down payment terms, and hoping nothing slips through the cracks. The problem isn't just volume. Legacy OCR treats contracts like flat text,
A sandbox A function A server A build Are you getting it!? These are all expressions of the same underlying compute infrastructure. With tweaks to load balancing, concurrency, persistence, overcommit… 2026 is the year serverless and servers finally converge. With no gotchas
One of our most requested features, longer Vercel function runtime, is here. What looks like an innocent tweak of a constant… is actually the conclusion a multi-year compute platform investment. Builds, Sandbox, and now Functions run on our homegrown microVM-based Fluid compute infrastructure. This investment has enabled innovations like function multi-concurrency, Active CPU pricing, and Secure Compute for private connectivity to existing cloud workloads… with lots more to come, in fact, in the coming days and weeks 😎
Vercel Functions can now run up to 30 minutes. Longer duration functions run our next-generation compute platform, now in preview. https://vercel.com/changelog/vercel-functions-can-now-run-up-to-30-minutes
View quoted postRT LlamaIndex 🦙 Contracts are where business commitments live, but most organizations still manage them manually, searching PDFs for renewal dates, chasing down payment terms, and hoping nothing slips through the cracks. The problem isn't just volume. Legacy OCR treats contracts like flat text, unable to interpret what it reads: the same payment term appears under three different headings, renewal conditions are buried mid-paragraph, and termination clauses span multiple amendments. We wrote up how LlamaParse solves this by: ✅️ Preserving document hierarchy ✅️ Using semantic reasoning to identify key fields regardless of how they're drafted ✅️ Mapping everything into validated, schema-aligned output Ultimately, it transforms contracts from flat PDF text into structured data your downstream systems can actually use. Read the full breakdown here: https://www.llamaindex.ai/blog/extract-contract-metadata?utm_medium=socials&utm_source=twitter&utm_campaign=2026-jun-
http://x.com/i/article/2066552183152373760
RT Eden Marco This is 100% true. The best enterprises i have worked with, with the best harnesses are model neutral
🇨🇭Why model neutrality matters more than cloud neutrality did In the cloud era, companies opted for cloud neutrality as a defensive mechanism Model neutrality can be a **offensive** mechanism. It's more important than cloud neutrality for 3 reasons: 1/ The rate of change is
RT Ankit Jain Human-written code died in 2025. Code reviews will die in 2026. A couple of months ago @swyx from @latentspacepod published my take that the traditional code review is dead (https://lnkd.in/g-S7iZeJ) A lot of people had thoughts on that — some agreed, and some pushed back. If the topic is still rattling around in your head, or you want to hear where I think this actually goes from here, I'll be speaking at @aiDotEngineer Come if you want to hear how I see code reviews evolving and a practical verification model that lets engineering teams ship faster without sacrificing quality or control. https://lnkd.in/ggqcygBw
if you use codex's computer use tools Whats the craziest most yolo thing you've done with it? I'll start, codex has: 1. found me a website to fax medical records 2. used docusign to sign something on my behalf 3. its negotiating the sale of a watch 4. guestlist for the 5/5 party what about you?