Sovereign Software Development

Software companies, at present, generally operate under a deeply flawed collaboration model: a socialist one. The engineering team owns the codebase in common, with no one having more authority than anyone else in any part of it. When you make changes, anyone on the team, no mater how far removed from the changes you’re making, can criticize and obstruct your changes; even if you’re altering something you created to begin with and know best.

This socialist model is ideal for entryists to sabotage and subvert. Furthermore, it fails to reward those of outstanding merit, who can only get informal recognition at best. There has to be a better option.

A bold engineer has noted these flaws and devised an alternative that mitigates or eliminates them entirely: Sovereign Software Development.

DisruptSV Wiki

Today, the DisruptSV wiki makes its debut.

This is our knowledge base for target companies, their weaknesses, and how to profitably take advantage of those weaknesses. Join the cause to take back tech from its occupiers — it’s literally in your financial interest.

While we’ve all got our plans that we won’t be sharing, contribute your other insights to the knowledge base so others can hit the ground running. Having more bootstrapped, closely-held companies in the space benefits us all indirectly. Your contribution to the wiki is a vote for this eventuality.

Don’t Sell Your Freedom

This has been a fruitful week.

We’re near launching the wiki, where we can collaborate to overwhelm Silicon Valley giants with small, targeted competition. Even with massive workforces and mountains of cash, they can’t defend every position.

The next article will be a heavy one. Until then, enjoy this excellent post on IndieHackers: How to Build a Startup Empire without Selling Your Freedom.