Strategic Planning for a New Business in the Tech Industry

(strat planning, continued)

From a consumer's point of view:

technology is a medium for indeterminate welbeing; there are an unknown number of acceptable outcomes. An uncertain-(N?)-dimensional optimisation target.

From a capitalist's point of view:

technology is a medium for machinery to generate profits; any opportunity to increase returns and reduce risk over a decided investment window, are game. Two (2) dimensional optimisation target.

From a technical serf's point of view:

returns have a ceiling; the question is one of getting a job done with minimal effort. One (1) dimensional optimisation target.

(continued, following preliminary studies in Ruby's package management systems)

I've pretty much figured out a product/service that needs to be worked on in this space... an abstraction layer over:

(dimension 1)
- documentation
- library/package management
- development
- deployment
- costing (for managers)
- hiring (for managers)

... for...

(dimension 2)

- all (popular) computer languages

... this basically facilitates ease of integration, and choosing the right tool for the right job, and faster sunsetting of the wrong tools. The market simply deserves to be clearer.

A day will come where no self-respecting developer is attached to a particular language platform because the ease of traversing language platforms becomes trivial.

(a day later, to the lady who suggested recreating something like http://bento.io, to whom I said it was non-technical founders who needed more help:)

Fine. You win. The devs need help too. But I'm not sure about the format for a solution.

Acquistion time for unknown languages/platforms needs to drop by 99%

10-50% speed-ups in learning time are good for a charity operation.

With 1,000% I can run a business.

With 10,000% we're ahead of the curve.

(Earlier, my reaction had been this:)



So what comes to mind now, as what traditional AI folks call an "expert system", for the education of people in new technologies. Specifically, the non-profit side of the project can work on being a Stark-Jarvis for open content. The for-profit side of the project can work on closed bodies of knowledge. The precipice is of the usual form of course - have a solution that is too closed, and would-be-customers are incentivised to build one themselves; have one that is too open, and it lacks commercial value.