> maybe the author has simply not worked with people who are good at refactoring
I agree with you 100% but this line got me thinking... shouldn't a methodology/process in principle lower the skill level required to be effective? I understand that Agile does to an extent, but perhaps the fact that "refactoring" is hard means the process has shortcomings?
That's one possible purpose to a process. Another is to increase reliability e.g. get the same outcome every time. Like 'complete on time'. Anybody can benefit from that, even the most senior of developers.
I agree with you 100% but this line got me thinking... shouldn't a methodology/process in principle lower the skill level required to be effective? I understand that Agile does to an extent, but perhaps the fact that "refactoring" is hard means the process has shortcomings?