Kangying L.(Connie)

6.1K posts

Kangying L.(Connie) banner
Kangying L.(Connie)

Kangying L.(Connie)

@timcanby

ML/SWE kaonavi ←SB Intuitions←https://t.co/m94NkbccQb←RecursiveAI(joined pj: https://t.co/CyM5PgT2Pn) ←JSPS DC2(図書館情報学&DH)Ritsumei| Women in Tech🙌New journey ▶️

Linkedin Katılım Mart 2014
1.7K Takip Edilen297 Takipçiler
Kangying L.(Connie)
Kangying L.(Connie)@timcanby·
音声操作できる四足歩行ミニBotを自作する未来まで、まだどれくらい遠いんだろう😭
日本語
0
0
0
23
Kangying L.(Connie) retweetledi
Marc Brooker
Marc Brooker@MarcJBrooker·
I believe that spec-driven development, whether formal specs or conversations, is the future. But writing great specs is hard, and always has been. That's why I'm super excited about this new blog post from the @kirodotdev team, and our automated reasoning teams at AWS.
Marc Brooker tweet media
English
6
41
335
29.4K
Kangying L.(Connie)
Kangying L.(Connie)@timcanby·
生きていて、猫ちゃんをぎゅっと抱きしめられる日々って、幸せだなあ。
日本語
0
0
0
50
Kangying L.(Connie) retweetledi
Google Cloud Japan
Google Cloud Japan@googlecloud_jp·
Google 公式、Agent Skills リポジトリを発表 → goo.gle/48W4Qb0 Firebase や Gemini API、BigQuery、GKE などの Google Cloud プロダクトに関する最新の専門知識に関するスキル情報を、必要なときにだけ読み込むため、コンテキストの肥大化を抑えられます。 #GoogleCloudNext
Google Cloud Japan tweet media
日本語
9
260
1.4K
210.6K
Kangying L.(Connie) retweetledi
Nitin.nn
Nitin.nn@NitinthisSide_·
🧵 Day 27/30 — #SystemDesign Your system is running in production. Users report slow APIs. Payments randomly fail. CPU looks normal. Logs are huge. Nobody knows where the actual problem is. This is where Observability becomes critical. Observability is the ability to understand what’s happening inside a system by analyzing its outputs — mainly: → Logs → Metrics → Traces Without observability, debugging distributed systems becomes guesswork. ⸻ Logs tell you what happened. Example: → Error messages → Request details → Stack traces → Authentication failures Useful for deep debugging. ⸻ Metrics tell you how the system is behaving. Example: → CPU usage → API latency → Request count → Error rates → Memory consumption Useful for monitoring health and detecting anomalies. ⸻ Traces tell you where time is spent across services. In microservices, one request may travel through: API Gateway → Auth Service → Payment Service → Database Distributed tracing helps visualize the full journey and identify bottlenecks. ⸻ Modern production systems use observability stacks like: → Prometheus + Grafana → ELK Stack → OpenTelemetry → Jaeger → Datadog → New Relic Companies like Uber, Netflix, Google, and Amazon heavily invest in observability because scaling systems is impossible if engineers cannot see failures clearly. Monitoring tells you something is wrong. Observability helps you understand why. #30DaysOfSystemDesign #Observability #BackendEngineering
Nitin.nn tweet media
Nitin.nn@NitinthisSide_

🧵 Day 26/30 — #SystemDesign Retries seem harmless. An API fails → retry the request. Still fails → retry again. Simple… until thousands of servers start retrying together and accidentally take the entire system down. That’s why production systems use Retry Strategies with Exponential Backoff instead of blind retries. A retry mechanism helps recover from temporary failures like: → Network instability → Timeout issues → Short server overloads → Rate limiting But retrying instantly creates traffic spikes during failures. Exponential backoff solves this by increasing delay after every failed attempt. Example: → Retry 1 → wait 1s → Retry 2 → wait 2s → Retry 3 → wait 4s → Retry 4 → wait 8s This gives systems time to recover instead of getting overwhelmed. Modern systems also add Jitter (randomness in delay) so millions of clients don’t retry at the exact same moment. Without jitter: → Retry storm → Traffic spikes → Cascading failures With jitter: → Requests spread naturally → Better recovery behavior → More stable systems That’s why companies like AWS, Google, Stripe, and Netflix heavily recommend exponential backoff patterns in distributed systems. Retries improve resilience. Uncontrolled retries destroy resilience. #30DaysOfSystemDesign #DistributedSystems #BackendEngineering

English
10
50
329
22.7K
Kangying L.(Connie) retweetledi
Kangying L.(Connie)
Kangying L.(Connie)@timcanby·
今日も朝4時半に起きて、ちょっと気合いを入れて創作料理を作りました。 ここ2日間、作業部屋ではずっと出前ばかり頼んでいたので、やっぱり自分で作ったご飯のほうがおいしいな〜と実感しました😆😆😆
日本語
0
0
0
45
Kangying L.(Connie) retweetledi
Peter Steinberger 🦞
Peter Steinberger 🦞@steipete·
The more skills you give codex, the less you have to prompt.
Peter Steinberger 🦞 tweet media
English
113
79
1.8K
159.2K
Kangying L.(Connie) retweetledi
Womp
Womp@womp3D·
pov: you make your own tech gadgets
English
4
70
760
52.1K
Kangying L.(Connie)
Kangying L.(Connie)@timcanby·
そろそろ片付けて帰る! 今日は自分用にキーホルダーを3Dプリントしたので、帰ってから色塗りする😆😆
Kangying L.(Connie) tweet media
日本語
0
0
0
90
Kangying L.(Connie)
Kangying L.(Connie)@timcanby·
今日は土台部分だけ組んでみた。 物理をちゃんと勉強してこなかったツケが回ってきて、見事に設計ミスしました😂 続きは来週末に期待…!
日本語
0
0
0
104
Kangying L.(Connie)
Kangying L.(Connie)@timcanby·
やばい😭 東京で、子どもの頃に家族が生地から手作りしてくれた肉まんと「シュウマイ」の味に巡り合えた…! しかも、ずっと心待ちにしてた「もち米シュウマイ」!! (私が小さい頃食べてたシュウマイは、中身がお肉じゃなくてもち米だったの。ずっとこの味を懐かしんでたんだよね…) 最高すぎる
Kangying L.(Connie) tweet media
日本語
0
0
0
82