From MyDaxko:

Tagline: Simple code is easier to understand and maintain. Strive for simple code and simple designs.

Other Resources

http://c2.com/cgi/wiki?KeepItSimple
Software design is not a haphazard process. There are many factors to consider in any design effort. All design should be as simple as possible, but no simpler. This facilitates having a more easily understood, and easily maintained system. This is not to say that features, even internal features, should be discarded in the name of simplicity. Indeed, the more elegant designs are usually the more simple ones. Simple also does not mean "quick and dirty." In fact, it often takes a lot of thought and work over multiple iterations to simplify.
http://blog.codinghorror.com/kiss-and-yagni/
Don't use fancy OOP features just because you can. Use fancy OOP features because they have specific, demonstrable benefit to the problem you're trying to solve. You laugh, but like Rico, I see this all the time. Most programmers never met an object they didn't like. I think it should be the other way around: these techniques are guilty until proven innocent in the court of KISS.
http://blogs.msdn.com/b/alfredth/archive/2009/01/08/are-you-smart-enough-to-debug-your-own-code.aspx
Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.

I think we should break out of making things private here at Daxko.

We should be treating anything we create (or write) openly and transparently for several purposes. It lets other see how we work and could potentially be used as a recruiting tool for other savvy engineers. Unless the code contains proprietary information, or otherwise sensitive client data I don't think there's any reason to make private repositories.

Thoughts?