"Involve junior developers in architecture reviews. They will help you to identify the mentally demanding areas."
#softwareengineering #developerexperience #teaming #pairing #architecture #productivity
We talk a lot about speed, automation, and AI-assisted development.
But maybe the real question is simpler: does mastery still matter?
After writing 250+ AI-assisted blog posts, I’ve learned that mastery didn’t disappear—it just moved.
It’s not about knowing every API anymore. It’s about judgment, taste, and seeing the claw—the human trace behind the machine output.
Read the full reflection on The Main Thread:
https://www.the-main-thread.com/p/does-mastery-still-matter-ai-java-developers
via @dotnet : Introducing Custom Agents for .NET Developers: C# Expert & WinForms Expert
https://ift.tt/YlwBdCO
#DotNet #CSharp #WinForms #Copilot #CustomAgents #SoftwareDevelopment #Programming #DevTools #Automation #DeveloperExperience #GitHub #Coding #TechInn…
Today felt like my own “Mother of All Demos.”
I took an 8-point #Jira ticket, dropped the description into #GitHubCopilot, and—because #Copilot is trained on our codebase—delivered a working solution in 25 minutes.
Copilot didn’t just write code; it helped refine instructions as it learned more about our architecture. Everything's inside a reusable dev container w/ onboarding docs, so anyone on the team can replicate.
Even the #Emacs guy is thinking about switching.
"It's crazy how 3 years into the AI revolution a non-technical investor will make predictions based on the fact that 'AI writes all the code now.' It's not a 'what if' or a 'maybe' or even a 'when' in their mind – they think it's our current reality."
via @dotnet : Announcing .NET 10 Release Candidate 2
https://ift.tt/q1RaZrO
#DotNet10 #ReleaseCandidate2 #DotNet #VisualStudio2026 #CSharpDevKit #DotNetMAUI #EntityFrameworkCore #CrossPlatform #DeveloperExperience #GitHubDiscussions #QualityImprovements #GoLiveS…
Developers: Would you take a 20% pay cut to work with a significantly better tech stack?
#GitHub introduces a new embedding model for Copilot - now in #VSCode!
The upgraded model improves how Copilot understands programming context, retrieves relevant code, and generates smarter completions.
Key improvements:
• 37.6% better retrieval quality
• 2× faster throughput
• 8× less memory used for code indexing
Learn more: https://bit.ly/46MJrQO
Enhance the Spring Boot developer experience with Arconia Dev Services: zero-code and zero-config infrastructure provisioning. Add one dependency. That's it!
Databases, event queues, observability platforms, AI services and more. All powered by Testcontainers!
#Java #SpringBoot #Arconia #Testcontainers #DeveloperExperience
https://www.thomasvitale.com/arconia-dev-services-spring-boot/
The Farmer Was Replaced: Code a Farm, Now Available for Under $5
#automation #DeveloperExperience #fun #programming #requirements
https://blazetrends.com/the-farmer-was-replaced-code-a-farm-now-available-for-under-5/?fsp_sid=144195
The story of Vite:
https://www.youtube.com/watch?v=bmWQqAKLgT4
See more: https://vite.dev
Guess what? I’ve made a switch to Vite this week. I’ve moved a React application from CRA (Create React App) to Vite. It’s been an exciting journey
#React #Vite #Migration #JavaScript
#Developer #DeveloperExperience
What's the technical hill you're willing to die on? What principle do you refuse to compromise?
JUnit 6 broke 50 repos. I’m delighted.
If a dependency bump can shatter your stack, you don't need fewer updates. You need better tests.
I maintain 50+ OSS repos as one human. I don't babysit them. I automated everything, including updates and minor releases. Many repos haven't been touched in 6 years. AS now JUnit 6 rolled in, a chunk failed. Perfect.
Why perfect? Because failure is a signal, not a disaster. Good tests mean breakage never escapes. I've had repos fail on a Java date parser change. Beautiful. I saw it before release, fixed it, moved on. During Log4Shell and Spring4Shell I didn't panic. I just waited for the next update. That's what behaviour tests are for. And no, they are not slow. If your tests crawl, your design does too.
I trust code I write. I do not trust magic. I remove convenience glue that silently rots:
I don't need MultiValueMap when Map<List> is clearer.
I don't need StringUtils.isEmpty when a simple null or empty check is obvious.
I don't need annotations that smuggle in half a framework.
Every extra library is a future liability: CVEs, Licences, Security, Data Privacy, Performance, breaking changes, mental overhead. Use them to start, then delete them to last. Fewer moving parts mean fewer ways to die.
After 6 years my micro systems still boot in micro seconds, still read clean, still behave. CI pipelines aged, sure, but the code stayed boring. Boring is freedom. Quiet, peaceful, done.
If your stack cannot auto-update without heart palpitations, the problem isn't updates. It's architecture.
Principles I ship by
Automate updates and everything else I can. Let tests be the gate, not fear.
Push behaviour tests to the edges. If it's slow, refactor until it isn't.
Prefer primitives and standard libs. Delete decorative wrappers.
Design for micro systems, not micro monoliths. Start fast, stay fast.
Fewer tools, fewer surprises, fewer nights on fire.
Congratulations. The system failed safely. After fix, you may proceed to do literally anything else with your life.
GitHub Copilot CLI is now in public preview — bring AI-powered coding directly to your terminal.
No context switching. Full GitHub integration. Explicit control over every command.
https://dropletdrift.com/github-launches-copilot-cli-for-public-preview/
Just deployed my Astro site on DigitalOcean!
Static builds fly on App Platform’s CDN, and SSR works cleanly with the Node adapter. Modern stack, smooth DX, and global performance in minutes.
https://dropletdrift.com/how-to-deploy-an-astro-application-on-digitalocean/
Let me be blunt here: you can't multitask. Neither can I. Nobody can.
What we call multitasking is really just context switching really fast, and every switch has a cost. It's like running too many applications on a computer with insufficient RAM - everything runs slower because the system keeps swapping things in and out of memory.
"A rule is only meaningful in a specific flow. When you abstract it too early, you lose that meaning and invite bugs the moment someone 'reuses' it in a place it doesn't belong."
#softwareengineering #developerexperience #objectorientedprogramming #code #reuse #functionalprogramming
https://ricofritzsche.me/objects-are-dead-long-live-feature-slices/
#Pinterest launched 𝐏𝐢𝐧𝐂𝐨𝐧𝐬𝐨𝐥𝐞 - a unified #InternalDeveloperPlatform (IDP) that centralizes engineering workflows.
By bringing together deployment, monitoring & service management, PinConsole gives engineers a 𝐜𝐨𝐧𝐬𝐢𝐬𝐭𝐞𝐧𝐭 𝐥𝐚𝐲𝐞𝐫 to focus on business logic, not infrastructure complexity.
Dive into the details on #InfoQ https://bit.ly/4n9rLEF
Local PostgreSQL setup killing your dev flow?
Quarkus Dev Services spins up DBs automatically for tests and dev mode.
No more manual YAML. Just code → test → repeat.
#SpringBoot #Quarkus #DevServices #DeveloperExperience #CloudNative
Don’t start from scratch.
Quarkus supports your Spring annotations — @Controller, @Service, @Repository.
Migrate your app module-by-module and go cloud-native without breaking everything.
#SpringBoot #Quarkus #DeveloperExperience #JavaMigration #ModernJava
