Raw LLM Responses

This has been true of development for a really long time. Kind of... When developers do something over and over again. The plumbing equivalent of an application. Calling code from SQL server with ado for example. Boy does that suck To do over and over again. Then. Along comes dapper. Along comes Ruby on rails. Along comes the entity framework. And millions of other things that make it so you never have to directly connect again. We abstract away a bunch of that. We write class libraries that are reusable utilities. There used to be a lot of development that you had to do by hand, especially on the web in 2007. There wasn't even a way to do pagination easily in SQL server 2010 (if I recall correctly limit and offset being new ish). And you know what we do as developers. We make technological advances so that we don't have to do the plumbing code anymore. That same wire up code that was in every application. Obviously AI takes this to a new level. But the reality is most of the things that I use AI for today. There is a library that does exactly what I needed to do. The difference is I can just have AI write the code instead of going and finding the dll that I need from nuget/npm. Or some other package repository. It is an extension of what we've been doing forever but I do think it's going to make coding a lot harder and a lot worse because if you get a feature from a package. When they discover a bug in that package, you upgrade the package. When there is a bug in some code that an llm wrote. Well you just don't discover the bug. Unless a user reports it. And then you have to go fix it manually. So my thought is that 10 years from now we're actually going to need more Junior developers to fix the shitty bugs that are simply not worthy of a senior developer. This is how I started my career and a lot of other people I know started their careers. I think it'll come back. With the invention of llm the reusable package is going to suffer. It's so much easier to