| ▲ | lelanthran 17 hours ago |
| This is a very one-sided article, unashamedly so. Where's the references to the decline in quality and embarrassing outages for Amazon, Microsoft, etc? |
|
| ▲ | dboreham 17 hours ago | parent | next [-] |
| Everything you read is in service of someone's business model. |
| |
|
| ▲ | esafak 17 hours ago | parent | prev [-] |
| Do we know that it decreased the quality, or introduced more opportunities for bugs by simply increasing the velocity? If every commit has a fixed probability of having a bug, you'll run into more bugs in a week by going faster. |
| |
| ▲ | lelanthran 7 hours ago | parent | next [-] | | > Do we know that it decreased the quality, or introduced more opportunities for bugs by simply increasing the velocity? That's an easy question to answer - you can look at outages per feature released. You may be instead looking at outages per loc written. | | | |
| ▲ | leptons 6 hours ago | parent | prev | next [-] | | AI is constantly trying to introduce bugs into my code. I've started disabling it when I know exactly where I'm going with the code, because the AI is often a lot more confused than I am about where the code is going. | |
| ▲ | pydry 17 hours ago | parent | prev [-] | | Do we know it increased the velocity and didnt just churn more slop? Even before AI the limiting factor on all of the teams I ever worked on was bad decisions, not how much time it took to write code. There seem to be more of those these days. |
|
