dataduck retweeted
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.
dataduck retweeted
ブログ書きました: Google、Kubernetesで10倍高密度にAIエージェントを実行可能にする「Agent Sustrate」と「gVisor」、オープンソースとしてCNCFに寄贈と発表
publickey1.jp/blog/26/google…
eks에서 Agent Substrate poc 하려다 미루고 있었는데 알아서 내주는 듯…agentcore runtime의 사악한 가격 대안이 될 수 있을지..
AWS Nitro Sandboxes on Amazon EKS just dropped. Nitro Sandboxes + Strands Box could be a really powerful combination for securing AI agents. Nitro provides hardware-level isolation, while Strands Box adds fine-grained policy enforcement over what agents can actually do inside that sandbox. aws.amazon.com/about-aws/wha…
150
어차피 쓰지도 못할 테스트만 할 수 있는 모델을 시간들여 볼 필요가 있을까?? 뭐하러 공개 하는거지...
韩国顶级大厂 LG 直接放大招了!!免费免费免
韩国 LG AI 研究院,今天宣布免费开放自研大模型 K-EXAONE 2.5 的 API
重点是:开发者、创业团队、企业、研究机构,任何人都可以申请 API Key,免费调用,不需要付费订阅!
而且这个模型最值得关注的不是聊天能力,而是 Agent
官方公布了 4 项 Agent 能力测试成绩:
AutomationBench:74.6 分,业务自动化
SWE-Bench Pro:59.2 分,软件开发与代码修复
BrowseComp:78.0 分,网页搜索与信息检索
Claw-Eval:77.3 分,Agent 工作环境中的问题解决
LG AI 研究院表示,在这几项基于开放数据集的内部评测中,K-EXAONE 2.5 已经展现出能够与 DeepSeek-V4.1-Flash、GLM-5.3 等模型竞争的 Agent 能力。
这意味着什么?
如果你正在折腾 AI Agent、Codex、自动化工作流,或者自己开发 AI 产品,又多了一个值得测试的免费模型 API。
尤其是独立开发者,模型调用成本一直是绕不开的问题。
现在又有大厂开始免费开放自研模型 API 了。
AI 模型越来越强,调用成本却有机会越来越低
官方 API 申请入口:
docs.exaone.ai/
建议先收藏,亲自测试一下实际效果。
LG 这次是真的给开发者送福利了
2
201
dataduck retweeted
Amazon EKSでPodごとにハードウェアレベルの隔離ができるようになってる。
通常のPodはノードのカーネルを共有するけど、これはPodごとに独立したNitro Sandbox上で動く仕組みで同じインスタンスの上で動くPodであってもカーネルを共有しない。
ホスト側からもデータを保護する機密モードや、ネットワークを完全に遮断する設定もある。
docs.aws.amazon.com/eks/late…
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
herdr는 터미널에서 쓸수 있어서 가치가 있는건데
herdrui.dev
もうターミナル自体使わなくていいじゃない
그냥 원래대로 돌아온거 아니야?
Day 25/
We are doubling all usage limits for all Pro 100/200/500 tiers and Business Premium, effective today.
We heard your kind feedback and won’t be reducing usage limits for Pro 200, so your Work and Codex usage will stay the same. We’re also going to continue offering extended limits for dots for now, and usage of your dot will still continue to be separate from your default usage.
And we'll of course also keep shipping better models and other efficiency improvements that increase your effective usage over time.
1
3
838
dataduck retweeted
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






















