Ben Gilbert

The sci-fi hits keep coming... Australian startup Cortical Labs has launched the CL1 biocomputing platform (https://lnkd.in/e-Mvi2GV), a groundbreaking device that fuses human brain cells with silicon technology, offering unprecedented insights into neural processing and learning mechanisms. The CL1 platform contains 800,000 lab-grown human neurons on a silicon chip, with cells that can adapt, learn, and respond to external inputs in real-time while remaining viable for up to six months. This innovative "brain in a vat" approach enables researchers to study neuronal behavior and potentially explore neuropsychiatric treatments through direct observation of neural networks. Priced at $35,000 per unit or $20,000 in 30-unit server racks, the platform represents a significant breakthrough in biocomputing technology, bridging the gap between biological intelligence and artificial computing systems for research and therapeutic applications.

5

Today, Gloo launched Gloo AI Studio, a production-grade development platform designed specifically for developers serving churches, ministries, nonprofits and mission-driven enterprises. Gloo AI Studio enables teams to move fast without cutting corners, because values-alignment cannot be bolted on after deployment. It must be embedded at the model and infrastructure layer. AI infrastructure decisions made today will shape how intelligence is distributed and trusted for decades. https://lnkd.in/gSNDHKDf

230

11 Comments

Curious about how to build a cleaner, more modular application? This article dives into the power of Domain-Driven Design (DDD), using a video processing app as a real-world example. Discover how DDD helps you: Create a Ubiquitous Language for better collaboration Break down systems into manageable Bounded Contexts Separate business logic from technical details Write clean, testable code Check out the full guide: https://lnkd.in/d5YCdxAd https://lnkd.in/d-XHyA5G #SoftwareArchitecture #DeveloperLife #Programming #CodeQuality #TechArticle

1

Sustained ~252–291 GiB/s of HBM memory throughput on H100s under decode load — essentially hitting the hardware roofline. This matters because HBM throughput, not FLOPs, is the real bottleneck in LLM inference. By keeping memory nearly fully saturated, I’ve unlocked far higher efficiency and throughput than standard engines. The result: 0.9–1.36M tokens/sec with ~0.1 ms first-token latency  #AI #LLM #GPURouter #H100 #Inference #CostEfficiency #Innovation #DeepLearning #AIInfrastructure #HighPerformanceComputing NVIDIA AMD OpenAI Google Shilpa Kolhatkar Keith Strier a16z speedrun

5

Wraps on an eventful week in robotics! Investment into robotics is booming across the board but how long will it really take before we see significant impact in any industry, in the labor market and in addressing social issues? https://lnkd.in/g6RJjVUQ

31

ROAI raised $1M in seed funding to develop XELO, an AI-driven one-click smart factory platform enabling fully autonomous, scalable, and easily configurable manufacturing solutions. https://lnkd.in/gvcqa5ac

3

1 Comment

With 8th Wall winding down, it’s good to see players like GEENEE and Cory Grenier’s team stepping up with continuity support. For anyone currently looking for stable WebAR options, this might be a viable path to explore. Good to see parts of the ecosystem showing up. The team at innovation.rocks (now svarmony) did a few tests and early projects with GEENEE back in 2019, and we genuinely enjoyed working with their approach at the time. As a small proof point, here’s a short clip from those days — #WebAR tracking performing surprisingly well as shown during AWE in Vegas on a shiny, round-shaped Red Bull or Coca-Cola can.

3

I'm incredibly excited for this talk. Top K queries are the backbone of search engines, which have historically been NoSQL databases unable to execute JOINs. We're fixing this with ParadeDB. Highly recommend attending, I promise you'll learn something!

36

I love Rails. I've built my wealth on it. That's exactly why I think we need to have an honest conversation about its biggest blind spot. Eileen M. U. gave a brilliant talk at Rails World last year: "The Myth of the Modular Monolith." After 6 years of modularizing Shopify's monolith, she concluded: "You can't solve human and cultural problems by changing your architecture." She's right kinda of about the culture part. But stopped one step short. Rails doesn't just allow tight coupling. It incentivizes it. ActiveRecord makes every model globally accessible from anywhere. Any controller, any model, any job can reach into any table through any association chain. There's no boundary enforcement. No import restriction. No compilation step that says "this module shouldn't know about that one." When your framework makes coupling the path of least resistance, blaming developers for coupled code is like blaming water for flowing downhill. Shopify tried to fix this with Packwerk. It just give you a map not a real solution. Rails Engines? Been there, done that. They are miniature apps that provide functionality to their host applications. They don't enforce real isolation and they weren't designed for progressive extraction. But this isn't a Rails problem. It's a missing tool problem. Look at what Nx did for the Node/TypeScript ecosystem: → Module boundaries enforced at the import level, not via YAML to-do lists → Dependency graph visualization built in → Affected-only CI: only test what actually changed → Clear public API per module, everything else is private by default → A real path from monorepo module to extracted service Nx didn't replace Node. It gave Node developers the guardrails to build modular systems naturally. The right thing became the easy thing. By default. Rails deserves the same. Imagine a Rails-native tool that: • Enforces module boundaries through autoload paths, not opt-in linting • Gives each module a public API (explicit exports) while keeping internals private • Generates a live dependency graph from actual code usage, not manual YAML declarations • Runs affected-only CI based on that graph Not a replacement for Rails. A companion that makes Rails' conventions work at scale. Eileen is right: culture matters. Education matters. Leadership incentives matter. But culture alone didn't give us CI/CD. Tools did. Culture alone didn't give us code formatting standards. Linters did. Culture alone won't give us modular Rails applications. Rails gave us developer happiness for building products. Now we need the same philosophy applied to building organizations of code. The myth isn't the modular monolith. The myth is that we have the right tools for one. Who's building this? 🎥 Eileen Uchitelle — "The Myth of the Modular Monolith" (Rails World 2024) https://lnkd.in/dabvzHQm

13

🔥 FREE TRIAL! 🔥 We just launched a free trial of Flux that makes it super easy to see what it can do. To achieve this, we pre-populated our trial with a few open source repos. And we grab updates for them to simulate a live environment. As a result, you can experience what Flux would look like with your code - pull request evaluations, trends over time, etc. - without having to load your code. (Although, you can do that, too, if you want :-) Check it out here: https://lnkd.in/eMhBunrf

30

2 Comments