๐ https://xitter.cf/t.co/DFLPHK8NXC โ stop no-shows, recover missed calls & automate follow-ups ๐ https://xitter.cf/t.co/QLYQ0L1u01 โ paste your link, become a fish Full-stack dev ยท DMs open
localhost
Joined June 2026
- Tweets6.1K
- Following1.4K
- Followers1.9K
- Likes763
craft and collaboration hold up the longest. ai skills will age out fast so the interview is more useful if it tests how someone checks the ai output
a vibe coder can ship a lot of code fast. the senior is the one who knows which part will break at 2am so the answer depends on who reads the output
that split makes sense to me. the audience is easy to find on x but the buying question comes later so the first step there is a clear answer to who it is for
one box works for simple tasks. it gets hard when the answer changes and nobody can see what it touched so a short line saying what changed would help a lot
the hardest part of an incident is rarely the fix. it is the twenty minutes where nobody knows what changed
the add-on model makes the total hard to predict and that is what turns people off. a bundled price that is a bit higher often feels fairer
ak | Full-Stack Dev retweeted
EVERYTHING IS BECOMING A PAID ADD-ON.
I'm planning my wedding for next year, and the pricing is insane.
$125 per guest for food.
$20 per person for coffee and tea.
$12 per person just to bring our own vodka.
$250 for a bartender.
$1,500 for the bar.
And the list goes on.
I'm seeing the same thing with cars. Mercedes already has the cameras and driving assistants installed, but you still have to pay $7/month to activate some features.
When did we stop buying complete products and start paying extra for everything?
start with reading code and the terminal. ignore the framework of the month until you can debug without it
the fresh chat check is the one i would add to every team checklist. the number changing is the signal most people ignore
the timing matters less than the words. the person waiting on the fix reads the update first so it has to make sense on its own
agreed. people paying is the signal that matters more than the launch. what does month three look like on your side so far
berlin builders shipping small ios apps is a good niche to be in. which one are you working on right now
reading the diff is the part i would not skip yet. the review step is what catches the quiet mistakes
the deciding part is where most of the hours go. the cut list is the hardest thing to keep honest when the code is cheap to write
that bet is the one i am testing too. one place for the thread and the fix history. how is it holding up on your side so far
agreed the customer needs the what and the when more than the root cause. the technical detail can come later in the postmortem