dataduck (@dataduck_) profile picture

data & AI platform engineering

대한민국 서울
Joined August 2009
Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)Photo by dataduck (@dataduck_)
We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.
178
196
71
4,626
298,224
Amazon EKSでPodごとにハードウェアレベルの隔離ができるようになってる。 通常のPodはノードのカーネルを共有するけど、これはPodごとに独立したNitro Sandbox上で動く仕組みで同じインスタンスの上で動くPodであってもカーネルを共有しない。 ホスト側からもデータを保護する機密モードや、ネットワークを完全に遮断する設定もある。 docs.aws.amazon.com/eks/late…
3
46
12
236
29,573
dataduck retweeted
Introducing @𝚓𝚜𝚘𝚗-𝚛𝚎𝚗𝚍𝚎𝚛/𝚌𝚑𝚊𝚝 Generative UI for Slack, Teams and more → Agents reply with native cards → Tables, fields, charts and buttons → Streams in as the model writes → One catalog for every Chat SDK platform
130
199
60
4,623
279,354
Hello, At 6:32 a.m. PDT we became aware of malicious LiteLLM 1.107.0 artifacts published to PyPI, Docker Hub, and GHCR, which were published at approximately 4:40 a.m. PDT. Enterprise deployments pulling only from our private registry are unaffected by this incident. We are coordinating communication around this incident in this GitHub issue (github.com/BerriAI/litellm/i…). We have removed the malicious releases and images. If you installed or ran them, please follow the remediation guidance in the above-linked issue and treat credentials accessible to those deployments as exposed. Sincerely, Oliver Jensen Director of Security - LiteLLM
6
16
12
86
30,112
dataduck retweeted
Introducing 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜. Run Pi, OpenCode, Codex, Claude Code, eve, fx, or your own harness durably on Vercel. With 𝚍𝚞𝚛𝚊𝚋𝚕𝚎-𝚑𝚊𝚛𝚗𝚎𝚜𝚜, agents automatically resume work after failures and run for hours, days, or months. vercel.com/blog/making-every…
141
107
77
1,489
247,319
dataduck retweeted
5년전에 끝내지 못했던 "최신 데이터 인프라 이해하기"를 다시 시작합니다. 다 설명 못했던 부분과, 그 동안의 바뀐 것들, AI가 들어오면서 바뀐 부분들까지 소개합니다.
5년 만에 다시 보는 데이터 인프라 지도 | 최신 데이터 인프라 이해하기 시즌2 EP01 지난 5년간 달라진 데이터 인프라를 짚고, 시즌1의 수집과 처리에 이어 저장, 쿼리, 분석, 서비스 활용과 AI까지 다룰 시즌2의 첫 시간 저장과 계산, 파일과 테이블 관리를 구분하고 웨어하우스와 레이크, DuckDB, BI 등이 전체 흐름의 어디에 놓이는지 소개 news.hada.io/geekcast/data-i…
2
8
34
3,033
「학부연구생과 석박사, 8년이라는 시간이 흘렀다.」 지도교수로서 학생을 키우는 연구실 육성 시뮬레이션 「Professor Maker」를 공개합니다. 지도하고, 졸업시키고, 추천서 쓰고, 떠나보내세요. gahyoun.github.io/professor-…
1
711
529
846
359,709
> We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime. Deno will remain open source, and we welcome others who want to continue its development. RIP
15
1
46
2,866
dataduck retweeted
非エンジニアと一緒に働いてて、PRを経由せずお互いdevブランチにガンガン直接コミットしまくってるんだけど、全くと言っていいほど問題が起きない push前に必要ならrebaseするだけで、コンフリクトはAIが解決してくれるんだから、そりゃそうだよなと 古いワークフローは即座に見直すべし
7
60
28
791
232,238
Someone rewrote Kafka in Rust and embedded it in Postgres using pgrx 🤯 Kafgres is a Rust-based Kafka broker that runs within Postgres. Kafka clients connect to Postgres on port 9092 and literally can't tell the difference. 🧵
55
169
43
1,771
132,899
dataduck retweeted
스태프 엔지니어를 위한 일감 발굴 가이드 플랫폼 팀의 일감은 장애뿐 아니라 비용, 운영 잡무, 사용자 우회책에서도 찾을 수 있음 원하는 기능보다 실제 작업과 불편, 이미 쓰는 우회책을 살피고, 가장 시끄러운 후보보다 왜 먼저 해야 하는지 설명하는 것이 핵심임 news.hada.io/topic?id=34513
7
16
2,483
dataduck retweeted
We are releasing cf, our new command-line tool that mirrors the entire Cloudflare API and supports programmatic TypeScript configuration. We are also open-sourcing Forge, our internal SDK generator. cfl.re/3VECjml #BirthdayWeek
72
279
147
2,426
546,177
If you're learning Go, spend 30 minutes reading this codebase instead of watching another 2-hour tutorial. (FIRST ONE IS MOST INTERESTING)
5
57
3
680
47,067
🥳 Excited to start revealing what we've been working on in the last few months. First, we decided to reinvent Kubernetes for agentic workloads with statefulness and fast resumption. Secondly, we are building an agentic orchestrator that will be Google's open agentic orchestrator and runtime. github.com/google/ax
128
377
123
4,227
724,441