Hacker News Reader

One week to both refactor a big code base and also make sure everything works as expected? Not the estimate I would expect from a senior analyst, too optimistic. Fine that you fix the regressions for free, but the last thing I want is a one-week refractory going to production and fire fighting later.

View on HN

I have 15+ years of experience in software development. The hardest thing I had to learn recently is that paring with AI changes the definition of "what is hard". You can decomposit a refactor into a steps of two kinds:

1. Conceptually hard, which you have to really think about and write code by hand for AI to follow,

2. Time consuming that follows patterns.

Then you do 1. review with AI what are implications on the codebase. Next you crate list of task for 2. and keep reviewing outcomes.

This does still not include any QA. The fact that A.I. tells you the implications of your changes does not take away the effort and time you need to verify the correctness end to end

Reply on news.ycombinator.com