https://hackernoon.com/an-organized-chaos-5c844f8a9c82?sourc...
21 karma · joined January 1, 2017
https://hackernoon.com/an-organized-chaos-5c844f8a9c82?sourc...
I personally just use evernote and list everything there.
[1] https://medium.com/@jmrocela/an-organized-chaos-5c844f8a9c82
In the end it's still a machine that gets things done.
IMO It is helpful to remove the "senior" or "junior" title when working with them.
Work with them. Provide guidance when needed. Learn from them. Trust them. Consider their opinions. Help them provide you with information on things you are not familiar with. Praise their accomplishments in public. Critisize mistakes in private. Provide useful feedback
Have fun :)
I shall carry your advice at heart.
What language are you good at OP?
You can quickly mock up majority of your use case using PHP, ruby or even Node.
Create a monolithic app and stay away from microservices until you have clearly drawn service boundaries. I'd say (6 to 12 months) in production. You dont need the headache of the distributed overhead.
Just keep in mind that you should "write code that can easily be disposded or replaced, not extensible"
For generating client sdk's i suggest using swagger. Grpc is there but i have trouble grasping protobuf sharing at the moment
For user clients, i would go for react native.
You're better off using a 3rd party for analytics when you are starting up: if you have the money, I'd suggest using segment, new relic or even google. Else, do it with prometheus or kibana.
My 2 cents