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.
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.
by H.I.A. Saint October 5, 2017
Get the Guerrilla Codingmug. In some High Schools in PG County Maryland Code 4 means a fight when the admin and security team hears that they start running
by Lowkeyyearlie December 10, 2019
Get the Code 4mug. by dm83737 May 5, 2007
Get the aped the codemug. by thatbitchinthecorner December 28, 2019
Get the Dress Codemug. Writing Software in your Production Environment where a mistake can end career(s) and possibly lives.
Ken: John, we don't have a development environment to write code in.
John: Can we safely do it in Production?
Ken: Not a chance in hell
John: Sounds like we have some hot bareback coding ahead of us!
John: Can we safely do it in Production?
Ken: Not a chance in hell
John: Sounds like we have some hot bareback coding ahead of us!
by mcdoh! March 18, 2011
Get the Bareback Codingmug. (noun): A verbal agreement between people that allows secrecy Vegas style, where "what happens in Vegas, stays in Vegas", and allows those involved to play things off as if nothing ever happened.
by NiggaCracker February 4, 2012
Get the Vegas Codemug.