Proof of Work for Developers
As a developer you can have many types of proof of work
You can have a portfolio website that shows all your past projects (a few dots of your path)
You can have some contributions to open source projects (more dots of your path)
You can use learn in public strategy to have as many dots as possible about what went right and what went wrong in your learning path
People that can create new things are rare
You can have a CV or Linkedin (worse proof of work), as anybody can say anything on it.
Shares tags with
- Bleeding edgeedge Bleeding edge is the state of art of something It is the new technology When you focus on bleeding edge (new), you have an advantage as everybody start in a clean slate. You…
- Consulting/ProfessorsIf you never own the whole process of doing something, like having Skin in the Game, you never will "taste" reality (Reality has a lot of details I think this happens with who…
- Generalistgeneralist are robust to automation automation will automate a specific task, it can't be easily generalized generalist are better for long term solutions for holistic solutions…
- Abstract NodeYou can model knowledge as a graph of nodes of concepts/ideas When you abstract 2 or more ideas in a more general concept finding the edges among those nodes This will make show…
- AtomWe can use atom to describe something that is minimal and indivisible We can have an atom of state like redux recoiljs We can have an atom of thought as Roam and Zettelkästen uses…
Sign in with GitHub to reply.
Select any passage to quote it.
Comments