Jeff Auston

💡 AI doesn’t just change how code is written – it changes expectations and outcomes. In the final section of Jellyfish’s AI Adoption Guide, we explore how expectations for engineering leaders are evolving as AI becomes embedded across the SDLC. Because the organizations pulling ahead are treating AI as a transformation, not a tooling upgrade. Inside, you’ll explore: - Why AI adoption is quickly becoming a leadership mandate, not an option - How to balance ambitious goals with realistic expectations - What cultural investments are required to sustain long-term gains - How data can be used to align executives and engineering teams The teams that win in the AI era won’t just have better tools – they’ll have leaders who know how to guide change. Download today: https://lnkd.in/dut_6WpQ

20

We’re excited to partner with Cognition, the stellar crew behind Devin 🤖 and Windsurf 🌊, to make SWE agents more effective. Here’s the workflow: ✨ CoreStory extracts the hidden business logic, requirements, and complex behaviors in legacy codebases into a persistent spec. ⚡ You pass that spec as context and tasks to Devin, Cognition's Autonomous AI Software Engineer. 🚀 With the spec to navigate, the AI agent gets more powerful. It can modernize entire systems, or use the spec to field even more tickets with higher confidence. This is what the future of software engineering looks like: Human devs + AI agents, working side by side, with CoreStory fueling the spec. #AI #Agents #SpecDrivenDevelopment #LegacyModernization #CoreStory #Cognition

17

Scaling your startup on AWS without burning through your budget? Sounds like a dream, but AWS actually hands out credits and runs programs that can save you serious cash - if you know how to grab them. This guide breaks down how startups can tap into the AWS accelerator, snag free credits, and turbocharge growth without sweating over the cloud bill. Spoiler: it’s less complicated than you think, and skipping this means leaving money on the table. #AWS #Startups #CloudComputing #TechGrowth #Entrepreneurship

2

When engineering leaders walk into PE board conversations armed with roadmaps, sprint velocity, and feature delivery timelines, that preparation isn't wrong. It's just incomplete. Boards care about product delivery — but not the way you think. They're not evaluating whether your team ships fast. They're evaluating whether what you're shipping is the right bet, and whether you can defend that in business terms. To a PE board, a roadmap isn't a delivery plan. It's a capital allocation document. Every feature represents a choice — why this, why now, and what are we giving up to build it? Four questions running in the background of every board conversation: 1️⃣ Is this roadmap connected to revenue and retention, or is it floating? Feature velocity means nothing if it isn't tied to business outcomes. 2️⃣ Can you tell me what you're not building, and why? The ability to defend trade-offs signals strategic judgment that a feature list never will. 3️⃣ What's underneath the roadmap? Tech debt, compliance gaps, scalability ceilings — boards want to know you see it and have a plan. Leaders who surface this proactively earn credibility. The ones who don't tend to have it surface at the worst possible moment. 4️⃣ What breaks if we push for more growth? PE firms are in the business of pushing. They want to know you've already stress-tested against that scenario. The language problem: Consider the difference between these two updates: "We shipped fourteen features last quarter and hit 94% of delivery commitments." "We prioritized two initiatives tied directly to enterprise retention over three others further from the revenue line. Churn in that segment is down 8%." Same team. Same quarter. Completely different signal. PE boards aren't anti-roadmap. They're anti-roadmap-as-religion. Stop trying to impress them with what you built and start being genuinely useful about why you built it, what you chose not to build, and what it'll take to keep building at scale. Those are different goals. They require different preparation. What's been your experience translating engineering strategy for board-level conversations? Curious what's landed well and what hasn't.

14

1 Comment

Tired of long CI builds and rising compute costs? Coda was too. They trialed Aspect Workflows, saw a 10x improvement in build times and a 67% reduction in compute costs, and decided to roll it out more broadly. "We went from having significant limits in CI and tools to where the limits are now just due to our code." — Neal Norwitz, Software Engineer at Coda Read more about the challenges they faced and the results they saw: https://lnkd.in/eA_pwcDQ

5

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