i finally cracked frontend design with AI... without using any skill
frontend needs taste to not look like slop, and i'm more of an engineer than an artist, so i'm genuinely bad at it
my way around it: collecting inspirations and modules from other people, building a lego of components
resources you can send to your agents:
- https://t.co/7CUfh1jSmr
- https://t.co/hKiKiyjLd8
- https://t.co/XMkWlWenQv
- https://t.co/k3p8MhfvCj
- https://t.co/PTkhqaLgU7
it's VERY easy for agents to edit components once they have the code
you send the link, your agent fetches the full list of components, then you ask it to find the best way to integrate them into your frontend foundation
the easiest way i found to make your UI/UX drastically better without being a genius designer
-get jacked
-crush it at work
-marry an honest woman (with a good body)
-keep things fresh so you smash like it’s the hooking up phase
-travel the world
-watch good movies
-avoid complainers
-eat healthy (90% of the time)
-call your friends for no reason
-host banger dinner parties
-overpay for good concert tickets
-have monthly movie nights with people who make you belly laugh
-and if you’re ever feeling down remember you’re spinning on a sphere in an infinite universe and the fact you’re alive is a 1 in 500 trillion miracle - you’re so lucky it’s absurd and you have nothing to lose :)
Transformer’s Attention mechanism has come a long way. We’d like to thank the researchers and the engineers in the open-source community for continuing to make high-performance AI accessible. Please celebrate with us by sharing this post, tagging more contributors, and sharing anecdotes to complete the open history of Attention! (1/8)🧵
Learn to ship. Shipping is a skill distinct from coding. Shipping is designing, coding, QAing, story-telling, teaching, marketing, selling, pivoting, iterating…
It used to be that coding dominated in importance because of coding ability scarcity. AI will push you to go further.
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?
-get jacked
-crush it at work
-marry an honest woman (with a good body)
-treat her amazing
-travel the world
-watch good movies
-avoid complainers
-prioritize your health
-call your friends for no reason
-be a hot strong dad
-host banger dinner parties
-and if you’re ever feeling down remember you’re spinning on a sphere in an infinite universe and the fact you’re alive is a 1 in 500 trillion miracle - you’re so lucky it’s absurd and you have nothing to lose :)