> So if you're banging out the same type of thing over and over again, yes, they will make that work light and then scarce. The same thing over and over again

> So if you're banging out the same type of thing over and over again, yes, they will make that work light and then scarce. The same thing over and over again should be a SaaS, some internal tool, or a plugin. Computers are good at doing the same thing over and over again and that's what we've been using them for > But if you need to create something niche, something one-off, something new, they'll slip off the bleeding edge into the comfortable valley of the familiar at every step. Even if the high level description of a task may be similar to another, there's always something different in the implementation. A sports car and a sedan have roughly the same components, but they're not engineered the same. > We used to worry about pointers and memory allocation. Some still do. It's not in every case you will have a system that handle allocations and a garbage collector. And even in those, you will see memory leaks. > Now we will worry less and less about how the code is written and more about the result it built. Wasn't that Dreamweaver?