Eric Potter

"It’s only NPE (non-prod environment), so it’s not urgent. I’ll look at it when I can." As a software developer, NPE is our production. Every new feature, bug fix, and business-critical change starts in non-prod. If NPEs are broken or unreliable, work gets delayed, timelines slip, and ultimately production does get impacted, just indirectly. So next time someone flags an issue in NPE, please consider this: Fixing NPE issues quickly keeps delivery moving and ensures production stays healthy.

19

2 Comments

Watching a well-known developer tooling company publicly reckon with its business model this week made something very clear to me. Many organizations don’t realize how much revenue quietly depends on users landing on specific parts of their website. * A product Q&A section that influences a few percent of conversions. * A fitment or compatibility tool that reduces purchase hesitation. * A buying guide that nudges the decision. * A blog post that introduces the product before the user ever sees a PDP. None of these are usually mission-critical on their own. They’re often written off as “only” one or two percent. But they all share something important: they only work if the user reaches the page. And combined they likely represent a percentage of revenue you can't ignore. AI is increasingly answering those same questions before a customer ever sees your Q&A, your guide, your calculator, or your content. The demand for this information won't change, but the access and path will. Developers may be encountering this first, but they won’t be the last. Over the next 12–24 months, the organizations that fare better will be the ones that understand exactly where this dependency exists and what replaces it when the click goes away.

4

Where does #a11y fit in your tech stack? Accessibility is infrastructure. Period. I’ve spent years building and auditing systems against Section 508 and WCAG. The biggest problem I see isn’t technical, it’s organizational. Teams treat accessibility like remediation instead of what it is: a core architectural concern on the same level as security and performance. Over 96% of the top million homepages have detectable WCAG 2 failures. We have the specs. We have the tools. What we don’t have is engineering leadership culture that treats a contrast ratio violation with the same seriousness as a broken API endpoint. And y’all, the regulatory landscape is catching up. April 24, 2026: DOJ’s Title II rule mandates WCAG 2.1 AA for public entities serving 50K+ populations. Private sector isn’t exempt, WCAG 2.1 AA is now the de facto standard in Title III litigation, up 102%. And you’re legally responsible even when using third-party platforms. That vendor VPAT does not equal a compliance strategy. What I’ve learned shipping accessible systems at scale: 1. Shift left, hard. Accessibility belongs in your component library, design tokens, and PR checklists. This should be as non-negotiable as type safety for your codebase. 2. Automate the floor, not the ceiling. Automated tools alone can’t catch everything, you need both automated and manual assessment. We don’t ship apps without auth. Stop shipping digital product without accessibility. #a11y #WCAG #Section508

6

1 Comment

"Angular is becoming Razor Pages." That’s what my teammate told me today. He was referencing Angular’s new @if control flow syntax and jokingly predicted the death of *ngIf by Angular 21. He ended his argument with the classic hot take: "Dotnet >>> Angular." I had to remind him why we chose Angular for our frontend. While the syntax might look familiarly chaotic to backend developers right now, the behavior is strictly next-gen frontend architecture. We aren't dealing with server-side rendering that requires a clunky full page reload every time a user submits a form. Angular provides an ecosystem that delivers a seamless feel that older backend technologies struggled to achieve on their own: ✅ True SPA Experience: No flickering reloads. The app feels native and fluid. ✅ Signals & Zoneless: We are rapidly moving toward a world where change detection is surgical and incredibly performant. ✅ Enterprise Dependency Injection: A structured way to manage code that other frameworks are still trying to bolt on via third-party libraries. ✅ Deferrable Views: The built-in ability to prioritize exactly what loads when (@defer) is a massive win for Core Web Vitals. We can borrow helpful syntax ideas from the backend, but the User Experience is pure frontend magic. ✨ Are you Team Angular or Team .NET for modern web apps? #Angular #WebDevelopment #RazorPages #UI #SoftwareEngineering #DotNet #Frontend #TechDebate #JavaScript #TypeScript

36

5 Comments

AI needs to be understood as accelerator, not a replacement. Software ecosystems are complex enough and require thoughtful planning and execution to keep things running for our business partners. We solve problems for the business, not create more.

2

🚨 New from Follett Software: IT Asset Manager is here, and it's built for K-12. 📱 Track devices 📦 Reduce loss ⏱ Save time on tracking and audits Read the news: https://ow.ly/ko4u50XVRXi

16

1 Comment