phishy retweeted
Docs aren’t just for humans—they’re context for agents, too.
Keep your agents on track with up-to-date docs, and let your agents help keep those docs current.
here's how i shipped 2,500 PRs last month to production
this was originally supposed to be for Cursor Compile in London. i couldn't make it since i was livestreaming for Grok @Bot Galaxy so i'm making it available for free here on X! watch it on 2x speed, i talk slowly
phishy retweeted
Replying to @mikejulian @DuckbillHQ
Why does it sound like you were looking at 2 days of code review and instead spent weeks to improve your system so you didnt need to do those 2 days lol 😂 But regardless all the stuff you listed is good regardless of AI or PR reviews thanks for sharing
phishy retweeted
🚨 BREAKING: ICE agents in Minneapolis are seen arresting another teenager without verifying his identity first, and admit to it on camera.
In the video, the teenager calmly tells agents he can go inside and get his ID to prove who he is. The agents refuse. Instead, they say they’ll “take pictures at HQ”… and then force him into their SUV anyway.
That is deeply alarming.
Law enforcement is not allowed to detain people first and figure out who they are later without lawful justification.
Detaining someone without verifying identity, without probable cause, and without allowing them to present ID raises serious Fourth Amendment concerns.
You cannot seize a person just to “check” who they are.
This also mirrors what DHS has now openly admitted: that people are being detained first and sorted out later based on suspicion alone.
That means innocent people, minors, and U.S. citizens are being taken into custody without verification, without charges, and without due process.
If the government can forcibly detain someone simply to identify them, that is not law enforcement… that is unlawful detention.
phishy retweeted
Tip: To improve AI coding, don’t just jump straight into tasks without planning. Planning first makes a big difference, as does managing context.
🧵👇
1. AI tools thrive on structure.
When you start with a clear spec, you guide the model’s reasoning. One good spec often performs better than 8 vague prompts.
2. A great spec includes:
– Purpose & Requirements
– Inputs & outputs
– Constraints
– APIs
– Milestones
– Coding conventions
This acts as both a blueprint and documentation.
3. Use Test-driven Prompts.
First, ask AI to write tests for your task.
Then, have it implement code that makes those tests pass.
Classic red → green → refactor.
4. Break your work into small chunks.
Decompose complex prompts.
Keep tasks focused so the model can produce cleaner, more reliable code.
5. Share context.
Feed the model your style guide, architecture, or prior code.
More context = more consistency.
6. Use the AI to generate diagrams
Helps with architecture planning and makes prompt inputs more grounded.
7. Always review AI output.
Check logic, refactor if needed, run the tests. AI coding is collaborative, not fire-and-forget. Keep the human in the loop.
Summary:
– Plan before you prompt
– Write specs
– Use test-driven dev
– Add context
– Break down tasks
– Iterate
💡 Vibe coding is fun. But planned prompting gets you further, faster.





