43 karma · joined September 10, 2016
As I'm typing this there is one reality that I'm understanding, the quality and completeness of the data fundamentally determines how well an AI system will work. and with just text this is hard to achieve and a multi modal experience is a must.
thank you for explaining in very simple terms where I could understand
1. Programming: Beyond the basics
2. Computer Systems
3. Operating Systems
4. Algorithms and Data Structures
5. Computer Networks
This is going to take time but it will be worth your time.
For discrete Math I sincerely recommend you to take a look at this book "Discrete Mathematics with Applications by Susanna Epp. This is an excellent book and it has good problems.
I will also recommend you to look at https://fa24.datastructur.es/ this is a very good beginner course on data structures that is completely free by UC Berkeley
1. Bounce rate combined with Session length
- Bounce rate can be defined as % of users who leave only after viewing one or few pages. The reason at least I coupled bounce rate with session length is atleast in the app we work there are few personas that prefer to stay in one page for a long period of time and do some interactions. Bounce rate combined with Session length always give us a good picture are folks using the feature(s) as intended. One thing we did was set a baseline metric where we first measured session length on the app as well as per page basis, and after that we could build the bounce rate. Amplitude works well for this case
2. Churn Rate - number of users who stop using the app over a given period. This should be easy to do by querying db if you maintain some session duration information.
1. keep the db schema simple. remember you are startup things change, so does the db schema so does your architecture.
2. One piece of advice from personal experience, Microservices usually don't work well for startups try building your solution as a modularized monolith.
3. always make decisions that are reversible (2 way door) and make sure coming back is also easy.
4. for any features you release have qualitative and quantitative metrics and more importantly guard rail metrics.
5. where ever you can use the an off the shelf solution like feature flags (launchdarkly), product analytics (amplitude) use them. These are solutions used by countless startups do not reinvent the wheel.
6. prioritize customer feedback, that is going to get you money and they are going to help make your product better. Instead of "failing fast" prioritize on "learning fast".
7. Be focussed on solving the problem don't romanticize the solution.
If someone is new to programming this in no way does any justice. Programming is way too complex to be fit in 5 minutes intro. https://norvig.com/21-days.html
Apart from this his awk,sed and perl oneliners are worth to act as a reference as well.
PickTrace (YC S15) is striving to transform agriculture. We help agricultural producers thrive in a time when regulatory, labor market, trade, and environmental pressures are increasingly challenging. Our software provides growers with real-time insights so they can improve their operations’ efficiency and compliance. Our customer obsession ensures that we solve real pain points, modernizing and transforming the world’s oldest and most fundamental industry – agriculture.
We are growing our team and are looking for
Senior Product Manager: https://hire.withgoogle.com/public/jobs/picktracecom/view/P_...
Senior Devops Engineer: https://hire.withgoogle.com/public/jobs/picktracecom/view/P_...
Senior Front-end Engineer: https://hire.withgoogle.com/public/jobs/picktracecom/view/P_...
Senior Android Engineer: https://hire.withgoogle.com/public/jobs/picktracecom/view/P_...
See and apply to open roles and/or email me: chaitanya.vemprala at picktrace.com