FRONTEND IS HARDER THAN BACKEND
FRONTEND IS HARDER THAN BACKEND
FRONTEND IS HARDER THAN BACKEND
FRONTEND IS HARDER THAN BACKEND
FRONTEND IS HARDER THAN BACKEND
FRONTEND IS HARDER THAN BACKEND
4 years ago,
I was still afraid of public speaking.
Now I can jump on stage and laugh at my own jokes.
It’s really just me up there, not pretending to be someone else when I step on stage.
And it feels amazing, you should try it.
Let’s CRUSH this week!
//PH: @RoxanaCodes
Claude Code creator:
"Since Opus 4.5, i uninstalled my IDE. I don't edit a single line of code by hand.
100% my code is written by Claude."
in 1-hour Y Combinator podcast, Boris Cherny reveals his daily Claude Code setup.
Claude Code + loops + dynamic workflow
Worth more than a $500 vibe-coding course.
One of my consultant pet peeves is opening a production database and seeing:
`organizationId`
`created_at`
`isActive`
`deleted_at`
in the same table.
I already know what happened.
Someone let the ORM create a few columns.
Someone else wrote raw migrations.
The JavaScript developer preferred camelCase.
The DBA or Backend guy preferred snake_case.
Nobody stopped to decide what the schema should look like.
Your ORM supports column mappings.
Use them.
Keep camelCase in your application.
Keep snake_case in your database.
The database is a product too.
Not a dumping ground behind your API.
bring the whole group chat
I’m building a tool to get you from 0 to an interaction like this with lesser prompts and way less token consumption
interaction inspired by the great @geniegetsme iOS app
I’m open for work.