Huy Phan

[iam_the_code @iam_the_code]

Loved how @boltapp bottom sheet collapses on the home screen, so I recreated it in React Native. Three snap points, drag-linked fades, the search bar riding up under the handle all Reanimated + Expo.

[Hugo @hugosaintemarie]

reminder to use `scrollbar-gutter: stable` if your layout shifts when the scrollbar disappears

[Roan @RohOnChain]

this is f*cking dangerous

someone just open sourced the entire "LOOP ENGINEERING" framework for free

build a hedge fund printing alpha 24/7 by feeding it into claude code with my article below

bookmark before someone takes it down

[Jiahan Chen @jiahan_c]

Small CI tip:

On Node.js 22+, use `node --run <script>` instead of `pnpm run <script>` for simple package scripts in GitHub Actions.

Tiny change, saves 200-400ms per call.

[Enzo Manuel Mangano @reactiive_]

The demo is built with React Native, and it's open source (along with 120+ React Native animations).

The secret ingredient is react-native-skia. After getting checkmated, we take a snapshot and then run the shader.

The "invisible" secret ingredient is Pulsar. It brings high-quality haptics and really adds a three-dimensional feel to the whole animation.

https://t.co/dwQaCluwt9

[そう｜Claude Codeで始めるAI自動化 @so_ainsight]

今週GitHubで急上昇したAI関連リポジトリ10選：

1. Understand-Anything
コードベース全体を対話型のナレッジグラフに変換するツール。知らない大規模コードでも構造・依存関係・業務ロジックを地図のように可視化して、検索や質問ができる。Claude Code・Cursor・Copilot・Gemini CLIに対応。
https://t.co/j9hK6tImY1

2. codegraph
コードを事前に索引化して、AIコーディングエージェントが毎回ファイルを探し回らずに済むようにするツール。トークン消費を約57%、ツール呼び出しを約62%削減。完全ローカル動作で外部送信なし。
https://t.co/TChuWEXUXk

3. MoneyPrinterTurbo
キーワードを入れるだけで台本・素材・字幕・BGMを自動生成し、高画質の短尺動画を作るツール。名前は派手だが中身はAI動画の自動生成。縦9:16も横16:9も対応。
https://t.co/oD69Imz5NC

4. ECC
Claude Code・Cursor・Codexなど複数のAIエージェント環境の性能を底上げするシステム。スキル・記憶・セキュリティを一式で提供し、63のエージェントと249のスキルを同梱。
https://t.co/MnxisTgzbU

5. taste-skill
AIが作るUIを「ありがちで退屈なデザイン」から脱却させるスキル集。レイアウト・タイポグラフィ・余白などプロのデザイン原則を適用する。Claude・Cursor・Codexで使える。
https://t.co/HE8DfLbm6w

6. knowledge-work-plugins
Anthropic公式の、Claudeを職種別の専門家に変える11種のプラグイン集。営業・サポート・マーケ・法務・財務などの業務向け。Claude Cowork中心で、Claude Codeでも使える。
https://t.co/tlnroaTAUp

7. Anthropic-Cybersecurity-Skills
AIエージェントにサイバーセキュリティの専門知識を持たせる754のスキル集。MITRE ATT&CKなど5つのフレームワークに対応。名前にAnthropicと付くが公式ではなく有志のコミュニティ製。
https://t.co/0jkC8aBYrP

8. academic-research-skills
Claude Code向けに、研究→論文執筆→査読→改稿を通しでこなすスキル集。引用チェックなど面倒な作業はAIが担い、知的判断は人間が握る「AIは副操縦士」設計。
https://t.co/lZjSi0h8aO

9. pi
コーディングエージェントCLI・複数LLMを束ねる統一API・エージェント実行基盤・ターミナルUIまで揃ったAIエージェント開発ツールキット。Slack連携も可能で、依存関係を固めてサプライチェーンの安全性も重視。
https://t.co/iQpX6RX7iS

10. skills（Anthropic公式）
Claudeに専門タスクをこなさせる「Agent Skills」の公式サンプル集。SKILL(.)mdに手順を書くだけで、Claude Code・Claude(.)ai・APIで使い回せる。スキルの作り方の見本にもなる。
https://t.co/ZoYJKevxF4

今週のトレンドは「AIエージェントのスキル集」と「コードの知識グラフ」一色。AIにコードを地図として読ませ、スキルを着せ替えて使う流れが一気に来てる。

保存して、来週のリストと見比べて。

[Joan @JuanRdBO]

expo-media-viewer just crossed ~10k downloads/month.

It turns any Expo thumbnail layout into a native fullscreen image/video viewer, with transitions, zoom, swipe dismiss, video playback, and auth URLs.

v0.5.1 is out today!

[Nate de Jager @dejager]

Pro tip: If you want Codex to debug/enhance your iOS animations have it use FFmpeg to convert a screen recording of the animation to a sprite sheet it can analyze.

This also works if you want to 'decompile' an animation to code.

[Sagar Shiroya @sagarshiroya_x]

React Session 4 Notes

Takeaways:
- State is the single source of truth.
- Normal variables do not trigger UI updates.
- useState gives value and setter.
- Setter updates state and signals React.
- React creates new virtual DOM after update.
- React compares old and new virtual DOM.
- Only changed real DOM nodes are updated
- Component must return one parent node.
- Props pass data from parent to child.
- Every component instance has its own state.
- Keys help React identify list items.
- Do not use index as key when list changes.
- Do not mutate array/object state directly.
- Use new reference for state updates.
- Next.js improves first paint using SSR/server components.
- Use client components only where interactivity is needed.

[Geek Lite @QingQ77]

不开 Simulator .app，用命令行或浏览器远程管 iOS 模拟器、点按滑动全搞定。

https://t.co/uhke7zLI8m

baguette 是个 Swift 写的无头 iOS 模拟器管理器，针对 iOS 26。一个 CLI 就能建、启、停模拟器，60 fps 推屏（MPEG 或 H.264 都行），靠 Xcode 26 的 SimulatorKit 私有框架注入触控手势和按键，不用注入 dylib。自带 Web UI，/simulators 管单个设备，/farm 并排管多个，同一条 WebSocket 管道搞定画面和输入。代码分层清晰，110 多个测试，swift test 不用起模拟器就能跑。

[Nitin.nn @NitinthisSide_]

🧵 Day 17/30 — #SystemDesign

Idempotency: How systems avoid duplicate payments, orders, and repeated actions

A user clicks “Pay Now” once… but the button freezes. They click again. Network retries happen. Mobile app resends the request after reconnecting. Suddenly your system may create two orders or charge the card twice.

That’s why reliable systems use Idempotency.

An operation is idempotent when repeating the same request multiple times produces the same final result as doing it once. The first request performs the action. Repeated identical requests should not create duplicate side effects.

This is critical in payments, bookings, checkout flows, and APIs exposed to unstable networks.

⸻

Simple Example

Without idempotency:

→ User clicks Pay twice
→ Two payment requests processed
→ Two charges happen

With idempotency:

→ Request contains unique idempotency key
→ First request succeeds
→ Duplicate request with same key returns original result
→ No second charge

Same request. Same outcome.

⸻

How It Works

Client sends request:

POST /payments
Idempotency-Key: abc123

Server stores:

→ Key
→ Request fingerprint
→ Final response / status

If same key arrives again:

→ Detect duplicate
→ Return saved response
→ Skip duplicate processing

This makes retries safe.

⸻

Where It Matters Most

→ Payment APIs
→ Order placement
→ Ticket booking
→ Wallet transfers
→ Subscription renewals
→ Webhook processing
→ Inventory reservations

Anywhere duplicates are expensive or harmful.

⸻

Real Companies

→ Stripe popularized idempotency keys in APIs
→ Payment gateways use retry-safe transactions
→ Booking systems avoid duplicate reservations
→ Fintech apps rely heavily on idempotent writes

Strong systems assume retries will happen.

⸻

Common Implementation Methods

→ Idempotency keys from client
→ Unique DB constraints
→ Transaction logs
→ Deduplication tables
→ Message consumer dedupe in queues

Often multiple layers are combined.

⸻

Challenges Most Ignore

Bad implementations fail when:

→ Same key used for different payloads
→ Key expires too early
→ Response not stored properly
→ Race conditions on concurrent requests
→ Only frontend prevents double click

Frontend protection is not enough. Backend must enforce safety.

⸻

Idempotent vs Non-Idempotent

Usually idempotent:

→ PUT update profile
→ DELETE resource (repeated delete still deleted)

Often non-idempotent by default:

→ POST create order
→ POST charge payment

But POST can be made idempotent with proper design.

#30DaysOfSystemDesign #Idempotency #BackendEngineering

[Sagar Shiroya @sagarshiroya_x]

High Throughput Systems using Kafka

#kafka #chaicode

[Fernando @Franc0Fernand0]

If I had to learn system design fundamentals from scratch, I would read the following 16 curated articles (links below): ↓

[Peter Piekarczyk (🥧🚗🐥) @peterpme]

My favorite react native android adb commands:

- adb logcat --pid=$(adb shell pidof <pkg>)
- adb shell pm list packages | grep <app>
- adb shell pidof <pkg>
- adb install -r app.apk
- adb exec-out screencap -p > screen.png
- adb pull /sdcard/<file> ./

What am I missing?

[Peter Piekarczyk (🥧🚗🐥) @peterpme]

All you need to know about building fast React native apps is in this one box

[Abhishek Singh @0xlelouch_]

System Design roadmap !!

Start → Basics → Networking → OS → Databases → Caching → Messaging → Scaling → Reliability → Security → Observability → Practice

Requirements → APIs → Load Balancer → App Servers → Database → Cache → Queue → Storage → CDN → Rate Limiter → Monitoring

Client → DNS → CDN → Reverse Proxy → Service → DB → Cache

Latency → Throughput → Availability → Consistency → Durability → Fault Tolerance → Scalability

SQL → NoSQL → Indexing → Replication → Sharding → Partitioning → Transactions

REST → gRPC → WebSockets → Async Processing → Event-Driven Systems

Redis → Kafka → RabbitMQ → S3 → Postgres → Elasticsearch

Single Node → Distributed → Multi-AZ → Multi-Region

Monolith → Modular Monolith → Microservices only when needed

Logs → Metrics → Tracing → Alerts → SLOs

Brute force design → Bottleneck finding → Tradeoff thinking → Better architecture

Functional requirements → Non-functional requirements → Capacity estimation → High level design → Deep dive → Failure cases → Scale plan

Read designs → Watch failures → Build small systems → Review mistakes → Redesign again

URL Shortener → Rate Limiter → Chat App → Notification System → Search → Feed → Payment System → Ride Sharing

Think → Draw → Explain → Defend tradeoffs → Improve

Consistency → Clarity → Repetition → Deep work

End → Crack interviews and build real systems

Save this !!

[Yiğit @yigitech]

mobil uygulamanızda olası tüm bugları deneyen ve varsa raporlayan claude eklentisi.

https://t.co/sKPMSN9ivv

[SumitM @SumitM_X]

Want to be a backend architect ?

Please learn :

1. Microservices Design
Service decomposition, Bounded contexts, Resilience (Circuit Breaker, Bulkheads)

2. Distributed Systems Fundamentals
CAP Theorem, Event sourcing, CQRS, Data consistency models (ACID vs. BASE)

3. High-Performance Data Management
Database partitioning, Index optimization, NoSQL data modeling

4. Advanced API Design
gRPC, GraphQL, API Gateways, Asynchronous APIs

5. Event-Driven Architecture
Kafka, Message queues, Pub/Sub patterns, Saga pattern

6. Cloud-Native Patterns
Container orchestration (Kubernetes), Serverless, Multi-cloud strategies

7. Observability
Distributed tracing (OpenTelemetry), Centralized logging (ELK), Real-time monitoring

8. Infrastructure as Code
Terraform, Helm, Configuration management best practices

9. Advanced Security
Zero Trust, OAuth2, JWT, Data encryption in transit and at rest

10. Scaling Strategies
Load balancing, Sharding, Horizontal vs. vertical scaling

[SumitM @SumitM_X]

As a React.js Developer, how many of the below concepts can you explain :

1. Fiber Architecture

2. Concurrent Mode

3. Suspense for Data Fetching

4. Passive Effects vs Layout Effects

5. Hydration

6. useTransition

7. FlushSync and Deferred Updates

8. Error Boundaries

9. React.memo vs useMemo vs useCallback

10. Context Re-renders

[Simon @iced_coffee_dev]

Most online tools only optimize file size, but they're still reinflated in memory.

This tool will optimize your GLTF/GLB assets and export to GPU-compressed KTX2, entirely client-side.

Try it here: https://t.co/FydO3NEXjB

#threejs #gamedev