Patrick Karsh

99% success rate on a site we’d never seen before. Not bad for launch 🚀 Developers build on Deck to interact with websites that have no APIs, reading or writing data wherever users need it. What’s remarkable is the quality and consistency, even across new, unseen systems. Auth Agents are redefining what “integration” means. Check our guides if you're ready to start building: https://lnkd.in/eG4h6aMS

84

Clients don’t come first. The team does. It’s the team that shows up, handles pressure, solves problems. They deserve protection, support, and transparency from leadership... especially in async environments. Cory Blumenfeld breaks it down perfectly. Watch the full episode here: https://lnkd.in/gYe6eKmE #AsyncWork #TeamTrust #LeadershipCulture #RemoteWorkLife #ProtectYourPeople

88

82 Comments

What's the MACH Alliance for? It's a question I've been asked a great deal and to take it back to first principals it was to promote architectures (unashamedly technical) to support customer choice, excellent user experience and interoperability between best of breed vendors. Has that worked? That's a debate that can last hours - the good MACH projects, the ones on stage at the various MACH events show that it absolutely can work. Have there been horror stories - of course, plus ça change in IT. However, one thing that has been announced and now released is the MACH Common Data Model. Search my LinkedIn and you'll find a link to a (now unavailable) blog I wrote in 2019 (I think; Stacey Trimnell-Ritchard remembers it I hope as she said she used it in a marketing conversation back then so it did happen 🤣) calling for this and so it's brilliant to see it now exists: https://lnkd.in/eTFVgYKX What is it? In their own words: "The MACH Alliance Open Data Model (ODM) initiative is the natural next step in enabling interoperability across composable ecosystems. It serves as a semantic interoperability layer: a "Rosetta Stone" for understanding how to translate data between systems in hybrid commerce architectures. It provides canonical reference models and implementation guidance that enable architects to design effective data integration across commerce platforms while preparing organizations for AI-powered ecosystems." I'm interested and signed up and I know we're looking at how we can incorporate the ideas into Patchworks (the platform already supports this of course and it will help our AI mapping tools no end). Find out more by attending MACH X in October: https://lnkd.in/epHx2JVp

42

3 Comments

There comes a time in every rapidly growing SaaS product's life when you need to stop releasing new things and fix the core. For Claude Code, that moment is now. I love CC - it's the most impactful piece of new tech I've used in years. However, the last few releases are full of regressions - the fact that the CC team use CC for 100% of commits (supposedly) may be a factor. I think they are 'drowning not waving' now. In numbers (Claude's analysis of it's own repo - verbatim): "Historical close rate: 20,149 closed / 365 days = ~55 issues closed/day  Current intake rate: 160 issues/day  Net change: 160 - 55 = +105 open issues/day (growing, not shrinking) They'd never clear the backlog at these rates. It's getting worse by ~105 issues per day. The 6,383 open issues would double in about 60 days. To clear all 6,383 open issues they'd need to close 160+/day just to stop the bleeding, then extra on top to eat the backlog. At, say, 200 closed/day (nearly 4x their current rate) with 160 incoming, that's a net -40/day — so ~160 days (~5 months) to clear the backlog.  In short: Claude Code's issue tracker is underwater." Anthropic - I get it. It's a tricky balance between velocity and quality, but you're approaching a watershed moment, and I want to keep using Claude because it is amazing.

27

9 Comments