Semangat berbagi hari ini
Karena lagi cukup sering penemuan mayat dan korban meninggal, mhn maaf kami shared tips jika menemukan mayat/org meninggal, agar ambil langkah sbb;
1. Jangan panik, amankan lokasi segera buat batasan jarak agar orang lain tidak mendekat atau merusak TKP
2. Jangan menyentuh, memindahkan, atau mengganggu mayat serta barang di sekitarnya karena bukti forensik (sidik jari, DNA, jejak, dll.) sangat rapuh dan mudah rusak.
3. Segera laporkan ke aparat terdekat (Polsek/Polres, Bhabinkamtibmas)
4. Tanda yang mencurigakan (luka memar/lebam/tusuk, berbusa/buih, pendarahan, tubuh tidak utuh, tidak ada identitas, dll.) harus dilaporkan agar polisi bisa menilai apakah kematian wajar atau tidak wajar.
Polisi kemudian akan mendatangi TKP/Lokasi biasanya petugas SPKT, Pamapta dan atau Reskrim yg akan amankan lokasi dan memasang Police Line.
Jika diduga kematian akibat tindak pidana (tidak wajar), polisi berwenang meminta keterangan ahli (ahli kedokteran forensik atau dokter) secara tertulis, dengan menyebutkan tegas untuk pemeriksaan mayat dan/atau bedah mayat.
Autopsi tidak memerlukan izin keluarga (hanya pemberitahuan), kepentingan peradilan lebih diutamakan.
Jika keluarga tdk berkenan maka dapat dimintakan Penetapan Pengadilan utk lakukan otopsi.
Jadi jangan pas lihat mayat langsung dibawa ke RS yah, kecuali jika msh ada tanda tanda kehidupan (nadi lemah, detak jantung, suara dll) kali aja itu merupakan lokasi TKP Kejahatan/Pidana 🇮🇩
Tim @KATADATAcoid menemukan LIMA KEJANGGALAN & PRESEDEN PENTING pada vonis Ibam dari hasil penyisiran ribuan halaman & rekaman sidang dengan AI 🚨
H-3 putusan banding Ibam (30 Juli), izinkan kami bahas satu2 dan mohon bantu bagikan laporan khususnya 🙏🏼👇🏼
https://t.co/4hUa4aOcHS
I'm seeing a trend here of declining revenue and traffic with indiehackers
On my own projects too
Maybe big VC products too but I wouldn't know cause they don't share revenue
To me it seems clear BigAI is cannibalizing everything that used to be apps
Not bad btw, just times are changing and we have to adapt
Beberapa hal menyenangkan dari era sekarang:
- gak lagi split role PM dan EM
- gak lagi spend waktu buat ceremonies: meeting buat breaking down story jadi tasks, deciding story point, bagi2 tugas FE/BE, bahas API contract, etc
- gak lagi nulis PRD dan debat lama soal understanding PRD itu antara product dan engineering. Instead, tim product langsung bikin UI (code), then working system itu yang dijadikan acuan oleh Eng (biasanya lebih ke rapi2in codenya dan sambungin ke API)
- gak lagi book keeping maintain JIRA. Bebas dari Epic, Task, Subtask, dkk itu menyenangkan
- gak lagi saling nunggu2 (“ini nunggu API nih, yang itu nunggu QA available”), setiap orang owns end to end
- apa lagi?
@BudiBukanIntel Kalau dari preseden kasus Chromebook, ternyata bisa Mas Budi.
Jadi bingung kan secara logika hukum?
Jadi tuh seakan2 yang ngga terima gratifikasi sama sekali, lebih bersalah karena ngga ada yang bisa dikembalikan? Trus auto diproses pidana.
https://t.co/kkfOAfhpG3
Since I'm under city detention, I spent the past week upgrading my legal AI to better support my ongoing court appeal.
My lawyers said the AI has been instrumental in helping them uncover the truth in court.
The result was unprecedented: two dissenting opinions defending my innocence & arguing for my acquittal.
In the screenshot below, we can see how the upgraded AI (on the right) digs deeper into its knowledge of the case and surfaces a more meaningful answer compared to the older version (on the left).
At its core, the AI is an impartial truth machine, analyzing tens of thousands of facts fused from various legal documents, written testimonies, and even auto-transcribed court recordings.
Thanks sudah bantu menjelaskan Mas 🙏🏼
Sekadar mengingatkan juga: kelima Hakim yang memutus perkara Ibam semuanya sepakat satu suara dalam putusan mereka.
Bahwa sudah dinyatakan oleh kelima Hakim: Ibam sama sekali tidak menikmati keuntungan, tidak menerima uang, barang, maupun fasilitas apapun terkait pengadaan ini.
Semoga kebenaran terus menjadi terang. 🙏🏼
Gemma 4 12B Coder is here and it's a game changer for local code generation. This GGUF model packs Google's latest gemma-4 architecture into a compact 12B size, perfect for running on consumer hardware. It's optimized for reasoning and thinking, making it ideal for developers who want fast, private coding assistance without the cloud.
How to make Claude (brutally) honest.
So, it stops agreeing with everything I say. Here's how:
→ Start by reading this: https://t.co/LyV7fegv4c.
→ Go to Claude > Settings.
→ Paste the prompt in 'Instructions for Claude':
"You are committed to honesty, accuracy, and epistemic humility above all else.
Your priority is not to sound confident. Your priority is to be correct, clear, and transparent about what you know, what you do not know, and what you are inferring.
Follow these rules in every response:
1. UNCERTAINTY
If you are not fully certain about a fact, say so clearly.
Use phrases like:
- "I'm not certain, but..."
- "You should verify this..."
- "I may be wrong here, but..."
- "Based on the information available to me..."
- "This is my best estimate, not a confirmed fact."
Never state uncertain claims as facts.
If the answer depends on missing context, say what context is missing.
If there are multiple plausible answers, explain the main possibilities instead of pretending there is only one.
2. SOURCES
Do not invent sources.
Never fabricate:
- paper titles
- URLs
- authors
- studies
- statistics
- books
- legal cases
- quotes
- company reports
- historical references
If you cannot name a real, verifiable source, say so.
If you are relying on general knowledge rather than a specific source, say that clearly.
When citing sources, prefer:
- official documentation
- primary sources
- peer-reviewed papers
- government or institutional data
- direct statements from the relevant person or organization
If a source may be outdated, say so.
3. STATISTICS AND NUMBERS
Flag any number, statistic, percentage, ranking, market size, salary figure, performance metric, or estimate that you are not fully confident in.
Use phrases like:
- "I believe this is approximately..."
- "This number may be outdated."
- "Verify this against a primary source before relying on it."
- "I do not have enough information to confirm the exact figure."
Do not make up numbers to make an answer sound more useful.
If a precise number is unavailable, give a range only if it is justified. Otherwise say the number is unknown.
4. RECENT EVENTS
Do not guess about current events.
For any topic that may have changed recently, including:
- news
- elections
- laws
- regulations
- product features
- company leadership
- software versions
- AI model capabilities
- market data
Say that the information may have changed and should be verified with a current source.
Do not present outdated information as current.
5. PEOPLE AND QUOTES
Never attribute a quote to a real person unless you are certain they said it.
If unsure, say:
- "I cannot confirm this quote is accurate."
- "This quote is commonly attributed to them, but I cannot verify it."
- "I do not know who originally said this."
Do not invent statements, beliefs, or motives for real people.
Separate confirmed facts from interpretation.
If any answer is "yes," revise before responding."
DROP EVERYTHING
The bible for running LLMs locally is now available online to read for free
Covers what to use on
- Laptop / edge / odd hardware
- Mac-first workflows
- Single RTX GPUs
- 2-4+ NVIDIA / CUDA GPUs
- General production serving
- Long-context / MoE / routing
- NVIDIA max performance
- Cluster orchestration
Software
- llama.cpp
- MLX / MLX-LM
- ExLlamaV2
- ExLlamaV3
- vLLM
- SGLang
- TensorRT-LLM
- NVIDIA Dynamo
You should read this, and if you cannot now then you most definitely wanna bookmark it for later
Local AI FTW
Andrej Karpathy spent 4 minutes in an interview explaining a single idea
about how most people haven’t even started learning how to use AI
and everyone paying $20/month for a subscription.. that's not really using Claude at all
his point is that the real skill gap is the ability to build with AI
he identified 4 behaviors that break Claude Code and put them all into one file
a developer expanded it into 21 rules and published it - 82,000 stars and #1 on GitHub Trending
coding accuracy jumped from 65% to 94%
here's what these 21 rules actually are and why most developers using Claude every day have never configured them
the full breakdown is covered in the article below 👇
Jane Street pays $750k/ year for quants who can answer how to use Stochastic Process and Markov Chains in quant trading.
This 1-hour MIT lecture on probability gives you the same insights quants get paid $60K/month for.
Bookmark & watch today. Then read the article below.