
1 month
tbf high prevalence is a double edged sword, it also means it’s trained on a lot of poorly written code which it will slide into

tbf high prevalence is a double edged sword, it also means it’s trained on a lot of poorly written code which it will slide into

Your way of thinking of constants and naming seems a bit “worst case” thinking?
And if it were to grow I would probably look into making a FlatFileParser which then encapsulated the constants, if you need to access the mostly random indexes outside of parsing I question why?
An enum could be a partial answer inside of this parser if it then keeps getting more and more correlated constants

This is just having constants like
final int FLATFILE_DATE_INDEX = 2
with more steps and boilerplate?
It took the llm 11 days to generate the code
It doesn’t seem to say anywhere anyone reviewed it in any time