Tony Guntharp

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Comment

Every engineering leader says they care about velocity. But velocity doesn’t die in the IDE. It dies in: Review queues Approval loops Dependencies across 3 other teams The fastest teams don’t code faster. They unblock faster.

1

Custom Apigee developer portals work. Until you have to keep evolving them. Auth changes. Docs drift. New APIs appear. Ownership never really goes away. Launchpad is a managed developer portal for teams that want stability without constant rebuilds.

1

Learn what Playwright is, why teams use it, how it compares with other E2E tools, and how to scale tests with parallel execution.

2

Here's an example of an advanced meeting note processor prompt that uses TextExpander's JavaScript capabilities to automatically insert metadata like the meeting date and attendee list.

6

When a workflow hits a snag, the entire run shouldn’t fall apart. 🛑 Automatic retries, graceful error handling, and smarter skipping give your workflows the resilience they need to keep moving, reduce breakages, and save your team from unnecessary rework. These upgrades help IT teams build smarter, steadier workflows that keep moving without constant supervision. Swipe to see them 👉 . . #ITWorkflows #AIAutomation #AIWorkflows #AI #IT #WorkflowAutomation #Atomicwork

23

3 Comments

Kubernetes is powerful. But YAML? Not so much. Here’s Harpoon in 60 seconds: No steep learning curve No YAML No security gaps Just drag, drop & deploy Visit the site & try free demo.

4

If you want your DevOps workflow to feel lighter and faster. This video is for you. In this episode, SAHIL VANDRA, Senior DevOps Engineer I, walks through how he uses GitHub to simplify two major parts of his workflow: - Automated code reviews - Smarter CI/CD pipelines He breaks down how AI helps reduce manual effort, speed up releases, and maintain steady deployments without compromising on quality. If you’re looking for practical ways to bring AI into your DevOps routine, this breakdown gives you a clear, real-world look at what actually works.   Watch the full video here: https://lnkd.in/d3zYaxgb #devops #aidevops #mlops #github #automation

26

Parallel’s best-in-class Search & Extract tools are now available in the Vercel AI SDK. Use them in your AI projects to retrieve high-quality context from across the open web, or on specific pages you define. Find everything you need to get started in the comments below.

40

2 Comments

📣 Today we’re announcing new features for Jellyfish AI Impact that bring together system data, developer sentiment, and guided insights - giving leaders a clearer, faster, and more complete picture of how AI is transforming their organizations and the overall SDLC. As AI becomes embedded in every corner of software development, engineering leaders face a new challenge: proving that these tools actually deliver value. From autonomous agents to code assistants, the landscape is evolving faster than most teams can measure. Keep up with the AI evolution with Jellyfish AI Impact: https://lnkd.in/g7t3wx5h

45

1 Comment

Custom software is not a feature upgrade. It is an operating decision. When software is built around your workflows, three things change: • Scale stops being constrained by tools • Security becomes architectural, not reactive • ROI compounds instead of leaking through licenses Off-the-shelf products optimize for averages. Custom software optimizes for you. Hiteshi builds systems aligned to business logic, not templates. #CustomSoftware #EnterpriseTech #DigitalTransformation #Hiteshi

12

Don’t dismiss vibe-coding as the "bad" opposite of production-grade software. Both are valid responses to their operating context. They just sit at different points on the same optimization gradient. The real gap in the discourse is the absence of clear graduation thresholds. The moments where the cost of not adding “serious” software attributes flips from acceptable to risky. That tension is structural: -Vibe-coding optimizes for speed and fit under constrained responsibility -Traditional engineering optimizes for resilience and scale under diffuse responsibility Vibe-coded tools feel threatening to experienced engineers because it compresses the distance between intent and outcome, makes scaffolding optional, and de-emphasizes ritual and process. That reaction is understandable. The tension emerges when expectations on the software quietly change, but the operating model does not. Introducing a Vibe-to-Product Gradient framework: 1️⃣ Personal / Situational Utility “If this breaks, I shrug.” Where vibe-coding thrives: -Single user or small trusted group -Built for speed and local need -Manual fixes are acceptable -No external commitments Signals you’re here: -Inline logic, minimal scaffolding -Little to no logging -Security by access, not design -Zero-infra thinking Signals you’ve graduated: -Someone else depends on it -Usage becomes routine -"Can we rely on this?" appears 2️⃣ Shared Operational Tool “If this breaks, someone Slacks me.” ⚠️ The first real, and most commonly missed, threshold. This is also where invisible work creeps in. Signals you’re here: -Multiple users rely on it -Workflows get blocked when it fails -Fixes feel "small", but user interruptions aren’t New expectations: -Predictable failure modes -Basic logging -Backups or recovery -Clear ownership Signals you’ve graduated: -Exec visibility -External stakeholders -"This can’t go down" appears 3️⃣ Business-Critical Capability "If this breaks, we miss money, reputation, or commitments". The danger zone for vibe-coded tools - because obligations have changed. This is when engineers get twitchy, and ownership should be transferred explicitly. Signals you’re here: -Financial or compliance impact -Informal on-call expectations -Trust is assumed, not optional New expectations: -Observability (logs, metrics, alerts) -Security and auditability -Change control -Explicit ownership and SLAs Signals you’ve graduated: -Multiple teams -Contractual guarantees 4️⃣ Platform / COTS-Equivalent “If this breaks, we’re on the hook.” At this point, you’re either: -Rebuilding half a SaaS platform internally, or -Paying someone else externally to absorb years of operational, legal, and organizational entropy. This is where COTS earns its keep - through liability transfer, not features. Key Takeaway: Don’t dismiss vibe-coded software as "not production-grade". The real risk to manage is when expectations keep graduating, but the tooling - and operating model behind it - doesn't.

6

We have made improvements to our agent workflow specifically tuning it for even better performance when used with SoTA models like VEO3 and Kling2.5. Check out this one-shot Supabase DB infotainment. { "input": { "prompt": "Cloudpunk themed CS/Tech tutorial on the topic – “The Magic Link Journey” – explaining how Supabase’s magic link login works, visualized as a secure portal adventure.", "video_model": "KLINGIMGTOVIDTURBO", "image_model": "SEEDREAM", "tone": "grounded", "duration": 60 } } GPT 5 High inference.

1

In this new video tutorial, Global Payment's Senior Software Developer Tony Smedal covers the complete configuration process including: 🔵 Extension activation 🔵 API key integration 🔵 Test transaction setup 🔵 Production deployment. This tutorial skips the installation basics and jumps straight into the configuration workflow (perfect for devs who need to get payment processing live quickly). Whether working on client sites or internal projects, this video covers the core setup process from development to go-live: https://bit.ly/3Gp9VgO

5

Discover the best practices for structuring React projects in 2024. Learn how modular components, Vertical Slice Architecture, and centralized state

1

Highguard, the newly launched multiplayer shooter from Wildlight Entertainment, is facing significant changes just weeks after its debut. In a surprising move, the developer has laid off a majority of its staff, a decision shared by former team members on LinkedIn. Wildlight's response to the layoffs indicated a shift in focus, retaining a core group to continue supporting and innovating on the game. This reshuffling raises questions about the sustainability of new gaming titles in a competitive market. The gaming industry has seen a surge in players, yet many new titles struggle to maintain a workforce capable of ongoing development and improvement. This situation is increasingly prevalent as studios grapple with the complexities of workforce management and project viability. As businesses within the tech and gaming sectors evaluate their trajectories, the fate of Highguard may serve as a cautionary tale about the pressures facing emerging developers and the importance of strategic planning in a rapidly evolving landscape. For more insights, read the full story at The Verge: [Highguard's developer reportedly lays off ‘most’ of its staff just over two weeks after launch](https://lnkd.in/e7VYJeEb). #GamingIndustry #TechNews #WildlightEntertainment #Highguard #GameDevelopment

2