Making sense of life requires you to learn new skills, understand a new perspective throughout your time here on Earth. Being intentional to learn is merely an intentional effort to find out more about this world in which we find self actualization.
Wanting centralised control under monetary authority
Minus, like life, have limits. How will that change the way you choose which photos to post?
Software should convey a sense of calm. I, as a user, should know what I can do with it and what I can’t do. I always know what’s happening, where I am and what is next. Everything comes easily to me. I don’t get stuck, never feel lost or stressed out.
The factors to effort to learn your software:
We need to facilitate learning wherever possible. Concepts as well as spatial and temporal relationships should stay constant and recognizable. Some examples: Software should always tell me directly what I need to know
- You intrinsically enjoy investing in companies
Absent of any financial returns, you wnt to do work to invest in companies anyways: mostly taking meetings with entrepreneurs, reading about business models, and networking with other domain experts.
- You have time - at least 10/weeks for the next 3-4 years doing work.
You should consider advocating a portfolio approach to angel investing. You need to diversify your risks
All of the available literature shows a positive correlation between return on investment and time spent conducting due diligence.
You need to budget sufficient time for you to build a suitably diversified portfolio.
- Customer’s needs vs growing rapidly. Does it need to be a dichrotomy?
- What are the best practices of creating a habit loop?
- Can a team lose sight of users feedback but hit metric? How does that work?
The unintended metrics - the time spent metric.
What is the difference between user value and business value? And what happens when that clash?
- Can we marry these two objectives together?
- Sometimes it can be done with appropriate copywriting
What is a product tactic? How does that look like?
You improve what you measure
Teams incentivized by metrics will move metrics. They won’t address user pain points.
Some examples include:
- Clubhouse, push notifications → retention metric
- Snapchat, streaks → repeat daily engagement metric
- Booking.com, urgency messaging to purchase → monetization metric
At times, your metric may not address a pain point. But you can avoid this by coming up with meaningful metrics based on pain points first.
But painpoint-derived metrics need not be our northstar metrics. You do not need to couple them together.
If you do not prioritize users, done inappropriately, they can sense it
If you prioritize user value, in the long run, your business value will follow.
Over the long-run, if a business invests in building user-value and operates with a user-first perspective, business metrics will follow.
You can consider this other tool for your data analytics. Interesting how they chose to open source their library. And their team is stacked.
Decentralised data for social media
[startup is not the best way to get rich](A Startup Is The Worst Way To Get Rich | by GreekDataGuy | Sep, 2021 | Making of a Millionaire)
Self hosted google like search engine
How does a system handle such high request rate? How does the architecture of such systems look like?
You heard of timescale DB?
What are timescale hyperfunctions?
They ar a series of SQL functions that makes it easier to manipulate and query time-series data in Postgre SQL with abstracted functions.
You can use hyperfunctions to calculate percentile approximates of data. Compute time-weighted average.
These hyperfunctions allow you to calculate percentile approximations.
Check it out [here](https://blog.timescale.com/blog/introducing -hyperfunctions-new-sql-functions-to-simplify-working-with-time-series-data-in-postgresql/)
Monitoring an API falls under the category of application performance monitoring
You can create application in components that are preset with features and styling. Building on top of react, you will use the syntax of react.
Bugs are part of the process. Quoting the article:
No matter how good a developer you are, these things will happen
- Create bugs
- Create the wrong software
- Write a dirty hack to get it done
- Architect the wrong design
- Make assumptions
- Fail a code review
- Spend a day where you can’t get the code to work
- Work on a failed project (probably)
- Technology will fail you
- You break the build
- The code won’t compile
- Miss a build a step and cause the environment to not work correctly
Skills can be learnt. Skills can be taught and improve over time. Writing readable code is a skill.Put yourself into a feedback loop; with deliberate practice you can improve and save all the readers of your code a ton of pain in the future.
The technology that we know 18 months ago is no longer the same. You have to consistency keep yourself well versed and updated with the latest happening. No, you do not do that out of fear of missing out. You learn because you have a learned attitude to seek knowledge so you can gain wisdom along the way. In the space of technology, knowledge is fills up the gap between a sucessful senior CTO with a fresh graduate.