Register and share your invite link to earn from video plays and referrals.

Search results for XGlasses
XGlasses community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including XGlasses
I see such a wide range of AI adoption curves in engineering orgs, it's fascinating. This could be the widest gap we'll ever have, which also makes sense given how big of a shift we're seeing. Right now, I think companies are in one of five stages. And you'll have to take off your X glasses, because all of us yapping on here aren't quite living in reality. Which btw, I like. Many of us are the crazies living in a future that could be a decade or more away, and that's fun to do, together. That being said, here's the stages I see engineering orgs in today. And before you read this know, this is just my (loosely held) opinion. And as I've said time and time again on here, but feel I always need to repeat. I'm not an expert, I'm just an insanely curious guy who loves sharing what I think. So on that note, here's my thoughts on the five stages eng orgs are in right now: Stage 1: Humans still writing code like it's the stone age. - there are less and less companies in this stage by the week, people are moving out of this stage quickly. But yes, believe it or not, some companies still only trust humans to write the code. Stage 2: One lab, one model, one effort level, and usually JIRA for ticketing. - this is the stage where an engineering leader has either decided their team needs to use AI, or an exec told an engineering leader they need to. They usually just go straight for Claude Code, and everyone on the team uses Opus High. Tickets are managed in JIRA, just like they always have been, and humans manage those tickets. Stage 3: Multi-model, driven by a third party model router that picks the model and effort level. Actively building a software factory. - usually people in Stage 2 graduate to this. They start getting crazy high bills from their model provider, and realize they have no idea how to tell their team which model or effort level they need to use for their work. They get pitched the concept of saving 30% or 40% if they switch to a company that offers a model router and decides which model and effort level to use per task. And, in this process, they start building a software factory. Stage 4: Multi-model, driven by internal benchmarks based on real PRs and their actual codebase. Software factory is mostly built. - usually tried auto model routing, but realized it wasn't really optimized for the work each team does. Started doing internal benchmarking and realized that the model and effort level the data science team needs for their python coding, is different from what the data engineering team needs for their python coding. Comes up with model/effort combos by team, but has a hard time keeping up with it. Software factory is mostly built, either moved from JIRA to Linear and now actively hands off tasks to Linear, or moved off a formal ticketing system entirely. Stage 5: feels the most behind, constantly optimizing models and effort levels, most easy/medium tasks are done entirely end-to-end by agents. Fully functioning software factory, but constantly updating and trying to adjust to new model releases. - yes, the first few words here are important. The most advanced stage feels the most behind. Kinda like Einstein with Math. He was quoted as saying, "the more I learn about math, the more I realize I don't know about math." The engineering orgs that are the most ahead, often feel behind. Terra 6.1 comes out, they're scrambling to figure out what they should use it for, where it will save them money/time. Some teams love this excitement, want to constantly change, for others its dizzying. Okay, Wednesday morning brain dump complete, time to play some WOW Forever. Zug Zug.
Show more