alexgvozden
The Micro SaaS Revolution: From Giants to Solopreneurs
hyperproductivity is here, but both market and options are increasing too so not sure what math could be used realistically but for sure we can't foresee in near future death of ideas
more technical details would be good but I guess either I missed it or they look at it as IP
in all the teams I worked most successful were ones that insisted on writing wiki / readme pages for each feature and task...
why?
1) project manager (person knowing why we're building) has to do fair amount of explaining to the developer 2) it's easy to verify that developer understands what he/she needs to develop 3) everyone else in the team can easily update themselves
my template was something like this
1) what has to be built 2) for whom - who is the typical user and scenario 3) who will built it and which branch on git 4) what app parts will be changed 5) any information related to deployment (database changes and similar)
doing it upfront meant a lot to the team, discussions and clarity... I would just call this more Wiki development then readme :)
I would not recommend console.log for production anyway
after that you will be able to think more rationally but honestly, if you have drive to do something else then leave transition period for leaving the company and in no way tell investors your idea is to start a new company, they will claim this came in the time of working there thus IP for new product should stay in the company