Crunchloop

We went to the Facultad de Ingeniería de la Universidad ORT Uruguay job fair to talk about how we work. We ended up listening more than we talked. That’s part of how we build a team, understand what people are looking for before telling them what we offer. #Crunchloop #LifeAtCrunchloop #ORTUruguay #TechUruguay

Forward Deployed Engineering is being presented as something new. It isn't. Good consultancies have always worked this way: engineers working directly with clients, understanding their systems, and making decisions rather than just completing tickets. The problem is what happens when they leave. Most of the knowledge leaves with them. That's what we've been building with Dap. It keeps the client's system context, including architecture, decisions, and history, so the knowledge stays and continues to grow. And Crunchloop stays involved. The same engineers and platform remain responsible for keeping things moving. If that model is what you've been looking for: https://lnkd.in/d79Xyubr #Dap #Crunchloop #AI

We’re looking for a Senior Ruby on Rails Full Stack Developer to join Crunchloop. This role is for someone who takes pride in the code they ship, likes working through hard problems with a team, and keeps learning along the way. What we’re looking for: → 5+ years building with Ruby on Rails → Solid judgment on architecture, databases, and automated testing → Hands-on experience with Docker and containerized deployments → Advanced English What you’ll find here: a close team, direct communication, and real room to grow. 📍 Full-time, hybrid, with offices in Montevideo and Buenos Aires. Read more about the role and apply: https://lnkd.in/dsMvHhyG

Proud to have been a Silver Sponsor of Rails World 2026. More than 1,000 developers, 27 speakers, and a lot of honest conversation about where Rails is heading and how AI fits into the work we do every day. All the talks are now online. If you couldn’t make it to Austin, this is the place to catch up. #RubyonRails #RailsWorld2026

You don't get trust in agents by asking for it. You get it by making the reasoning visible. The question that matters after an agent touches your code isn't "did it work?" It's "what did it do, and why?" — and if that answer lives in a log nobody reads, trust stays where it started: at zero. Trust is built when you can see each decision, the context behind it, and the trail it left — before, during, and after the work. That's why visibility is the product, not a feature of it. It's what we built Dap's governance layer around. More here: https://lnkd.in/dDBWYDpC

#StartupDay at Xplora UCEMA ✅ Ignacio Cesarani and Alejandro Susmelj represented Crunchloop on September 11, talking with #founders and #builders about what they're working on and where #software fits in. Thanks to the Startup Day team for putting together a room full of people actually building things. See you at the next one. #StartupDay #Argentina 🇦🇷

I spent the weekend processing everything that happened during Rails World last week — genuinely great quality, and I enjoyed it enormously. A lot happened, from David Heinemeier Hansson's opening keynote to Aaron ❤️ Patterson's closing one. But here's the thing: I don't think the value is in debating whether any of those statements were right, wrong, or missed predictions. I think there's more value in taking that information and building our own conclusions from it. Maybe the drive behind those words mattered more than the words themselves — and maybe the fact that the topic was raised with that much conviction is more valuable than whatever position anyone actually took. I really identify with "Pencils Down" and "Look at all the things I'm not doing" from DHH. That's exactly why I've been invested in building an AI platform that works on — among other things — code generation, code review, and auto-merge. AI is already good at that, and it's only going to get better, so that's where the handoff makes sense. And this is where I agree with Aaron and Obie Fernandez too — "programming as an engineering profession is as alive as it's ever been, as it moves up an abstraction level" We'll still need programmers, we'll still need software engineers, to make the right technical, design, and architectural decisions. Everybody will be a maker now, yes. But I think this new era is the one that makes software engineers shine! Obie's tweet: https://lnkd.in/gpxqr3Dj P.S. — for the data-minded: I like to bounce my ideas against scientific numbers too, and I still believe DORA's 2025 report is pretty spot on here: "For an individual, friction doesn't vanish so much as move: it shifts from manual grind to deciding and verifying, possibly in the form of prompt iteration, result vetting, and assessing code that looks remarkably similar to correct code." (p. 40) #RailsWorld #AI