The advantage of a company, as opposed to an individual, is that the two are not necessarily mutually exclusive. Mahalo can at once both work on resolving bugs on Mahalo central, as well as start up new (and maintain existing) sister sites. In fact, the commonality of code implies that fixes developed for one site can be rapidly exported to other sites.
However, Mahalo does need to walk a fine line between putting all its resources into new site development, strangling the maintenance effort, and putting all its efforts into fixing bugs, bringing new developments to a standstill. The trick is to find that golden path in the middle, where urgent bugs are fixed immediately, less urgent bugs are fixed, though at a lower priority, and new development continues. As income from the new sites starts rolling in, Mahalo will be able to hire more devs to make this work-load more bearable, allowing acceleration of both aspects.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.