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 assigned 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 damn 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 pissed off, but he usually does my job for me in half the time, and he's just that damn good. Plus he signs my paycheck.

Guerrilla Coding by SrcMaker October 4, 2017

Guerrilla Coding 

Also known as Guerrilla Programming or Guerrilla Development, this technique of coding is employed by only the best. Their hiring manager and the higher ups that don't know shit about programming definitely think these dudes are "Unicorns" and they love that these guys can code, design do Visios and PowerPoints and present them at Keynotes and other engagements, especially around tech savvy clients or at least clients who think they are tech savvy but again probably don't know shit.

Common characteristics a Guerrilla Coder (Unicorns):

1. They have near 20 years experience in the business, but probably have been programming since 7, brining up their experience to well over the three decade mark. A programmer like this with 35 years coding experience has seen and done it all.

2. They have balls. They take risks that other programmers on their team would never do. And people respect them for that.

3. They are pretty arrogant, but have the skills and experience and reputation and balls to back it up. So they don’t really care if they are stepping on other developer’s toes. Again Balls and Respect.

4. Sometimes they break the built. But on one else on the team has the balls to tell them shit.

5. They love the saying “I don’t always test my code, but when I do I do it in production.” Somehow they get away with not thoroughly testing their code like the other developers, but that’s because somehow it almost always works.

My Guerrilla Coding Manager broke the fucking build again, but somehow he fixed it in 5 minutes. Fucking Guy is nuts but somehow always gets our team across the finish line.

Guerrilla Coding by H.I.A. Saint October 5, 2017