Travis Hester

GitHub just unlocked a new level of developer workflow. Den Delimarsky walks through how GitHub Spec Kit now integrates with the brand-new Copilot CLI. Here is what stands out: ➡️ Switch between multimodal models like Cloud Sonnet 4 and GPD5 for different behaviors. ➡️ Run custom slash commands directly in the CLI to guide Copilot. ➡️ Follow a repeatable workflow: constitution, specify, clarify, plan, tasks, analyze, and implement. This walkthrough is more than a tutorial. It is a glimpse into how developers will collaborate with AI agents to rapidly build, test, and ship projects. 👉 Watch Den's full breakdown and see the live demo here: https://lnkd.in/gAgvBb9v #GitHub #Copilot #DeveloperTools #AI #Workflows

206

3 Kommentare

One of the most exciting #passkey features we've announced at Google I/O is now available as an origin trial: #WebAuthn immediate mediation. With "immediate mediation", you can build a dynamic passkey sign-in experience upon checkout, falling back to a regular form based sign-in when no passkeys are available (See the video). As a bonus, the user can sign in with a password stored to the password manager, thanks to the 9 year-old `PasswordCredential`. You can try them as an origin trial—allowlist your domain to test this new feature on your #Chrome customers. Learn more about WebAuthn immediate mediation at https://lnkd.in/gPG7vtCW

105

2 Kommentare

Since announcing my "High-Performance Node.js" workshop last week, I've received dozens of messages from enterprise developers facing the same critical challenge: "How do we identify event loop blocking in production before it becomes a crisis?" This is precisely the real-world problem separating junior developers from senior engineers. Let me share what I tell enterprise teams. The Three Warning Signs I Look For: 🚨 Response Time Spikes with Normal CPU Usage When your APIs start timing out but your servers aren't maxed out, you deal with event loop blocking. The server has capacity but can't process new requests because the event loop is stuck. 📈 Memory Growth Over Time Blocked event loops often cause promise queues to build up, creating memory leaks. Because of this single issue, I've debugged Node.js applications consuming 8GB+ RAM. Your monitoring should track memory trends, not just point-in-time usage. ⚡ Inconsistent Response Patterns Some requests complete in 50ms, while identical operations take 5+ seconds. This inconsistency is a classic indicator that something is intermittently blocking the event loop. The Real Solution Goes Beyond "Just Use Async/Await" Most developers think proper async/await usage solves everything. However, enterprise applications need comprehensive instrumentation, strategic worker thread implementation, and a deep understanding of Node.js internals. We'll tackle this in my workshop on September 29th in London. We'll debug real scenarios, implement proper monitoring, and build applications that perform consistently under production load. For enterprise teams dealing with Node.js performance challenges, this workshop bridges the gap between theoretical knowledge and production reality. 📅 September 29th | London | 4 Hours Intensive 🎯 Limited seats available Register: https://lnkd.in/d7A6wr2K What's your team's biggest Node.js performance challenge? I'd love to hear about it in the comments.

71

1 Kommentar

CODEWARRIOR: In the 90s for MacOS there was "the world's most powerful integrated development environment" with one of the coolest names and packaging. I still keep a CD-ROM version on hand knowing that although I can't use it anymore, it reminds me how much of an impact speed can make on a user experience. It was *so* much faster than the default Mac tools for writing code AND it had terrific visual design sensibility. Performance-based engineering excellence combined with emotionally resonating design excellence is truly a winning combination. Why? We all have the need ... the need for *speed*. And it's one of the ten laws of simplicity :-). --JM --- Ref: The 10 Laws of Simplicity https://lnkd.in/g29uNddd

72

11 Kommentare

The snapshot command in DDEV lets you save your database state and restore it later. Think of it as a checkpoint system for your development environment. Here's how to use it: - Create a snapshot: "ddev snapshot --name=snapshot_name" - List your snapshots: "ddev snapshot --list" - Restore a snapshot: "ddev snapshot restore snapshot_name" - Restore latest snapshot: "ddev snapshot restore" I use this constantly during live streams and tutorials. Set up your site exactly how you want it, take a snapshot, then experiment freely. When things break, just restore back to your clean state. #ddev ~~~ If you found this post helpful. ♻️ Please repost and follow.

52

5 Kommentare

Blogged: Publishing NuGet packages from GitHub Actions the easy way with Trusted Publishing https://lnkd.in/emFPg-nV In this post I describe how you can use nuget's new Trusted Publishing feature to publish NuGet packages from a GitHub Actions workflow #dotnet #NuGet #GitHub

29

1 Kommentar