Coding With David

  Artificial intelligence has already begun transforming how software is built. Tools like AI coding assistants, autonomous agents, and AI-driven development environments can now generate working implementations in minutes. Tasks that once took hours—or days—can often be completed in a single interaction with an AI model. This rapid acceleration raises an inevitable question for the industry: How long will it take before software engineering becomes fully autonomous? The answer is not a single breakthrough moment. Autonomous engineering will emerge gradually in stages , each one shifting more responsibility from humans to machines while redefining the role of software engineers. Understanding these stages helps organizations prepare for the changes already underway. The Four Stages of AI-Driven Software Engineering Stage 1: AI-Assisted Engineering (Today – ~2027) This is where most teams operate today. Developers use AI tools to accelerate their workflow, b...

  As developers, we're constantly building, fixing, and scaling. It’s easy to get lost in the weeds of lines of code and specific features. We can get so focused on a single function or a single database query that we lose sight of the bigger picture. That’s where systems thinking comes in. It's a game-changer. It’s not just a fancy concept from management books; it's a practical, powerful approach that can fundamentally change how you design, build, and maintain software. What is Systems Thinking? In simple terms, systems thinking is a way of understanding how things are connected. It's about looking at the big picture and recognizing that your application isn't just a collection of code snippets. It’s a dynamic system with interconnected parts, each affecting the other. Think of it like a human body. Your heart doesn’t just beat; it pumps blood to your organs, which process it, which then affects your energy levels, and so on. Software works the same way. ...

  When starting to build forms in Blazor, it's common to immediately reach for a third-party component library. Date pickers, masked inputs, sliders, validation UI, file upload widgets – the list goes on. While these libraries can be incredibly useful, they also come with tradeoffs: extra dependencies, styling constraints, larger downloads, and the need to learn a new component API that often duplicates what browsers already do well. This post serves as a powerful reminder that modern HTML inputs are already "power controls." With Blazor, you can wire them up with minimal C# code while retaining all the benefits of native browser behavior. The result? Simple, fast, dependency-free UI that still feels modern and responsive. The Core Idea: Let the Browser Do the Work This approach demonstrates a wide range of input types using plain HTML, leveraging the browser's native capabilities: type="email" for native email validation type="ur...