see which API's Im working with... or if from scratch then see which API's I'll be constructing and how those will be used by higher up functions...
if the app has a GUI then mockup the GUI first in some graphics program to see which kinds of things are useful to users, and then see what the minimum number of primitives is needed from the layers bellow to service that
pay the assistant $15/h to set up appointments/get coffee/make you look lie a hot-shot, pay the software engineer knowledgeable of the latest mobile platform $2/h
things like that are so insulting
the machine does not have to be big...
it can be a bunch of small spider like machines, or even more groups of machines:
- material suppliers
- welders
- concrete ones (these can be essentially carrying tubes that are pump out concrete)
this might be the next step for building multilevel farms, for agriculture (building huge pyramids).
I've seen mockups/studies done in Japan (I think) that talk about exactly this, spider like swarms of robots moving along rail like structures maintaining/buidling fractal like pyramid structures that are super-tall ;))
the only way to take agriculture/housing to the next level... have multi-level cities (and not what pseudo-multilevel that we have now)...
- rail constructors (rails for welders/material suppliers to move along)
if the app has a GUI then mockup the GUI first in some graphics program to see which kinds of things are useful to users, and then see what the minimum number of primitives is needed from the layers bellow to service that