ຸ retweeted
Like mother, like sons.
Stream Marvel Television’s #VisionQuest and the rest of the #MCU on Disney+.
ຸ retweeted
Pakai AI itu ada levelnya
LV1 ngobrol, copy paste ChatGPT
LV2 kasih konteks, kasih Excel sheet
LV3 AI yang kerja, bikin slide, bikin dokumen
LV4 agent kerja bareng, koordinasi
LV5 agent nyuruh agent, move metrics
LV6 AI detect dan auto-solve problem sendiri
LV7 bikin AI sendiri untuk ngumpulin unique data untuk bikin AI yang lebih canggih
Penjelasannya di video
ຸ retweeted
🚨 MASSIVE CRASH: 🇮🇩 Rp 848,000,000,000,000 ($47 BILLION) wiped off Indonesia’s stock market as stocks plunge around 11.5%.
The biggest daily drop since 1998.
This is insane...
ຸ retweeted
I'm just going to dump my whole agentic setup out here, because I see too many people missing giant chunks of this and it's hurting them.
Here's what I have and recommend:
0. an AGENTS.md that is a router -- it sends the agent to the right skills, docs, tools
1. a standard workflow doc/skill customized to my needs ... (grab Matt Pocock skills if you don't already have something) ... I tag this in most sessions with `@/AGENT_WORKFLOW.md` and it pulls it in.
2. self-healing docs for every system, and agents are instructed to keep them updated ... I tag the ones I know I need, or let the agent find them through AGENTS.md ... I also provide a more detailed summary in the first 7 lines of every doc, so they're easily greppable to find the right thing, and this is documented in AGENTS.md
3. agents always run the app ... the agent should always actually run the app itself, and test its work and fix issues as it goes, especially if running autonomously / asynchronously
4. end-to-end tests and instructions to write more and keep up to date, and docs on how to write tests, what to avoid, and a list of all the tests and what they test in yet another markdown doc ... write and run targeted tests during implementation, improve and commit with work
5. custom linters at precommit hooks looking for any problems you run across, with `--fix` fixing the problems automatically, OR if that's not feasible, it shells out to a cheaper LLM like Composer 2.5 or Sonnet to fix the problems -- NOT just flagging them, but actually resulting in cleaned code
6. cross-agent review at each major point: research, plan, implementation, and wrap-up. I mean codex, claude, cursor, whatever -- but it shouldn't be the same model reviewing the same code. And specific docs for agent review, what to look for, how to approach it. Also, personas -- looking at the code from different perspectives, such as maintainability, code quality, security, performance, AI smells, domains (e.g. "financial services expert" or whatever) ... and each persona also "owns" a set of system docs too and keeps them up to date
7. agent traces / worksheets that track what the agent is doing each session. if the agent fails partway through, you should be able to hand this worksheet to another agent and it could finish the job. commit this worksheet with the work so it's all connected and easy to reference later (you will reference these later!!), also have the agent apply git tags that correspond to specific worksheet names so they're easy to find
8. automatic agent feedback to you at the end of the session, added to a doc that is also committed with the work, that you periodically ingest into an interactive session and improve your workflows
9. a tools or bin folder that contains python or bash scripts that the agent has skills to make to make its job easier (for example, I have an `agent_review` bash script that lets the agent kick off agent reviews via CLI without knowing each agent's particular incantations) ... docs on how to make scripts effectively, and instructions to constantly build these out more
10. periodic agent sweeps through recent commits, looking for problems / gotchas from a higher level across commits
11. a coding conventions doc that is just for specific coding conventions you want to see in the code base, your review agents use these a lot (but a lot of this should be in linters)
12. an agent loop / night shift skill for autonomous work, that lays out how the agent is to approach this, from an orchestration standpoint
13. a task queue that is accessible to the agent (mine is just a TODOS.md, but yours might be in Linear etc, with a CLI to fetch via API)
14. a periodic false-confidence test audit skill that looks for tests that aren't actually testing what you think they're testing, and that fix those
15. visual regression tests -- take screenshots, compare via tool and with agent visual review, commit with work (git lfs useful here) or at least push into the PR
16. automatic performance benchmark tests that notice when performance degrades
17. performance profiling tools that can be used by agents for targeted benchmarking, trying new techniques, comparing outputs, and comparing profiles
18. end-of-shift full validations, including running all tests, performance, agent reviews, sweeps, everything -- when you return, it's all as pristine as it can be
If you have all this, your agentic coding experience is going to be very different than dry prompting and manually guiding it toward the right thing every time.
Inspired by 82-0.com, but for football.
Draft a Premier League XI from random clubs and seasons. Build your team. Simulate the season.
Can you go 38-0?
38-0.app/game
#football #soccer #fifa #premierleague
ຸ retweeted
During your life, you will meet a lot of people like Raj.
It is important that you ignore them.
ຸ retweeted
Tenang, walau 1 dollar skrng udah 18.000
Itu artinya rupiah lagi dilemahin, biar ekspor josss, toh beli tempe goreng masih pake rupiah. Ga pake dolar.
Amanlah.
Itu buktinya ibox, resto mewah, event2 fashion tetep rame.
Ini ulah mata2 asing yg buat gaduh.
Jaya jaya jaya
ຸ retweeted
this is actually insane
> be tech guy in australia
> adopt cancer riddled rescue dog, months to live
> not_going_to_give_you_up.mp4
> pay $3,000 to sequence her tumor DNA
> feed it to ChatGPT and AlphaFold
> zero background in biology
> identify mutated proteins, match them to drug targets
> design a custom mRNA cancer vaccine from scratch
> genomics professor is “gobsmacked” that some puppy lover did this on his own
> need ethics approval to administer it
> red tape takes longer than designing the vaccine
> 3 months, finally approved
> drive 10 hours to get rosie her first injection
> tumor halves
> coat gets glossy again
> dog is alive and happy
> professor: “if we can do this for a dog, why aren’t we rolling this out to humans?”
one man with a chatbot, and $3,000 just outperformed the entire pharmaceutical discovery pipeline.
we are going to cure so many diseases.
I dont think people realize how good things are going to get
how to build a bootstrapped startup without funding:
1. pick a problem you personally have. if you don't use your own product daily, quit now
2. skip the pitch deck. open your code editor. ship something ugly in a weekend
3. charge money from day 1. free users give you nothing but support tickets
4. use boring tech. PHP, SQLite, vanilla JS. frameworks are a trap that mass waste your time
5. host on cheap VPS ($5-20/mo). not AWS. you don't need kubernetes for 1,000 users
6. do customer support yourself. it's the fastest product feedback loop that exists
7. automate everything you do more than twice. cron jobs > employees.
8. grow on Twitter/X by building in public. your journey IS the marketing
9. keep your burn rate near zero so you never need to raise. ramen profitable > series A
10. say no to investors, cofounders, and "advisors" who want equity for intros
i've been doing this for 10+ years now. no employees, no funding, no board meetings
the entire VC game is designed to make you think you need permission to start
you don't











































