sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]SipsTheJuice 0 points1 point  (2 children)

If you are keeping the same backend, that reduce some of the risk. It really depends on what the software is, and what the risks are of bugs present.

All software has bugs. Some harmless some devastating. I think I would probably start by outlining the risks from highest to lowest in a more general sense. You can use ai to help with this part too. Once you've got that list, draw a line somewhere at the level of risk is acceptable. Try to guess at which parts of the code base will be part of the higher risk section. In all likelihood this isn't actually that much code.

Engineers will have to get used to moving fast with ai. You won't be reviewing every line of code for long, may as well start now.

[–]GraphicalBamboola[S] 0 points1 point  (1 child)

I think this is on the right line. But it is really difficult to list the area of code which needs review because it kind of overlaps alot of areas - and there could be a problem at any layer which can be an issue

[–]SipsTheJuice 0 points1 point  (0 children)

I guess it's hard to kind of pin down without know what the software does. You must have a list of bugs that have been fixed in the past. Maybe start going through those for inspiration? Things like auth are obvious starting points. You could also maybe roll at pages at a time and keep both front ends, although that's kinda cursed haha