👨🏻💻 Full Stack Dev: Laravel, Vue 🧑🏻💻 Misi mencari biji kopi di https://teapawt.org/t.co/qMNawNuReE ✍🏻 Saya menulis di https://teapawt.org/t.co/herzGgp5h6
Joined October 2012
- Tweets19.6K
- Following747
- Followers8.8K
- Likes1.5K
Pinned Tweet
Himpunan projek-projek peribadi saya:
1. Perlu Kopi
Sebuah direktori pemanggang biji kopi tempatan, terutamanya biji kopi yang dipanggang untuk filter coffee. Saya nak mudahkan diri pilih biji kopi dan senang rekomendasi kepada kawan-kawan.
teapawt.org/afiqsazlan/status/1829…
🎉PerluKopi dah ada UI baru!
Terima kasih @afifsohaili buka mata saya mengenai kesilapan DB-dump-to-UI. Kena lebihkan penyampaian visual.
Terima kasih juga @ImnNazri untuk mockup design yang padu.
Juga terima kasih kepada semua yang menyumbang kepada perkembangan ini.
Most of a QA tester’s time goes into setting up, not testing. Before they can check a single screen in our app, they have to create a booking, switch to a carer account, apply, switch back, approve, pay, start the job, and so on.
I wanted to fix that with Claude, both for the QA team and to verify my own work faster.
The answer: a Claude chat connected to an MCP server loaded with QA scenarios. Now they just tell Claude the state they need, and start testing.
You might guess it just writes rows into the database. But an app action is more than a database write: there are notifications, cascading updates, queued jobs and more.
So Claude plays the customer and the carer step by step, through the same API our apps call. Everything that happens in real life happens here too: push notifications, KiddoPoints earned, the review prompt. One run sends about 20 notifications across the two phones.
The states that took QA longest to build are now a single sentence. A carer who has to accept the parent’s edits halfway through a fee negotiation. A tuition class that starts in 30 minutes. A customer with 5,000 points, some expiring in 3 days, and a 3x promo running.
The tool will keep on growing as our features grow.
On safety: the scenario server only exists on QA. Production doesn’t register it at all.
A tool that can run whole user journeys is too much uncontrolled power for production. If you build something similar there, build small, narrowly scoped tools that each do one thing, and gate each one by permission.
That’s what we do on production: each write tool changes one setting, shows a preview first, and only saves after you confirm.
afiqsazlan retweeted
i wanted a faster feedback loop for giving feedbacks about my app to a running opencode session.
my workflow before was:
1. check the UI, found something to fix
2. screenshot/copy the selector/page url/etc whatever looks relevant
3. find the right project and the agent session
4. describe the bug, paste everything
which is slow, so i built a chrome extension that talks straight to my opencode, called browsertalk (duh)
point at an element. it automatically captures a screenshot crop, the page url, selector, text, attributes, and bounding box, then gives you a comment box. drop your comment, hit submit, and it queues the feedback to the opencode session you pick.
the agent gets the comment plus the facts it needs to find the code.
it's been genuinely helpful for me. i can just rapid-fire the feedbacks from the browser without breaking my flow of checking the UIs page-by-page.
publishing the working version on github for you guys. it's very rough, but usable enough. PRs welcome. should be able to trim the msgs more (usually the url is the most important and enough for agents to find what element I'm talking about).
opencode is the default backend (cos I use it), but you can extend it to your agent of choice: fork it, ask your ai to implement the strategy, and send a pr. pi and more are next. again, PRs welcome.
30s video demo montage below, powered by deepseek 🤣
github.com/afifsohaili/brows…
More choice doesn’t always help customers. Sometimes it leaves them stuck. That's something I've realised working in Kiddocare.
We’ve all got used to AI. We ask it a question, it suggests an answer and explains why, and then we decide whether to accept it or change it. The final call stays with us.
I think businesses should move the same way:
1. Inform: give customers the information they need to understand what they actually need
2. Suggest: offer one best option based on what you know about them, especially their needs, and explain why
3. Hand over the decision: the customer always makes the final call
Most businesses have done step one. They get stuck at step two, either because they don’t have enough data or because they don’t know what to do with the data they have.
afiqsazlan retweeted
If you’re burned out and tired from using AI, you’re spreading yourself too thin. Your brain isn’t made to juggle ten different context windows at once especially when each of them contains challenging work. Moving back to one thread at a time has led to me shipping so much more.
afiqsazlan retweeted
jev new Box primitive is Yolo for everything
your favorite mug, your cat, your specific plant, it can take all that and more as inputs and find it
KKM: "Gunakan pelitup muka yang sesuai"
Tapi letak pelitup muka yang SESUAI sama saiz, sama warna, sama penting dengan pelitup yang TIDAK SESUAI. Ayat untuk pelitup muka yang tak sesuai pun tak jelas sesuai ke tak sebenarnya?
afiqsazlan retweeted
Where does one find people like this? I’d love to have an army of them at 37signals - or just one to start - but I’ve found everyone claims they can do everything but very few can actually do anything.
afiqsazlan retweeted
Introducing Microsoft-Decision-1, our new model for fast decision-making.
It delivers top performance on structured decision tasks, outperforming both LLMs and other decision models in latency and quality.
We’re already testing it across Microsoft for everything from incident response and quality control to scientific discovery.
afiqsazlan retweeted
I'm a full-time designer who decided to sign up for a GitHub account early this year, and I've been doing random vibecode projects in my free time ever since (it almost feels like an addiction)
p/s: I knew nothing about writing code
Satu barang saya beli: carseat baru untuk anak sebab dia dah tinggi. Rasa bangga sokong produk tempatan, Quinton
s.shopee.com.my/1gJFU1fXXt
Satu lagi beli susu Ascenda. Paeds kata isi susu tinggi kalori, sesuai untuk naikkan berat badan.
Saya terus beli 2 x 3 x 600g. Bolehlah tahan 1.5 bulan.
s.shopee.com.my/7faScZm4XD
