guerrilla coding

guerrilla coding comes from the root phrase guerrilla warfare, because like guerrilla warfare, guerrilla coding is swift and irregular programming that takes agile to the extreme with hit-and-run type coding of various components within a project. meaning a programmer that jumps from component to component adding their own code to make that component more efficient or completing that component more quickly, and in the mind of the guerrilla coder “better” than the programmer or programmers who were originally -ssigned to that task.

it’s when the best programmer in your group who has the ability and “creative freedom” to write any code and change any code they wish in any source code module in your team’s git or svn or other source code repository; most likely your manager and he usually feels that the project is going to slow, and therefore he takes it upon himself to speed up the development work, by writing a little bit of code here, correcting some other developer’s bugs over there, perhaps refactoring another developer’s code over there to make it perform better, or at least in their mind easier to maintain.

a manager like this is normally known to your organization as a unicorn, because he rose the ranks from developer to team or “pod” lead, to perhaps architect, eventually making it to group manager; basically, they can do it all. they are just that d-mn good, and they know it, and think they are a g.o.a.t. and they even go around saying they code guerrilla style.
my manager uses the guerrilla coding technique. i would be p-ssed off, but he usually does my job for me in half the time, and he’s just that d-mn good. plus he signs my paycheck.