|
|
|
|
|
by kortex
30 days ago
|
|
I think my company is a microcosm of the current state. The non-engineering side (HR, correspondence, marketing) are on the "forced adoption" side, giving out gift cards to folks using Glean the most. In engineering, we can't raise token budgets fast enough. Devs are "routing around damage" when they hit caps, going from claude to opencode to copilot. Productivity is up (roughly) 100-300% in terms of story points and 75-200% in lines of code. And defect rate is down [0], more bugs are caught in review before QA or prod. Our teams are just starting to figure out our new workflows too, for design -> spec -> code -> review, it'll only get better as we refine the process. It's looking like software industries will reap massive benefits, while most others which have some error tolerance will only see modest gains. It's unclear how it will impact high accuracy fields like legal (it might even be net negative). Also which is it - a useless technology that has to be force-fed because it sucks, or a economy-shaking game changer that will put folks out of jobs en masse? Those seem like a contradiction. 0 - i think process here is extremely important. I think it would be very easy to create an unmaintainable slopocaplypse. We have an informal platform team of about three (including myself) that have been affectionately and informally dubbed the Tech Priests of Mechanicus Adeptus (warhammer reference) that ensure the prompts/skills and associated tooling are optimal, that code standards are enforced, and that solutions are converging at the system-wide level. |
|