As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
🚨 They told you privacy was a feature.
$DREGG is proving it should be a LAW OF MATHEMATICS.
No blind trust.
No hidden permissions.
No backdoors waiting to happen.
Every interaction is capability-based.
Every access must be explicitly granted.
Every action is cryptographically enforced.
This isn’t just another Solana meme narrative…
It’s a radical rethink of digital sovereignty. ⚡
Early projects with real vision always look “too different” at first.
$DREGG feels like one of them. 👀
CA:
XkeTXo1125vz5H9svJpGiw4JvLbN8VmMu9cmMvspump
📈 Chart:
https://t.co/TBi5HDT1mz
🌐 Website:
https://t.co/5KyDbrJOf4
💻 GitHub:
https://t.co/CtgqumXMpk
Watching this one closely. 🔥