@julyx@BetaEpsilonPhi Tapi secara default, ketika ngomong gitu, asumsinya memang sifatnya exclusive OR (XOR). Jadi wajib milih salah satu.
Memang OR dan XOR ini jarang dibedakan dalam obrolan keseharian :))
@anhtiss Saya juga kepikiran ini setelah denger podcast nya Najeela Shihab dan radit. Di era nadiem, I think ia ingin bikin KM mirip IB (self exploration, dll). Di sisi lain, kurikulum sebelumnya mirip2 singapore.
Jadi sepertinya emang secara filosofis berubah. Ini yg bikin โkagetโ
@karirfess Anyway di dual ladder career path, technical staff itu sudah top tier engineer. Jadi posisinya kemungkinan udah setara C level tapi di lajur non-manajerial
SECURITY ADVISORY โ TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE โ packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH โ payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
โข Rotate cloud, GitHub, and SSH credentials immediately
โข Audit cloud audit logs for the last several hours
โข Pin to a prior known-good version and reinstall from a clean lockfile
Detection โ the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
https://t.co/Zy8qG7PA9f
Credit to the security researcher for responsible disclosure.
Mungkin underrated, Muse Spark nya Meta ini oke juga. Pertanyaan teknis, brainstorming, cukup verbose dan detail. Tapi reasoning masih Claude yang top notch
Makin lama makin surreal. Bikin internal tools sekarang modal prompt + replicate existing tools. Near zero development cost dan bis di custom sesuai workflow kita ๐
Excited to announce a new open-source, free-to-use memory tool I have been developing with my good friend @MillaJovovich.
The project is called MemPalace and it is an agentic memory tool that scored 100% on LongMemEval - the industry standard benchmark for memoryโฆ this is higher on than any other published results - free or paid - and it is available now on GitHub.
You can check out Millaโs video about it on her Instagram.
Iโll also put some links in the comments below - please try it out, critique it, fork it, contribute to it - and join our discord.
@rbayuokt Anyway, identation di zed ini udah bener belum ya? Last usage gabisa auto detect dan fallback ke space mau dipaksa gimanapun juga. Cukup nyebelin sebagai tab indent user wkwk
We've been building an internal Claude Code plugin system at Intercom with 13 plugins, 100+ skills, and hooks that turn Claude into a full-stack engineering platform. Lots done, more to do. Here's a thread of some highlights.
Three days ago I left autoresearch tuning nanochat for ~2 days on depth=12 model. It found ~20 changes that improved the validation loss. I tested these changes yesterday and all of them were additive and transferred to larger (depth=24) models. Stacking up all of these changes, today I measured that the leaderboard's "Time to GPT-2" drops from 2.02 hours to 1.80 hours (~11% improvement), this will be the new leaderboard entry. So yes, these are real improvements and they make an actual difference. I am mildly surprised that my very first naive attempt already worked this well on top of what I thought was already a fairly manually well-tuned project.
This is a first for me because I am very used to doing the iterative optimization of neural network training manually. You come up with ideas, you implement them, you check if they work (better validation loss), you come up with new ideas based on that, you read some papers for inspiration, etc etc. This is the bread and butter of what I do daily for 2 decades. Seeing the agent do this entire workflow end-to-end and all by itself as it worked through approx. 700 changes autonomously is wild. It really looked at the sequence of results of experiments and used that to plan the next ones. It's not novel, ground-breaking "research" (yet), but all the adjustments are "real", I didn't find them manually previously, and they stack up and actually improved nanochat. Among the bigger things e.g.:
- It noticed an oversight that my parameterless QKnorm didn't have a scaler multiplier attached, so my attention was too diffuse. The agent found multipliers to sharpen it, pointing to future work.
- It found that the Value Embeddings really like regularization and I wasn't applying any (oops).
- It found that my banded attention was too conservative (i forgot to tune it).
- It found that AdamW betas were all messed up.
- It tuned the weight decay schedule.
- It tuned the network initialization.
This is on top of all the tuning I've already done over a good amount of time. The exact commit is here, from this "round 1" of autoresearch. I am going to kick off "round 2", and in parallel I am looking at how multiple agents can collaborate to unlock parallelism.
https://t.co/WAz8aIztKT
All LLM frontier labs will do this. It's the final boss battle. It's a lot more complex at scale of course - you don't just have a single train. py file to tune. But doing it is "just engineering" and it's going to work. You spin up a swarm of agents, you have them collaborate to tune smaller models, you promote the most promising ideas to increasingly larger scales, and humans (optionally) contribute on the edges.
And more generally, *any* metric you care about that is reasonably efficient to evaluate (or that has more efficient proxy metrics such as training a smaller network) can be autoresearched by an agent swarm. It's worth thinking about whether your problem falls into this bucket too.
Indonesian Flood Explorer
Google baru-baru ini share dataset banjir dari artikel berita dari tahun 2000 sampai dengan tahun 2026.
Datanya cukup besar sekitar 600MB tetapi data tersebut bisa di filter untuk region Indonesia saja dan size sekitar 25MB.
Data ini berasal dari Groundsource, inisiatif metodologi dari Google yang memanfaatkan Gemini, yang mengubah jutaan laporan publik menjadi arsip data berkualitas tinggi untuk membantu memprediksi krisis.
Kalau saya lihat data dari tahun ke tahun banjir di Indonesia memang tambah parah.
App di bawah ini saya buat dgn vibe coding pake GPT-5.4. tujuan hanya ingin render data scr offline & belum ada tujuan khusus (kalau ada ide komen aja)
Tech Stack:
- Tauri + Rust
- DuckDB
- Svelte
Link app menyusul.
Bookmark kalau berkenan.
Halo! Lulusan Linguistik di sini! Saya menemukan video menarik ini dari akun Instagram [@]batyalael.
Sejujurnya, pertanyaan โnyelenehโ kayak gini, hampir pasti ada jawabannya. Ini observasi yang tajam banget, dan justru jadi pintu masuk ke beberapa poin dalam teori pemerolehan bahasa.