The Rise of CoderSight by Claude AI

Before AI

When I started software development in 2016, everything in this field was different. It may not seem like many years ago, but the impact of the changes since then has been enormous. Learning was not as easy as it is today. Finding answers to questions took much longer, and debugging issues was a far more time-consuming process for developers.

Despite companies providing documentation for their packages and features, the greatest hope for any developer searching for the right solution was stackoverflow.com — a remarkable community of developers from around the world, united on a single platform with one goal: to ask and answer questions. But that platform seems to be used less than before.

The New Reality

Today, I have the privilege of using Claude, one of the most capable AI platforms available, as a coding agent. For me as a junior developer back in 2016, an AI coding agent would have been something truly incomprehensible. So, I began using it in a particular way: I would describe everything about my idea and let it build things step by step. During each step, I observed that while AI is capable of handling many tasks, it still requires human perception and analysis to transform an idea into something real and lasting. It tends to approach tasks in the simplest way possible, without always considering long-term maintainability. Nevertheless, the outcome of this experiment was the CoderSight web application— a project coded by AI which is a CMS based platform. The code may not be the finest of its kind, but it demonstrates something important: AI is powerful, yet deeply dependent on the software developer who understands the business, the principles of software development, and the right solution for each problem.

Think of it as a revolution in the learning curve. Software can now be designed faster than ever before, and every developer can learn new things and resolve unfamiliar issues more effectively than in the past. The pace has accelerated dramatically. I've witnessed the evolution of .NET through various frameworks over these years, and Blazor stands out as the one I appreciate most — it made frontend development possible within the .NET ecosystem, which is why I chose to build this website with it. This experience caused me to learn many more details about Blazor.

Claude Code: A Practical Experience

Working with Claude Code has given me a clearer picture of both its capabilities and its blind spots.

Strength: It excels at investigation. When bugs or issues arise, it does a solid job of analyzing the environment, tracing the problem to its root, and proposing targeted fixes. Also, it fastens the development if you give it a completely clear idea and its details to be implemented.

Weakness: Its design instincts can let it down. When I was implementing a blog post notification system for subscribers, it generated a foreach loop that sent notifications to all subscribers synchronously — on the same thread as the publishing process itself. It was a poor design decision that would have caused real problems under any meaningful load. Also, it usually tries to be a what I call it a designer of the moment who does not think about the future of the app itself and the codes are not so clean. This is the kind of gap where developer judgment remains essential.