AI built this working weather mobile app in one shot, you have to see this, itโs insane!
It fetches live weather data, has push notifications, analytics, and can launch straight to the App Store or Play Store.
My only prompt was โBuild a simple weather app.โ The rest? 100% AI.
Check it out: https://t.co/hWj2zvgPVR
During my time at @FullscriptHQ, I explored how AI agents can help with one of the more tedious engineering problems:
Refactoring existing code ๐งโ๐ป
What I learned:
โข where agents shine
โข where they struggle
โข how to work with them instead of against them
Check out the article here ๐
https://t.co/1vw6u7wulH
TanStack AI now runs on react-native! ๐
Stream down to mobile devices with ease using fetch + polyfills or XHR transports!
Try it out with the latest releases!
After a very thorough 3 day full security sweep and hardening process, we'd like to issue an official all clear โ on TanStack repo and package security. Full details have been updated in our post-mortem and security followup blog (linked below).
TL;DR:
- Only the Router/Start repo was affected. 42 monorepo packages, 2 versions per package. These were promptly deprecated within the hour and removed by NPM shortly after
- All other repos and packages were unaffected and remain secure including: Query, DB, Store, AI, Table, Form, HotKeys, Virtual, Pacer, Config, Devtools, CLI, Intent, etc.
- All available and published versions of every TanStack package are safe to download, including TanStack Router/Start.
https://t.co/KQSXhUM4XM
https://t.co/mtN9hF5Ioy
TL;DR for open-source maintainers
๐ซ NEVER use "pull_request_target" workflows
๐ซ NEVER use shared caches in your publish pipeline
Combining these 2 in particular is extremely dangerous
I've repeated this countless times over the years, but another reminder is always useful
๐จ How the TanStack npm attack actually happened:
1. Attacker opened a normal-looking pull request (#7378) on the TanStack repo.
2. GitHub automatically ran CI tests on that PR.
3. Code inside the PR stole the workflow's GitHub Actions Cache write token during the test run.
4. The attacker used that token to plant poisoned files in the shared build cache. The PR could be closed afterwards. The poisoned cache stays.
5. The official release workflow later pulled from the cache, baked the malicious files into the build, and signed and published 84 malicious package versions to npm.
This is crazy. The hacker installed a dead-man's switch that will wipe your computer if you revoke the GitHub token they stole from you. Revoking the token is what triggers the wipe.
nobody at your company knows what your app actually looks like.
designers ship figma. engineers ship code. PM ships a roadmap.
none of them match.
we built atlas to fix this. point it at any iOS app, get back a complete map of every screen and every path through it.
this is doordash.
ANTHROPIC JUST RELEASED THE OFFICIAL PLAYBOOK FOR BUILDING A COMPANY WITH CLAUDE CODE.
30 minutes. free. from the engineers who built it.
Bookmark this before you forget.
CEO: 1 human. Employees: AI agents. Operations: fully automatic.
The zero-headcount company is no longer a joke.
I'm looking for 50 more software engineers to join my team at https://t.co/dSpoqHsWo9 for the next week. We work with frontier labs to help them train models.
100 - 200 USD /hr. Fully remote. Hiring in 150+ countries. RT's appreciated!
https://t.co/DGV9sKw6di
As soon as your software gets any users, you'll need to deal with every veteran developer's nemesis:
...the backlog
Here's a skill I made (/triage) for burning through your backlog at record speed:
Say goodbye to Dropbox, iCloud, and OneDrive subscriptions.
Someone open-sourced a sync tool that replaces all three for $0. And no company can shut it down.
It's called Syncthing.
Here's how it works:
Every cloud storage company on earth routes your files through their own servers. That's not a technical requirement. That's a business model.
Syncthing skips the server entirely.
โ Your devices connect directly to each other
โ Every transfer is TLS encrypted with perfect forward secrecy
โ Every device is authenticated by a cryptographic certificate
โ Nothing moves without your explicit permission
โ Works on Windows, macOS, Linux, Android, FreeBSD
No account. No subscription. No company holding a copy of your files.
Dropbox can raise prices. iCloud can change its terms. Google Drive can shut down tomorrow.
Syncthing runs on your own machines. There's no server to breach. No company to pressure. No subscription to cancel.
One install. Your devices. Your files. Your rules.
100% Opensource.
https://t.co/zXSEvtiX0a
a 12 parter deep dive about the JSI? sign me up!
(how refreshing to see someone still do this type of content in 2026 โจ)
๐ https://t.co/3YlTX299aH
As a Canadian whose life has been completely changed by entrepreneurship, it's hard to describe how disappointing this graph is ๐
Hopefully we can turn this around, it's in everyone's best interest to cheer for, celebrate, and support your builders.