It want solved. There was some generic boilerplate that was added to IDEs but it wouldn't be project specific. It wasn't able to look at patterns within your own codebase and repeat them.
>and the latter was a requirement of being a decent engineer.
Most software projects are too big to fit in one engineers head. Having AI be able to research what the relevant code is, how it works, what race conditions exist, what pitfalls or other things you may run into saves a lot of time in regards to planning.
> It want solved. There was some generic boilerplate that was added to IDEs but it wouldn't be project specific. It wasn't able to look at patterns within your own codebase and repeat them.
I left out some expository, apologies. For example, I rely pretty heavily on using VSA as a way to keep things self contained and thus created templates for each different functionality type (background worker, crud action, etc) where they already have the logging/database connection/code flow pattern, I just need to shove in whatever business logic is needed. Now, that logic is the hard part and would require me to explain it in excruciating detail to Claude, or write it out by hand, but it take the same amount of time either way.
It want solved. There was some generic boilerplate that was added to IDEs but it wouldn't be project specific. It wasn't able to look at patterns within your own codebase and repeat them.
>and the latter was a requirement of being a decent engineer.
Most software projects are too big to fit in one engineers head. Having AI be able to research what the relevant code is, how it works, what race conditions exist, what pitfalls or other things you may run into saves a lot of time in regards to planning.