The eXtreme Go Horse (XGH) Process

eXtreme Go Horse original design documentation
It turns out it seems XGH is not as well known as it should be. A good friend pointed me to a readily available translation of its core process principles, which you can find in here

But reading a txt in Github is not the most pleasant thing so here’s a mirror with a modicum of formatting


Original source:

And the updated version:

1. I think therefore it’s not XGH.
In XGH you don’t think, you do the first thing that comes to your mind. There’s not a second option as the first one is faster.

2. There are 3 ways of solving a problem: the right way, the wrong way and the XGH way which is exactly like the wrong way but faster.
XGH is faster than any development process you know (see Axiom 14).

3. You’ll always need to do more and more XGH.
For every solved problem using XGH 7 more are created. And all of them will be solved using XGH. Therefore XGH tends to the infinite.

4. XGH is completely reactive.
Errors only come into existence when they are perceived.

5. In XGH anything goes.
It solves the problem? It compiled? You commit and don’t think about it anymore.

6. You commit always before updating.
If things go wrong your part will always be correct… and your colleagues will be the ones dealing with the problems.

7. XGH don’t have schedules.
Schedules given to you are inconsequential. You will ALWAYS be able to implement EVERYTHING in time (even if that means accessing the DB through some crazy script).

8. Be ready to jump off when the boat starts sinking. Or blame someone else.
For people using XGH one day the boat sinks. As time passes by, the system grows into a bigger and bigger monster. You better have your resume ready for when the house comes crashing down. Or have someone else to blame.

9. Be authentic. XGH don’t follow patterns.
Write code however you want. If it solves the problem you must commit and forget about it.

10. There’s no refactoring just rework.
If things ever go wrong just use XGH to quickly solve the problem. Whenever the problem requires rewriting the whole software it’s time for you to drop off before the whole ship sinks.

11. XGH is anarchic.
There’s no need for a project manager. There’s no owner and everyone does whatever they want when the problems and requirements appear.

12. Always believe in improvement promises.
Putting TODO comments in the code as a promise that the code will be improved later helps the XGH developer. He/She won’t feel guilt for the shit he/she did. Sure there will be no refactoring (see Axiom 10).

13. XGH is absolute.
Delivery dates and costs are absolute things. Quality is relative. Never think about quality but instead think about the minimum time required to implement a solution. Actually, don’t think. Just do it!

14. XGH is not a fad.
Scrum, XP? Those are just trends. XGH developers don’t follow temporary trends. XGH will always be used by those who despise quality.

15. XGH is not always WOP (Workaround-oriented programming).
Many WOP require smart thinking. XGH requires no thinking (see Axiom 1).

16. Don’t try to swim against the tide.
If your colleagues use XGH and you are the only sissy who wants to do things the right way then quit it! For any design pattern that you apply correctly your colleagues will generate 10 times more rotten code using XGH.

17. XGH is not dangerous until you see some order in it.
This axiom is very complex but it says that a XGH project is always in chaos. Don’t try to put order into XGH (see Axiom 16). It’s useless and you’ll spend a lot of precious time. This will make things go down even faster. Don’t try to manage XGH as it’s auto-sufficient (see Axiom 11) as it’s also chaos.

18. XGH is your bro. But it’s vengeful.
While you want it XGH will always be at your side. But be careful not to abandon it. If you start something using XGH and then turn to some trendy methodology you will get fucked up. XGH doesn’t allow refactoring (see Axiom 10) and your new sissy system will collapse. When that happens only XGH can save you.

19. If it’s working don’t bother.
Never ever change – or even think to question – a working code. That’s a complete waste of time even more because refactoring doesn’t exist (see Axiom 10).
Time is the engine behind XGH and quality is just a meaningless detail.

20. Tests are for pussies.
If you ever worked with XGH you better know what you’re doing. And if you know what you’re doing then why bother testing? Tests are a waste of time. If it compiles it’s good enough.

21. Be used to the ‘living on the edge’ feeling.
Failure and success are really similar and XGH is not different. People normally think that a project can have greater chances of failing when using XGH. But success is just a way of seeing it.
The project failed. You learned something with it? Then for you it was a success!

22. The problem is only yours when your name is on the code docs.
Never touch code of which you’re not the author. When a team member dies or stays away for too long the thing will go down in flames. When that happens use Axiom 8.

23. More is more.
With XGH you thrive on code duplication – code quality is meaningless and there’s no time for code reviews or refactoring. Time is of the essence, so copy and paste, quickly!